Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backend/s3: Adds support for IAM role chaining #35720

Merged
merged 9 commits into from
Sep 23, 2024
Merged

Conversation

gdavison
Copy link
Contributor

Adds support to the S3 backend for IAM role chaining when authenticating with AWS. Provides parity with the AWS provider v5.67.0

Target Release

1.10.0

Draft CHANGELOG entry

ENHANCEMENTS

  • backend/s3: Adds support for IAM role chaining. The backend attribute assume_role now accepts multiple elements.

Copy link
Member

@jar-b jar-b left a comment

Choose a reason for hiding this comment

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

LGTM 🎉

% TF_ACC=1 go test ./...
ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 145.240s

internal/backend/remote-state/s3/go.mod Outdated Show resolved Hide resolved
@gdavison gdavison merged commit 305775e into main Sep 23, 2024
7 checks passed
@gdavison gdavison deleted the s3/f-role-chaining branch September 23, 2024 21:26
Copy link

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants