You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, construct names are limited to only alphanumeric characters. This was due to coupling we had between construct names and CloudFormation resource logical IDs. But this has changed, since now we have a transformation function that takes a construct's path and allocates a logical ID for it. This means that we can now relax our constraints for construct names to anything other than "/" (which represents that path separator). This is useful since it is becoming increasingly common to reuse the name for other things (i.e. domain names in HostedZones, singleton unique id of a custom resource lambda function, etc).
The text was updated successfully, but these errors were encountered:
At the moment, construct names are limited to only alphanumeric characters. This was due to coupling we had between construct names and CloudFormation resource logical IDs. But this has changed, since now we have a transformation function that takes a construct's path and allocates a logical ID for it. This means that we can now relax our constraints for construct names to anything other than "/" (which represents that path separator). This is useful since it is becoming increasingly common to reuse the name for other things (i.e. domain names in HostedZones, singleton unique id of a custom resource lambda function, etc).
The text was updated successfully, but these errors were encountered: