BitBucket and Jira Not Acessible After Deploying into Existing ASI using AWS Quickstart

[Lawrence Davis]

I am attempting to use the Atlassian Quickstart CloudFormation templates to build our BitBucket, Confluence, & Jira servers. We've done the following:

1. Deployed the Confluence quickstart using option #1 (Jira in a new ASI using end to end deployment). Once the CloudFormation stack is complete we're able to access the Confluence configuration page via the classic load balancer.

      2. Deployed both the Jira and the BitBucket quickstarts using option #2 (Deploy into an              existing ASI).

The Confluence & Bitbucket configuration pages are not accessible after the CloudFormation template has been run and the load balancers for both services report the instances are "out of service".

I've attempted to run the templates in two separate regions (West Oregon & East Virginia) with the exact same result. In particular, in the East Virginia region the Cloudformation templates were deployed and none of the default parameters were changed. We're always able to connect to the Atlassion product that gets deployed with quickstart option #1 (new ASI ie. VPC). Any subsequent products (bitbucket/confluence) which are deployed into an existing ASI using quickstart option#2 cannot be accessed and show as "out of service" on the load balancers.

Has anyone run into this situation before and resolved it? 

[Lawrence Davis]

I found another suggestion from @[deleted]-dennis which helped me get Confluence running (terminated the instances and let autoscaling replace them with new ones). They're now accessible via the load balancer. However, Bitbucket is still not accessible and I receive the following message when I go the the URL of the instance directly: 

"Your Atlassian instance is starting. If you suspect there is a problem with the installation you can look at the install log at /var/log/atl.log"

Unfortunately that file does does not exist on the bitbucket server that was created by the quickstart.