docs(s3): update documentation for more context around autoDeleteObjects

[SankyRed]

Issue # (if applicable)

29873

Description of changes

This the documentation update to notify users that upon setting the autoDeleteObjects to true we would also add a new policy s3:PutBucketPolicy to handle race conditions.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[colifran]

See my comment. We need to give more context behind why the s3:PutBucketPolicy is being added.

[SankyRed]

See my comment. We need to give more context behind why the s3:PutBucketPolicy is being added.

Updated the readme to provide more context around why the policy is being added. Please take a look when you get some time @colifran

[colifran]

A few verbiage suggestions and then this will be good to go.

[SankyRed]

A few verbiage suggestions and then this will be good to go.

Updated the docs, thanks @colifran

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 1dcc318
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).