r/s3_bucket_intelligent_tiering_configuration: New Resource

[daniepett]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #16123

Example

resource "aws_s3_bucket_intelligent_tiering_configuration" "example" {
  bucket = "my-bucket-name"
  name   = "example-tier"

  filter {
    prefix = "test/"

    tags = {
      name = "example"
    }
  }

  tier {
    access_tier = "DEEP_ARCHIVE_ACCESS"
    days        = 180
  }

  tier {
    access_tier = "ARCHIVE_ACCESS"
    days        = 125
  }

}

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSS3BucketIntelligentTieringConfiguration_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSS3BucketIntelligentTieringConfiguration_ -timeout 180m
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_basic
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_basic
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_removed
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_removed
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_disableBasic
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_disableBasic
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_updateBasic
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_updateBasic
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Empty
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Empty
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Prefix
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Prefix
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_SingleTag
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_SingleTag
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_MultipleTags
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_MultipleTags
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_PrefixAndTags
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_PrefixAndTags
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Remove
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Remove
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithTier_Empty
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithTier_Empty
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_Default
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_Default
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithOneTier_UpdateDays
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithOneTier_UpdateDays
=== RUN   TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_RemoveOne
=== PAUSE TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_RemoveOne
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_basic
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_PrefixAndTags
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Remove
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Empty
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_MultipleTags
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_SingleTag
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Prefix
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithOneTier_UpdateDays
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_RemoveOne
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithTier_Empty
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_Default
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_updateBasic
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_disableBasic
=== CONT  TestAccAWSS3BucketIntelligentTieringConfiguration_removed
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithTier_Empty (24.26s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Empty (24.97s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_basic (94.91s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_Default (98.00s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_removed (134.45s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_disableBasic (149.40s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_SingleTag (153.90s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithTwoTiers_RemoveOne (153.95s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_MultipleTags (155.14s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Prefix (156.40s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_Remove (156.61s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithOneTier_UpdateDays (156.62s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_WithFilter_PrefixAndTags (156.68s)
--- PASS: TestAccAWSS3BucketIntelligentTieringConfiguration_updateBasic (203.35s)
PASS
ok      github.com/terraform-providers/terraform-provider-aws/aws       205.230s
...

[KVInventoR]

how will be it work if you setup many policies for different folders?

I think configuration for specific folder should in included in namespace for this folder.

[zhelding]

Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding.

Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single aws directory to a large number of separate directories in internal/service, each corresponding to a particular AWS service. This separation of code has also allowed for us to simplify the names of underlying functions -- while still avoiding namespace collisions.

We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author.

For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000.

For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide.

[ewbankkit]

LGTM 🚀.

Commercial

% make testacc PKG_NAME=internal/service/s3 TESTARGS='-run=TestAccS3BucketIntelligentTieringConfiguration_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 20 -run=TestAccS3BucketIntelligentTieringConfiguration_ -timeout 180m
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_basic
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_basic
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_disappears
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_disappears
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_Filter
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_Filter
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_basic
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_Filter
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_disappears
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_disappears (25.23s)
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_basic (27.99s)
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_Filter (107.78s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/s3	111.337s

GovCloud

% make testacc PKG_NAME=internal/service/s3 TESTARGS='-run=TestAccS3BucketIntelligentTieringConfiguration_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 20 -run=TestAccS3BucketIntelligentTieringConfiguration_ -timeout 180m
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_basic
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_basic
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_disappears
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_disappears
=== RUN   TestAccS3BucketIntelligentTieringConfiguration_Filter
=== PAUSE TestAccS3BucketIntelligentTieringConfiguration_Filter
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_basic
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_Filter
=== CONT  TestAccS3BucketIntelligentTieringConfiguration_disappears
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_disappears (28.16s)
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_basic (31.24s)
--- PASS: TestAccS3BucketIntelligentTieringConfiguration_Filter (126.74s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/s3	130.097s

[ewbankkit]

@daniepett Thanks for the contribution 🎉 👏.

[ewbankkit]

% make golangci-lint
==> Checking source code with golangci-lint...

[github-actions]

This functionality has been released in v3.65.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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 issues.
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.