We're getting a forbidden response when configuring an s3_resource in the cloud. The same settings and code work locally and using

dagster dev

. Once deployed to the branch deployment, it fails on init when validating access to the bucket. We found that locally we receive the same forbidden error when changing the system time. This may or may not be related.

botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden

• Is this something encountered before? • I there a way to create more verbose init logs to troubleshoot such issues?

i can take a look - can you dm me the name of the branch?

Thank you jordan. We found the issue. We have to pass

region_name

with the s3 config when calling

build_init_resource_context

Chatting in DM but repeating here for any other readers: I suspect fargate is setting

AWS_REGION

or

AWS_DEFAULT_REGION

by default which boto3 is in turn using: https://github.com/aws/containers-roadmap/issues/1611 https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html So explicitly setting the region in the boto3 client or session is probably a good idea.