Task is not coming up due to Insufficient IP Address available under stubnet

Question

Hi
The task is not coming up for One of our ECS container services due to "insufficient free addresses in subnet" issue (PFA). When I click on "Deployments" tab, two tasks are visible - 1) Primary (last deployment as "in progress") 2) Active (last deployment as "Completed", Revision as "Inactive). Upon clicking on the primary task, it shows status as "DELETE_IN_PROGRESS" and stuck there. Not sure how to ensure its deletion and ensure it releases the IP which can be used by another task. I cannot delete it forcibily or stop the deletion to make it active as actions are disabled for this.

Could you plz advise how to fix this issue? My infra expert says, we can start the task assigning it a different subnet id but that is not so easy as same subnet id is being used by many resources through cloud formation scripts. I want a manual solution to this so I get a healthy system back.

Thanks.

Steve_M · Answer

The AWS re:Post community doesn't have access to your account, and nobody contributing here is able to view (or change) the state of any services within your account.

If you have a paid-for support plan then your best option is to log support call about this https://console.aws.amazon.com/support/plans/home#/

If you are on a basic support plan then the AWS re:Post community may be able to help if you can provide more details of your problem here.

You're also advised to edit your question to remove your account number and phone number, as posts on re:Post are not private.

iBehr · Answer

If you are out of IPs in the subnet, you either have to:
- stop resources using IPs in the subnets to free them up for use by new resources
- specify a different subnet that has IPs available
- create a new subnet and specify to use that new subnet.

There is no magic to solve the out of IPs in a particular subnet issue.

Hope this helps.

Task is not coming up due to Insufficient IP Address available under stubnet

関連するコンテンツ