Confirm that you have the right credentials sourced and make sure you have a region specified in your sourced credentials. Are you able to launch a client access gateway for the same system? With that running, can you curl for the S3 bucket?
Thanks Jaret. Yes all of those are configured - a local db repl connection works and the curl command above responds with
{:s3-auth-path “bucket-name”}
I wanted to circle back here to close the loop in case someone else runs into this issue. Dean and I worked together on a support case to share the details in his output. And it turns out that Dean was using the compute group name and not the system name for analytics sync command.