Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-9869

Support custom DNS in the AWS Bitbucket Server template

XMLWordPrintable

    • 0
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, using a custom DNS with ELB requires hardcoding the domain name in the template, as follows:

      ATL_PROXY_NAME=<domain-name>

      Custom DNS should be made available without having to modify the template in this manner.

            [BSERV-9869] Support custom DNS in the AWS Bitbucket Server template

            Ishwinder Kaur (Inactive) added a comment -
            Atlassian Update - 15 April 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues.

            Kind regards,
            Bitbucket Data Center

            Ishwinder Kaur (Inactive) added a comment - Atlassian Update - 15 April 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues . Kind regards, Bitbucket Data Center

            Tech-DPE added a comment - - edited

            My use case:

            I want to use a custom domain mycompany.com. I have uploaded our SSL cert into AWS and reference it. Problem is that Bitbucket redirects to the AWS ELB DNS name so there is no way to get a "secure" (correct cert) SSL connection without hardcoding the URL in the CloudFormation template, which is not so pretty.

            As far as I can see there is no workaround with Route 53 or something else since this is done inside Bitbucket.

            Tech-DPE added a comment - - edited My use case: I want to use a custom domain mycompany.com . I have uploaded our SSL cert into AWS and reference it. Problem is that Bitbucket redirects to the AWS ELB DNS name so there is no way to get a "secure" (correct cert) SSL connection without hardcoding the URL in the CloudFormation template, which is not so pretty. As far as I can see there is no workaround with Route 53 or something else since this is done inside Bitbucket.

            Jesse Rehmer [Contegix] added a comment -

            Not everyone wants to use Route 53 for DNS.  It needs to be set properly so the Tomcat HTTP connector settings contain the correct proxyName.

            Jesse Rehmer [Contegix] added a comment - Not everyone wants to use Route 53 for DNS.  It needs to be set properly so the Tomcat HTTP connector settings contain the correct proxyName.

            Roger Barnes (Inactive) added a comment -

            What purpose does setting this serve? Our thinking is that Route 53 can handle DNS, but perhaps we're missing something in the internals that requires this to be set.

            Roger Barnes (Inactive) added a comment - What purpose does setting this serve? Our thinking is that Route 53 can handle DNS, but perhaps we're missing something in the internals that requires this to be set.

              Unassigned Unassigned
              smaruvada Shashank Maruvada (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: