Skip to content

Conversation

@benbart
Copy link
Contributor

@benbart benbart commented Aug 4, 2025

Running this was causing an error despite setting the region in the aws creds. Hardcoding it to us-west-2 is a reasonable solution since we're never not deploying cumulus to that region.

@etcart
Copy link
Collaborator

etcart commented Dec 12, 2025

your region needs to be set in a way that (to me) is nonsensical, but this is an aws cli problem not a cirrus problem (IMO)
you can set it in a file called ~/.aws/config (not credentials)
with a block that looks like

[profile cumulus-sit]
region = us-west-2

where cumulus-sit is my profile name
this is different from your credentials file where that block looks like

[cumulus-sit]
credentials.....

(not [profile cumulus-sit])
why the diff? I don't know but setting this right fixed things for me

additionally, if we're going to hardcode region that needs to be done in env.sh as well where the same thing happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants