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

[Enhancement]: aws_s3_bucket_intelligent_tiering_configuration support to skip archive access tierings #37077

Open
inka opened this issue Apr 24, 2024 · 1 comment · May be fixed by #37957
Open
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service.

Comments

@inka
Copy link

inka commented Apr 24, 2024

Description

https://aws.amazon.com/s3/storage-classes/intelligent-tiering/
allows to use "instant access" tiering classes (enabled automatically) and asynchronous "archive access" tiering classes.

The asynchronous classes are optional opt-ins. So from AWS console it's perfectly possible to use intelligent tiering without having archive or deep archive access enabled.

This is not possible via the terraform resource yet as the "tiering" block can not be skipped.

AWS Provider Version
5.46.0

Affected Resource(s) and/or Data Source(s)

  • aws_s3_bucket_intelligent_tiering_configuration

Potential Terraform Configuration

resource "aws_s3_bucket" "bucket" {
  bucket        = "bucket"
}

resource "aws_s3_bucket_intelligent_tiering_configuration" "bucket_intelligent_tiering" {
  bucket = aws_s3_bucket.bucket.bucket
  name   = "intelligent-tiering"

  #tiering {
  #  access_tier = "ARCHIVE_ACCESS"
  #  days        = 370
  #}
}

References

No response

Would you like to implement a fix?

No

@inka inka added the enhancement Requests to existing resources that expand the functionality or scope. label Apr 24, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/s3 Issues and PRs that pertain to the s3 service. label Apr 24, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Apr 24, 2024
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Apr 26, 2024
@dhpollack dhpollack linked a pull request Jun 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants