Confluence AWS Quick start 502 Bad Gateway

last week i deployed the aws quick start with confluence datacenter and everything worked perfect. Today I updated the stack to allow the bastion connection but when I updated the autoscaling and the new instance was generated, this new one did not have confluence configured.
From there any instance that I deploy from that stack comes without the confluence and if I try to connect it obviously goes 502 bad gateway.

Any ideas?

Thank you

1 Like

We are also facing 502 Bad Gateway error.
We found this error in log:

FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.7/site-packages/pip/_vendor/certifi/cacert.pem'

Also i deploy a new stack with a new confluence DC and get the same error.
Thank you

Have the same issue today. Though not with Confluence but with Jira Software. Seems that Jira isn’t installed on the ec2 instance.

here is a public ticket with manual steps how to fix [SCALE-63] Deploying AWS Quickstart Template into Existing VPC fails - Create and track feature requests for Atlassian products.