Skip to content

Conversation

@briskt
Copy link
Contributor

@briskt briskt commented Nov 5, 2025

IDP-1734 ssp-hub-production secondary region deployment is broken


Changed

  • BREAKING CHANGE: add the region name to the end of the CD user name to avoid conflict when this module is used by the same app in the same account in multiple regions.

@briskt briskt requested a review from a team as a code owner November 5, 2025 02:32
@briskt briskt requested review from Praveenraj-K, forevermatt, hobbitronics and jason-jackson and removed request for a team November 5, 2025 02:32
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 5, 2025

Copy link

@hobbitronics hobbitronics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a good solution

@briskt
Copy link
Contributor Author

briskt commented Nov 5, 2025

Seems like a good solution

Yeah, I can't count the number of times this has bitten me. IAM is, like S3, a global service so names have to be unique across regions. (S3 bucket names have to be unique across the entirety of AWS.)

@briskt briskt merged commit 077c1bc into main Nov 5, 2025
2 checks passed
@briskt briskt deleted the cd-user-name branch November 5, 2025 06:19
@forevermatt
Copy link
Contributor

Umm... I'm probably missing something. Is there a way (when doing a single GitHub Actions run) to use different credentials for deploying to the different regions?

I suppose it could be separate secrets on the GitHub repo, used where needed in the GitHub Actions workflow. Never mind, presumably that's the direction you're going. (Thanks!)

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants