AWS CloudFormation results in 503 Service Temporarily Unavailable

Hi all,

I am evaluating TeamCity for my organisation as we consider migrating from Jenkins.

I used the AWS CloudFormation template to set everything up. The Stack is successfully created. When I try to navigate to the URL specified in the Stack's Output, I get a 503 Service Temporarily Unavailable message.

I have little experience with AWS in general, but I noticed in the ECS overview that the MainNode service is not starting. The log is full of repeating entries:

• service TeamCity_TeamCityServer_MainNode deregistered 1 targets in target-group ...
• service TeamCity_TeamCityServer_MainNode has started 1 tasks: task ...
• service TeamCity_TeamCityServer_MainNode has begun draining connections on 1 tasks.
• service TeamCity_TeamCityServer_MainNode deregistered 1 targets in target-group ...
• service TeamCity_TeamCityServer_MainNode has started 1 tasks: task ...
• service TeamCity_TeamCityServer_MainNode has begun draining connections on 1 tasks.

So from what I can tell, the main server node is unable to start properly...

Has anyone encountered a similar issue before? Or could anyone point me in the right direction to get to the root cause of this issue?

Kind regards,

Jonas