-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Versioning on s3 outposts #40759
base: main
Are you sure you want to change the base?
Versioning on s3 outposts #40759
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @AnanyaDevGo 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
Description
This PR introduces a new resource, aws_s3control_bucket_versioning, to support enabling versioning for S3 Outposts buckets. The existing aws_s3_bucket_versioning resource is not modified and remains dedicated to regular S3 buckets.
Context
The issue, #33119, highlights that the aws_s3_bucket_versioning resource cannot handle S3 Outposts buckets due to:
API Differences: Outposts require s3control.PutBucketVersioning instead of s3.PutBucketVersioning.
Validation Differences: Outposts use ARNs (arn:aws:s3-outposts) instead of bucket names.
Versioning Status Support: Outposts only support Enabled and Suspended statuses, not Disabled.
Closes #33119.