Environment name with alphanumerics and numbers

[cptflammin]

Currently only supported lower case letters. As we may have by example different use case environments (dev, alpha, beta, test (qualification), prod, demo1, demo2...) and regions (us-west1, eu-central-1...), it would be better being able to name them

eu-central-1_dev
us-west-2_demo1
etc...

[biddster]

While we're doing this, can we make environment names longer please? 10 chars is pretty limiting!

[AustinDeric]

I too would like this feature. We use amplify and we like to match our git branch name with the environment name. Cloudformation can handle numbers, letters and dashes so i don't see why amplify can't as well.

[jcvalerio]

We need this too, we use git-flow in our development process and as @AustinDeric we need to match the branch name with the environment, currently, we have to perform some transformations on our CI process to address this limitation.

👍

[melodymorgan]

Is there any movement on this? The limitation is a real bummer.

[alexkates]

Any updates here? Seems like something that should be supported...

[cnegrisanu]

Hi guys,

This is really needed. It is nice to use the full CI/CD pipeline but as others have mentioned, when using the feature branching model from gitflow with feature names based on Jira issues it is very limiting accepting only alphas in the naming and only supporting 10 chars. Why is there a feature and release branch auto-detection option for in the Amplify Console? It totally defeats the purpose.

All my feature branches are failing at the Build stage with error:
Environment name should be between 2 and 10 characters (only lowercase alphabets).

Please help us with this! @undefobj
Thanks!

[fsjodininfrapros]

Another vote to have this addressed, the usefulness of automatic builds for feature branches is greatly diminished with such severe limitations on the branch names

[PTaylour]

Another related use-case for you.

At the moment it's not possible to use the AppSync @function directive with a lambda function that has an underscore in the name.

Template format error: Resource name ScopingAPIDevRun_embedding_suggestionsLambdaDataSourceRole is non alphanumeric.

This issue also looks to be related #2526

I can make this a separate issue if you'd prefer

[maximelebastard]

Hey, same issue for us. We use jira which has tickets ids like "PROJECT-123".
We'd love to be able to create environments for these tickets, named like project123.

[adi518]

Ridiculous error. It renders the feature branch feature almost useless. These don't work:

• e2e
• foo-bar

[rush86999]

would love to see an update on this

[nwmahoney]

Any updates on this?

[hackmajoris]

I'm strongly assume that this issue appears just on remote CI/CD, and the reason is that you use the amplifyPush script: https://github.com/aws-amplify/amplify-hosting/blob/main/scripts/amplifyPush.sh

The workaround:
use amplifyPush --simple flag

For the Amplify Team: I think the solution is lowercase and exclude all the special characters from that ${ENV} variable in the script.

[yitzhaktal]

Can be really useful to me as well :)