-
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
Add 'Governance' and 'Compliance' object retention modes for aws_s3_bucket #6872
Comments
It looks like we will need to modify a couple of resources for full support: Suggested syntax: resource "aws_s3_bucket" "foo" {
bucket = "my-versioning-bucket"
acl = "private"
object_lock_configuration {
object_lock_enabled = true
rule {
default_retention {
mode = "GOVERNANCE"
days = 30
}
}
}
} resource "aws_s3_bucket_object" "foo" {
bucket = "my-versioning-bucket"
key = "important-data.txt"
retention {
mode = "GOVERNANCE"
retain_until_date = "2020-01-05T00:00:00.000Z"
}
legal_hold {
status = "ON"
}
} |
Support for S3 object lock configuration in the For tracking |
This has been released in version 1.56.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
Hi,
As of current moment - v0.11.11 - one cannot simply configure S3 Object Lock as a part of object
versioning
configuration or otherwise.Being able to set Retention Modes - Governance and Compliance is crucial for some businesses, that are prone to regulatory constraints.
Potential Terraform Configuration
Something like
retention_mode
inversioning
sectionThe text was updated successfully, but these errors were encountered: