Summary

When requiring an SSL connection between Synchrony and the AWS Elastic Load Balancer, the default configuration returns an Amazon SSL certificate instead of the customer's domain certificate. This can cause Synchrony to stop connecting.

Environment

• Confluence Data Center deployed to AWS via template

Workaround

• Manually edit /etc/atl file to change ATL_SYNCHRONY_SERVICE_URL to point to the customer's domain instead of the ELB FQDN

Proposed Solution

• Change the Confluence Data Center template to set ATL_SYNCHRONY_SERVICE_URL to use ATL_PROXY_NAME instead of the LoadBalancerName