Issue

E3 currently uses the Atlassian internal templates in the atlassian-aws-deployment repo for provisioning. However, it seems like the templates have recently undergone major changes, i.e. naming and parameters which E3 depends on. Out-of-the-box, E3 will fail to access the templates because of naming changes and "fall back" to trying to pull the templates from S3, which shouldn't happen. If E3 is forced to point to the atlassian-aws-deployment templates, provisioning will be unsuccessful.

Workaround

Update e3.yaml to use the stable public AWS CloudFormation repo for provisioning:

template_url: https://raw.githubusercontent.com/aws-quickstart/quickstart-atlassian-confluence/develop/templates