Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

How to extend the g5 capacity limitation with gp2

0

I deployed a docker image in an EC2 instance, and made AMI and Launch Templates, which to be used to build a Auto Scaling Group, and encountered the following error when do auto-scaling:

Launching a new EC2 instance. Status Reason: We currently do not have sufficient g5.xlarge capacity in zones with support for 'gp2' volumes. Our system will be working on provisioning additional capacity. Launching EC2 instance failed.

I can startup 6 instances at most, further instance will be failed, no matter by auto-scaling or mannually. It seems that there are some limitation on instance type and volumn type, but I couldn't find where to set, I have tried to update the quota of

Storage for General Purpose SSD (gp2) volumes, in TiB

but it doesn't work, is there any way to extend the limitation? Thanks!

Topics
Management & GovernanceComputeStorage
Tags
Amazon EC2Amazon Elastic Block StoreAWS Auto Scaling
Language
English

asked 2 years ago660 views

1 Answer
1

Hello.

Since that error is a capacity problem on the AWS side rather than an EC2 quota, I think that in order to avoid it from the user side, it is necessary to start it after a while or use a different instance type or availability zone.
https://docs.aws.amazon.com/autoscaling/ec2/userguide/ts-as-instancelaunchfailure.html#ts-as-capacity-1

Wait a few minutes for Amazon EC2 Auto Scaling to find capacity for this instance type in other enabled Availability Zones.
Expand your Auto Scaling group to additional Availability Zones. For more information, see Add and remove Availability Zones.
Follow the best practice of using a diverse set of instance types so that you're not reliant on one specific instance type. For more information, see Auto Scaling groups with multiple instance types and purchase options.

EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

  • hanming
    2 years ago

    Thanks for your reply! Do you mean that the instance pool of g5 type in current avaliable zone was used up when I requested to create new instance? Actually we built similar cluster with g4dn instances and never encountered this problem, can we assume that there are more resource for g4dn than g5?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content