aws / aws/ec2-image-builder-roadmap

Support More Character Types in Resource Names

Open
#106 0 comments 0 reactions 0 assignees View on GitHub
Proposed
Dominant language
No language data
Stars
35
Forks
7
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

Support more character types in resource names.

Image Builder resources are currently restricted to 128 alphanumeric, space, 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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

We'd like to be able to have a human-friendly "fully-qualified" name for AWS resources. For example, suppose a service is organized hierarchically by:

1. Stage
2. Region
3. Cell

We'd like to name a resource `my-service.us-east-1.cell-0.resource-name`, 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).

**Are you currently working around this issue?**

Using space as the fragment separator (e.g. `my-service us-east-1 cell-0 resource-name`).

This is fine, but we'd like to use a consistent separator across all AWS resources.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the AWS Image Builder resource-name constraints described here and compare them with the linked IAM role-name rules. No repository files or tests are identified; done would mean Image Builder accepts periods and the requested IAM-compatible characters in resource names.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.