https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
m
I’m not sure what the best thing to look for here is - after quite a few minutes the error reports: 
* error waiting for service (arn:aws:ecs:eu-west-1:463234216787:service/picnic-staging-c3fd3bc/picnic-staging-server-8563e16) to reach a steady state: ResourceNotReady: exceeded wait attempts
b
Hi @most-address-4174 This suggests that the service isn't getting marked as healthy and ECS is continually trying to restart it If you go to ECS in the AWS console, you may get a wee bit more information about why this is as part of your service logs I would suggest it's that the container isn't starting correctly
m
Hey @broad-dog-22463 thank you for the response! I’m not sure if you have any pointers, but in the ECS dashboard the EC2 instance doesn’t seem to connect - it shows 
0
container instances. On the EC2 dashboard, I only see 1 instance that’s unnamed, but I think that’s the ECS cluster instance
b
Can you show me your infra code that spins this up?
m
Yep!
Sorry if this is horribly awry - I’m still learning through the AWS setup 🙂
index.ts
@broad-dog-22463 for context, everything seems to be creating except that EC2 instance:
@broad-dog-22463 Sorry to bother you, do you have any idea what could be going wrong in that config to cause the service to hang on creation?
10 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by