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
We'd like to be able to have a human-friendly "fully-qualified" name for all AWS resources. For example, suppose a service is organized hierarchically by:
Stage
Region
Cell
We'd like to name a stack my-service.us-east-1.cell-0.my-stack, where period is used as the separator between level fragments.
Using fully qualified names lets us deploy multiple copies of a service into the same account during development (e.g. have cell 0 and cell 1 in the same personal development account).
Currently we have to use something like -- as the separator which can be difficult to read. For example, my-service--us-east-1--cell-0--my-stack.
The text was updated successfully, but these errors were encountered:
Name of the resource
AWS::CloudFormation::Stack
Resource name
No response
Description
Support more character types in stack names.
Cfn stacks are currently limited to 128 alphanumeric and dash characters. We'd like it expanded to include periods and other symbols.
Matching what's allowed for IAM role names would be preferred (alphanumerics and
_+=,.@-
).https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html#cfn-iam-role-rolename
Other Details
We'd like to be able to have a human-friendly "fully-qualified" name for all AWS resources. For example, suppose a service is organized hierarchically by:
We'd like to name a stack
my-service.us-east-1.cell-0.my-stack
, where period is used as the separator between level fragments.Using fully qualified names lets us deploy multiple copies of a service into the same account during development (e.g. have cell 0 and cell 1 in the same personal development account).
Currently we have to use something like
--
as the separator which can be difficult to read. For example,my-service--us-east-1--cell-0--my-stack
.The text was updated successfully, but these errors were encountered: