CloudFormation Template Hangs on Install?
I've been having troubles with my (old, cloud hosted, perennially upgraded, and not optimally set up) TeamCity server. So I decided to try the AWS CloudFormation. After requesting more IP's because of the first rollback, it looks like the ECS service is not notifying the CloudFormation template that it is finished installing. This may be due to the warning I get in the ECS service that the containers aren't running the most recent version of the AWS ContainerAgent. Is there a maintainer to the CloudFormation?
It seems to have been stuck in (CREATE_IN_PROGRESS) for around an hour because the ECS service isn't checking back in with the creation process.
What do I do at this point? Just leave it half-finished and go about my business figuring out how to set the rest of it up?
Ideally, I would have a single C5 large instance running the default agent, and ECS services running build agents as cheaply as possible when the default agent was busy. Is there a tutorial or anything to walk me through setting this up?
Please sign in to leave a comment.
Note: the CloudFormation install rolled back in the end, with the error:
Service arn:aws:ecs:us-west-2:service/TeamCityCloudFormation_TeamCityAgents did not stabilize.
I believe this has to do with my IAM setup. The tutorial here: https://confluence.jetbrains.com/display/TCD18/Running+TeamCity+Stack+in+AWS says I need to create a service-linked IAM role. Not sure whether this is the case.
Still would be open to commentary of any kind.
Okay, I tried it a third time and it worked. Surprising, but I'll take it.
I'm having the same issue. I've tried four times and even tried creating the service-linked IAM role. It is still showing CREATE_IN_PROGRESS for the 2 TCServerNodeService services.