Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

c5d.24xlarge is not supported #954

Closed
yumex93 opened this issue Dec 9, 2019 · 0 comments · Fixed by #958
Closed

c5d.24xlarge is not supported #954

yumex93 opened this issue Dec 9, 2019 · 0 comments · Fixed by #958
Assignees
Labels

Comments

@yumex93
Copy link

yumex93 commented Dec 9, 2019

Summary

I tried to call ecs-cli up with instance type c5d.24xlarge, however, it gives me the error

Error executing 'up': ValidationError: Parameter EcsInstanceType failed to satisfy constraint: must be a valid EC2 instance type.\n\tstatus code: 400, request id: ea84537f-2e77-4467-9a4d-6c634490dc03

However, when I try to launch container instance from console, this type is supported.

Seems it is due to in the cloud formation template, this type is not added to your hardcoded allowed value list.

Can you update the list to include the newest EC2 instance types?

Description

  • Which specific command was run?
ecs-cli up --instance-type c5d.24xlarge --region eu-west-1 --image-id ami-0f1670c2113013c34 ...
  • Which version of the CLI you are using? (Run: ecs-cli --version)
  • Which version of Go are you using? (Run: go version)
  • What platform are you using to run ECS CLI commands? (E.g. Linux, macOS, Windows)

Config files

  • docker-compose.yml

  • ecs-params.yml

  • ~/.ecs/config

Expected Behavior

The cluster can be successfully created.

Observed Behavior

Error executing 'up': ValidationError: Parameter EcsInstanceType failed to satisfy constraint: must be a valid EC2 instance type.\n\tstatus code: 400, request id: ea84537f-2e77-4467-9a4d-6c634490dc03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants