Using your own domain for the hosted UI - Amazon Cognito
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Using your own domain for the hosted UI

After setting up an app client, you can configure your user pool with a custom domain for the Amazon Cognito hosted UI and auth API endpoints. With a custom domain, you enable your users to sign in to your application by using your own web address.

Adding a custom domain to a user pool

To add a custom domain to your user pool, you specify the domain name in the Amazon Cognito console, and you provide a certificate you manage with Amazon Certificate Manager (ACM). After you add your domain, Amazon Cognito provides an alias target, which you add to your DNS configuration.


Before you begin, you need:

  • A user pool with an app client. For more information, see Getting started with user pools.

  • A web domain that you own. Its parent domain must have a valid DNS A record. You can assign any value to this record. The parent may be the root of the domain, or a child domain that is one step up in the domain hierarchy. For example, if your custom domain is, Amazon Cognito must be able to resolve to an IP address. To prevent accidental impact on customer infrastructure, Amazon Cognito doesn't support the use of top-level domains (TLDs) for custom domains. For more information see Domain Names.

  • The ability to create a subdomain for your custom domain. We recommend using auth as the subdomain. For example:


    You might need to obtain a new certificate for your custom domain's subdomain if you don't have a wildcard certificate.

  • A Secure Sockets Layer (SSL) certificate managed by ACM.


    You must change the Amazon region to US East (N. Virginia) in the ACM console before you request or import a certificate.

  • An application that permits your user pool authorization server to add cookies to user sessions. Amazon Cognito sets several required cookies for the hosted UI. These include cognito, cognito-fl, and XSRF-TOKEN. Although each individual cookie conforms to browser size limits, changes to your user pool configuration might cause hosted UI cookies to grow in size. An intermediate service like an Application Load Balancer (ALB) in front of your custom domain might enforce a maximum header size or total cookie size. If your application also sets its own cookies, your users' sessions might exceed these limits. We recommend that, to avoid size limit conflicts, your application not set cookies on the hosted UI subdomain.

  • Permission to update Amazon CloudFront distributions. You can do so by attaching the following IAM policy statement to a user in your Amazon Web Services account:

    { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowCloudFrontUpdateDistribution", "Effect": "Allow", "Action": [ "cloudfront:updateDistribution" ], "Resource": [ "*" ] } ] }

    For more information about authorizing actions in CloudFront, see Using Identity-Based Policies (IAM Policies) for CloudFront.

    Amazon Cognito initially uses your IAM permissions to configure the CloudFront distribution, but the distribution is managed by Amazon. You can't change the configuration of the CloudFront distribution that Amazon Cognito associated with your user pool. For example, you can't update the supported TLS versions in the security policy.

Step 1: Enter your custom domain name

You can add your domain to your user pool by using the Amazon Cognito console or API.

Amazon Cognito console
To add your domain to your user pool from the Amazon Cognito console:
  1. Sign in to the Amazon Cognito console. If prompted, enter your Amazon credentials.

  2. Choose User pools.

  3. Choose the user pool to which you want to add your domain.

  4. Choose the App integration tab.

  5. Next to Domain, choose Actions, then choose Create custom domain.


    If you have already configured a user pool domain, choose Delete Cognito domain or Delete custom domain to delete the existing domain before creating your new custom domain.

  6. For Custom domain, enter the URL of the domain you want to use with Amazon Cognito. Your domain name can include only lowercase letters, numbers, and hyphens. Do not use a hyphen for the first or last character. Use periods to separate subdomain names.

  7. For ACM certificate, choose the SSL certificate that you want to use for your domain. Only ACM certificates in US East (N. Virginia) are eligible to use with an Amazon Cognito custom domain, regardless of the Amazon Web Services Region of your user pool.

    If you don't have an available certificate, you can use ACM to provision one in US East (N. Virginia). For more information, see Getting Started in the Amazon Certificate Manager User Guide.

  8. Choose Create.

  9. Amazon Cognito returns you to the App integration tab. A message titled Create an alias record in your domain's DNS is displayed. Note down the Domain and Alias target displayed in the console. They will be used in the next step to direct traffic to your custom domain.

To add your domain to your user pool with the Amazon Cognito API:

Step 2: Add an alias target and subdomain

In this step, you set up an alias through your Domain Name Server (DNS) service provider that points back to the alias target from the previous step. If you are using Amazon Route 53 for DNS address resolution, choose the section To add an alias target and subdomain using Route 53.

  • If you aren't using Route 53 for DNS address resolution, then you must use your DNS service provider's configuration tools to add the alias target from the previous step to your domain's DNS record. Your DNS provider will also need to set up the subdomain for your custom domain.

  1. Sign in to the Route 53 console. If prompted, enter your Amazon credentials.

  2. If you don't have a hosted zone in Route 53, create one with a root that is a parent of your custom domain. For more information, see

    1. Choose Create Hosted Zone.

    2. Enter the parent domain, for example, of your custom domain, for example, from the Domain Name list.

    3. Enter a Description for your hosted zone.

    4. Choose a hosted zone Type of Public hosted zone to allow public clients to resolve your custom domain. Choosing Private hosted zone is not supported.

    5. Apply Tags as desired.

    6. Choose Create hosted zone.


      You can also create a new hosted zone for your custom domain, and you can create a delegation set in the parent hosted zone that directs queries to the subdomain hosted zone. Otherwise, create an A record. This method offers more flexibility and security with your hosted zones.For more information, see Creating a subdomain for a domain hosted through Amazon Route 53.

  3. On the Hosted Zones page, choose the name of your hosted zone.

  4. Add a DNS record for the parent domain of your custom domain, if you don’t already have one. Add a DNS A record for the parent domain and choose Create records. The following is an example record for the domain 60 IN A


    Amazon Cognito verifies that there is a DNS record for the parent domain of your custom domain to protect against accidental hijacking of production domains. If you do not have a DNS record for the parent domain, Amazon Cognito will return an error when you attempt to set the custom domain. A Start of Authority (SOA) record isn't a sufficient DNS record for the purposes of parent-domain verification.

  5. Add a DNS record for your custom domain. You record must point to the custom domain Alias target, for example Choose Create record again.

  6. Enter a Record name that matches your custom domain, for example myapp to create a record for

  7. Enable the Alias option.

  8. Choose to Route traffic to an Alias to Cloudfront distribution. Enter the Alias target provided by Amazon Cognito when you created your custom domain.

  9. Choose Create Records.


    Your new records can take around 60 seconds to propagate to all Route 53 DNS servers. You can use the Route 53 GetChange API method to verify that your changes have propagated.

Step 3: Verify your sign-in page

  • Verify that the sign-in page is available from your custom domain.

    Sign in with your custom domain and subdomain by entering this address into your browser. This is an example URL of a custom domain with the subdomain auth:<your_app_client_id>&redirect_uri=<your_callback_url>

Changing the SSL certificate for your custom domain

When necessary, you can use Amazon Cognito to change the certificate that you applied to your custom domain.

Usually, this is unnecessary following routine certificate renewal with ACM. When you renew your existing certificate in ACM, the ARN for your certificate remains the same, and your custom domain uses the new certificate automatically.

However, if you replace your existing certificate with a new one, ACM gives the new certificate a new ARN. To apply the new certificate to your custom domain, you must provide this ARN to Amazon Cognito.

After you provide your new certificate, Amazon Cognito requires up to 1 hour to distribute it to your custom domain.

Before you begin

Before you can change your certificate in Amazon Cognito, you must add your certificate to ACM. For more information, see Getting Started in the Amazon Certificate Manager User Guide.

When you add your certificate to ACM, you must choose US East (N. Virginia) as the Amazon Region.

You can change your certificate by using the Amazon Cognito console or API.

Amazon Web Services Management Console
To renew a certificate from the Amazon Cognito console:
  1. Sign in to the Amazon Web Services Management Console and open the Amazon Cognito console at

  2. Choose User Pools.

  3. Choose the user pool for which you want to update the certificate.

  4. Choose the App integration tab.

  5. Choose Actions, Edit ACM certificate.

  6. Select the new certificate you want to associate with your custom domain.

  7. Choose Save changes.

To renew a certificate (Amazon Cognito API)