Fall back to USEast1 aws region when region is not set - #2101
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
AWS OIDC accounts stopped working for Kubernetes API targets on EKS after the AWS SDK v4 upgrade in 2026.2, with health checks and deployments both failing with
Cannot find supported authentication schema. A Kubernetes API target has nowhere to set an AWS region, so Calamari falls back to theaws-globalregion which fails for unsigned STS requests.Results
us-east-1instead ofaws-global. A configured region still takes precedence.ap-southeast-2with no region set: health check, raw YAML deployment, access-key account and assume-role.Fixes HPY-1542
Before
After