Table of contents

This is for internal use by the PaaS team. Public-facing documentation is located at docs.cloud.service.gov.uk.

ADR026: DNS layout for UK hosting

Context

We are moving AWS hosting from Ireland to London. This ADR contains the decisions of the DNS names we will use for apps and system components that will be hosted in London.

Decision

We will use the following domain patterns for the London hosting:

  • (system_component).london.(system_domain)
  • (app_name).london.(app_domain)

Where:

  • (system_component) – api, uaa, doppler, ssh, etc.
  • (system_domain) – cloud.service.gov.uk, staging.cloudpipeline.digital
  • (app_domain) – cloudapps.digital, staging.cloudpipelineapps.digital

The reasons are:

  • We should re-use the (system_component) first part to minimise the changes to the Cloud Foundry manifests.
  • We should re-use the (system_domain) and (app_domain) last part, because these domains are assigned to GOV.UK PaaS as the public interface.
  • The domain part london is preferrable to uk, because AWS may provide multiple-region hosting within the UK in the future.

The domain structure for the dev and CI environments won’t change. For the dev environments we will create a flag to choose where to create the deployment.

Examples

Production

Ireland London
api.cloud.service.gov.uk api.london.cloud.service.gov.uk
sample-app.cloudapps.digital sample-app.london.cloudapps.digital

Staging

Ireland London
api.staging.cloudpipeline.digital api.london.staging.cloudpipeline.digital
sample-app.staging.cloudpipelineapps.digital sample-app.london.staging.cloudpipelineapps.digital

Status

Accepted

Consequences

New tenants will be encouraged to use London hosting. Plans need to be derived to notify exiting tenants to move their apps and services to London.