Feature: AWS Shield Advanced: DRT AccessRole ARN and Access Log Bucket Associations

[chasse-code]

Description

Add support for Shield DRT Access

• Support adding DRT Access Role Arn Association
• Support adding SRT Access Log Bucket Association

Relations

Closes #32626

Output from Acceptance Testing

make testacc  PKG=shield  TESTS=TestAccShieldDRTAccess
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/shield/... -v -count 1 -parallel 20 -run='TestAccShieldDRTAccess'  -timeout 180m
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_basic
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_basic (14.07s)
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_multibucket
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_multibucket (14.43s)
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_disappears
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_disappears (14.08s)
=== RUN   TestAccShieldDRTAccessRoleArnAssociation_basic
--- PASS: TestAccShieldDRTAccessRoleArnAssociation_basic (12.37s)
=== RUN   TestAccShieldDRTAccessRoleArnAssociation_disappears
--- PASS: TestAccShieldDRTAccessRoleArnAssociation_disappears (13.10s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/shield     71.329s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccShieldDRTAccessLogBucketAssociation_' PKG=shield
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/shield/... -v -count 1 -parallel 20  -run=TestAccShieldDRTAccessLogBucketAssociation_ -timeout 180m
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_basic
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_basic (26.00s)
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_multibucket
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_multibucket (27.42s)
=== RUN   TestAccShieldDRTAccessLogBucketAssociation_disappears
--- PASS: TestAccShieldDRTAccessLogBucketAssociation_disappears (26.76s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/shield	85.920s

% make testacc TESTARGS='-run=TestAccShieldDRTAccessRoleARNAssociation_' PKG=shield
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/shield/... -v -count 1 -parallel 20  -run=TestAccShieldDRTAccessRoleARNAssociation_ -timeout 180m
=== RUN   TestAccShieldDRTAccessRoleARNAssociation_basic
--- PASS: TestAccShieldDRTAccessRoleARNAssociation_basic (33.17s)
=== RUN   TestAccShieldDRTAccessRoleARNAssociation_disappears
--- PASS: TestAccShieldDRTAccessRoleARNAssociation_disappears (20.86s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/shield	66.069s

[ewbankkit]

@chasse-code Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v5.16.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.