aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Cloudformation: Inconsistent name length restrictions

Open
#888 2 comments 4 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

As we are building more of our infrastructure via cloudformation we are running into instances where different resources have different name length restrictions. Here are some examples that we've come across, and they range from a maximum of 32 to some allowing over 400 characters.

Target group name:
A maximum of 32 alphanumeric characters including hyphens are allowed, but the name must not begin or end with a hyphen.

RDS:
The DB cluster identifier is case-insensitive, but is stored as all lowercase (as in "mydbcluster"). Constraints: 1 to 60 alphanumeric characters or hyphens. First character must be a letter. Can't contain two consecutive hyphens. Can't end with a hyphen.

CloudWatch Event Rule Name:
Details: The supplied rule name is invalid. Maximum allowed length is 64.

Lambda: Function Name:
This field is too long. The maximum length is 64 characters.

DynamoDB table:
Between 3 and 255 characters long.

Rest Api Gateway:
Not sure of the length, but it can take over 400 characters.

The inconvenience this causes us is to be able to set a standard naming convention across all resource types. Ideally we would like to be able to name a domain stack of resources in a way which identifies them easily.

We also suffix the name with the environment they are deployed in (dev, test, sandbox, prod).
The other issue is as we deploy our resources into the dev account, everything would be fine. But in sandbox it fails as it has crossed the max name length limit. Not all the name length limits are documented in the CloudFormation documentation.

Is there something on the roadmap for AWS to align the naming standards of the resources?

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or implementation entry point is identified. The issue documents differing AWS resource naming limits and asks whether CloudFormation will align them; it needs a concrete scope and maintainer decision before a newcomer can define a change or completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.