Use Stack ID for OriginAccessControl.Name property #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Fixes #67 and #66
Description of changes:
OriginAccessControl.Name
propertyThe template fails to deploy when the stack name is longer than 64 characters. The
OriginAccessControlConfig
resource fails to create, with a genericInvalidRequest
error. TheName
property has. a max length of 64 characters.The
OriginAccessControlConfig.Name
property was set to!Sub oac-${AWS::StackName}-${AWS::Region}'.
For sufficiently long stack names (including the default stack name), this triggered the bug described above.OriginAccessControlConfig
resources must have a unique name across all regions for an account. To ensure this, the
Name` property was derived from both the StackName and Region. The max length of a stack name is 128 characters. This is longer than the 64 characters allowed by the OACConfig Name property.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.