AWS CDK - how does one debug a hanging deploy?

Question

There are times when I run cdk deploy and it will get to creating a ECS service and just hang because I did "something" wrong with my config --

55/57 Currently in progress: MyServiceFA17513E

Is there any way to get insight into what the problem is? It seems to take quite long to timeout (hour+?)

Go to CloudFormation console and check out the stack that is creating — Oleksii Donoha, May 01 '20 at 09:39
Thanks @Marcin that's what I was looking for. Now I'm able to see, >service my-service was unable to place a task because no container instance met all of its requirements. The closest matching container-instance abbb7c1b-... has insufficient memory available — Dylan, May 01 '20 at 14:54
can you post your configuration? so we can see what you are doing right now and hopefully come up with a solution. — Jonny Rimek, May 01 '20 at 18:25
Yes issue solved. @JonnyRimek I wasn't worried about the configuration necessarily, more the process of how to debug when you run into a situation like this. — Dylan, May 02 '20 at 12:27
can you layout your solution pls? I'm having a similar problem — Jonny Rimek, May 03 '20 at 10:14
@JonnyRimek in my case I needed to allocate less memory to my containers so they could fit in the ec2 instance (or bump up the ec2 instance size) — Dylan, May 04 '20 at 15:41
interesting, my issue was caused because I disabled the NATGateway, afaik. I'm 90% sure^^ — Jonny Rimek, Aug 05 '20 at 14:37

score 15 · Accepted Answer · answered Jun 16 '21 at 19:14

15

You can run your command with the verbose parameter to get more details cdk deploy -vv

answered Jun 16 '21 at 19:14

Melissa Guo

1 Answers1