AWS Confluence DC CloudFormation Template: could be able to resolve EFS not only via DNS but also IP

XMLWordPrintable

      Problem Definition

      It's not possible to deploy an Internal Facing Confluence DC on AWS using the quick start CloudFormation template when using own DNS Server.

      This happens because the template uses the DNS to mount the EFS into the new Confluence Node, so the two conditions on EC2 to use the EFS via DNS are:

      1. The connecting EC2 instance must be inside a VPC and must be configured to use the DNS server provided by Amazon. For information about Amazon DNS server, see DHCP Options Sets in the Amazon VPC User Guide.
      2. The VPC of the connecting EC2 instance must have DNS host names enabled. For more information, see Viewing DNS Hostnames for Your EC2 Instance in the Amazon VPC User Guide.

      Suggested Solution

      Make it possible to deploy Confluence DC using our own DNS Server.

      Why this is important

      Currently we can only deploy internet-facing datacenters, but most of the companies need to deploy dev/staging instances too, that should be accessed internally only due to security policies.

      Workaround

      Currently the only workaround is to use the AWS DNS server instead.

            Assignee:
            Duy Truong Luong
            Reporter:
            Eduardo Mallmann (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: