Creating a new S3 Bucket with ObjectLockConfiguration can lead to Cloudformation stuck in CREATE_IN_PROGRESS, and eventually giving up with "Internal Error".
The bucket actually creates successfully, but Cloudformation thinks something went wrong. Per the docs, there are redundant properties (ObjectLockConfiguration.ObjectLockEnabled, and ObjectLockEnabled).
Expected behavior
Cloudformation should acknowledge that the bucket was created successfully.
Scope of request
Creating a new S3 Bucket with ObjectLockConfiguration can lead to Cloudformation stuck in CREATE_IN_PROGRESS, and eventually giving up with "Internal Error".
The bucket actually creates successfully, but Cloudformation thinks something went wrong. Per the docs, there are redundant properties (ObjectLockConfiguration.ObjectLockEnabled, and ObjectLockEnabled).
Expected behavior
Cloudformation should acknowledge that the bucket was created successfully.
Suggest specific test cases
Example bad request:
Example good request:
Since only the latter actually works, perhaps remove the former?
Helpful Links to speed up research and evaluation
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-bucket-objectlockconfiguration.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-bucket.html#cfn-s3-bucket-objectlockenabled
Category (required) - Will help with tagging and be easier to find by other users to +1
Storage S3