[New Data Source] aws_s3_bucket_replication_configuration

[tabito-hara]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Description

• Added a new data source: aws_s3_bucket_replication_configuration, backed by the GetBucketReplication API

• The schema is identical to that of the aws_s3_bucket_replication_configuration resource, except for the and block within the filter block.

  • While this block is defined as a map in the resource, it is implemented as a block with key and value arguments in the data source, to better align with the API response structure.

Relations

Closes #42028

References

GetBucketReplication API

Output from Acceptance Testing

$ make testacc TESTS=TestAccS3BucketReplicationConfigurationDataSource_ PKG=s3
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.9 test ./internal/service/s3/... -v -count 1 -parallel 20 -run='TestAccS3BucketReplicationConfigurationDataSource_'  -timeout 360m -vet=off
2025/05/18 14:11:50 Initializing Terraform AWS Provider...
=== RUN   TestAccS3BucketReplicationConfigurationDataSource_basic
=== PAUSE TestAccS3BucketReplicationConfigurationDataSource_basic
=== CONT  TestAccS3BucketReplicationConfigurationDataSource_basic
--- PASS: TestAccS3BucketReplicationConfigurationDataSource_basic (33.11s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/s3 37.194s

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.