aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::S3::Bucket] - [BUG] - Stack event history not logging updates to S3 bucket UpdateReplacePolicy attribute
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::S3::Bucket
### Resource Name
_No response_
### Issue Description
Cloudformation does not log/display UPDATE_FAILED or UPDATE_COMPLETE events for S3 buckets that have the UpdateReplacePolicy attribute changed via change set. This is different from the behavior observed for DeletionPolicy attribute changes, which do log events.
### Expected Behavior
| Timestamp | Logical ID | Status |
| ------------ | ----------- | ------- |
| ### | STACK_NAME | UPDATE_COMPLETE |
| ### | STACK_NAME | UPDATE_COMPLETE_CLEANUP_IN_PROGRESS |
| ### | BUCKET_RESOURCE | UPDATE_COMPLETE |
| ### | STACK_NAME | UPDATE_IN_PROGRESS |
### Observed Behavior
| Timestamp | Logical ID | Status |
| ------------ | ----------- | ------- |
| ### | STACK_NAME | UPDATE_COMPLETE |
| ### | STACK_NAME | UPDATE_COMPLETE_CLEANUP_IN_PROGRESS |
| ### | STACK_NAME | UPDATE_IN_PROGRESS |
### Test Cases
Execute a change set with an existing bucket which sets or changes the UpdateReplacePolicy attribute
### Other Details
_No response_
Contributor guide
Research direction
No source files, entry points, or automated tests are identified in the issue. Start by executing a change set on an existing AWS::S3::Bucket that sets or changes UpdateReplacePolicy, compare its stack event history with a DeletionPolicy change, and consider the work done when the expected bucket update events are logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100