Deployments using AWS OIDC Accounts Use Incorrect Region

[briggs-octo]

Severity

1 report

Version

2026.2.12437

Latest Version

None

What happened?

When using an AWS OIDC account, the AWS region specified within the account is incorrectly used for all deployments. If no AWS region is specified within the account, the default is us-east-1, which will then also used for deployments.

Reproduction

1. Configure an AWS OIDC Account
2. Define an AWS deployment process, specifying a different region for the deployment than what was specified in the AWS account (e.g., Upload a package to an AWS S3 bucket step)
3. Note that the AWS region used for the deployment is sourced from the AWS account (or us-east-1 if undefined) rather than what's defined in the deployment process.

Error and Stacktrace

Regular AWS Account Output (expected):

Regular account:
17:06:54   Info     |       Running the step as the AWS user xyz
17:06:54   Verbose  |       Bucket eu-west-octopus-test exists in region Europe (Ireland) (eu-west-1). Skipping creation.


AWS OIDC Account Output (incorrect):

17:14:28   Info     |       Running the step as the AWS role OctopusDeployS3Role/OctopusAwsAuthentication
17:14:28   Verbose  |       Bucket eu-west-octopus-test exists in region US East (N. Virginia) (us-east-1). Skipping creation.

More Information

No response

Workaround

Use a regular AWS account (non-OIDC)

OR

Create region-specific AWS OIDC accounts and use the appropriate account for the region you're deploying to

[briggs-octo]

Related to #9955