Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

Ensure long IAM names do not cause failed deployments #7

Closed
jpignata opened this issue May 10, 2017 · 2 comments · Fixed by #9
Closed

Ensure long IAM names do not cause failed deployments #7

jpignata opened this issue May 10, 2017 · 2 comments · Fixed by #9

Comments

@jpignata
Copy link
Contributor

[05/10/17 12:26 PM] Pierre: one thing: the first time I ran, I called the whole stack john-ecs-cd
[05/10/17 12:27 PM] Pierre: and this made CodeDeploy fail because the deployment CFn stack failed because the IAM role name was longer than 64 chars
@steckmey
Copy link

Pedantic accuracy: the stack name was actually johns-ecs-cd

@jpignata jpignata mentioned this issue May 14, 2017
Merged
@jpignata
Copy link
Contributor Author

I wasn't able to get this to fail with johns-ecs-cd, but really-long-stack-name-trying-to-cause-errors did break the IAM resources created. #9 should resolve this issue. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't fail if user chooses long stack name awslabs/ecs-refarch-continuous-deployment
2 participants
@jpignata @steckmey