Cloud Platform supports IPv6 addresses. To use IPv6 for your website, you can follow either of these options:
- Enable SSL for your site and Configure your domain name with the appropriate prefix
- Use Platform CDN (if available)
Enable SSL for your site
IPv6 support on Cloud Platform Enterprise or Cloud Platform Professional requires an Amazon Web Services Elastic Load Balancer (ELB) infrastructure. For an ELB to be provisioned for an environment, you need to enable SSL support for the environment, which requires you to purchase and upload an SSL certificate as a legacy SSL certificate in the Cloud Platform interface. Having an ELB enables IPv6 support. For Cloud Platform Professional websites, there is an additional charge to reflect the cost of the ELB.
For information about how to enable SSL, including how to upload a legacy SSL certificate, read Enabling SSL. If you want IPv6 support, but not SSL, you must create a self-signed SSL certificate to use with Cloud Platform. You can then upload this self-signed certificate instead of purchasing a certificate. For more information, see Creating a self-signed SSL certificate.
Configure your domain name with the appropriate prefix
In your DNS provider’s web interface, add the appropriate prefix to your domain name. In most cases, prefix your CNAME domain name with the dualstack
prefix to support both IPv4 and IPv6 visitors. Prefix your CNAME domain name with the ipv6
prefix to support only IPv6 visitors. For example, suppose your website’s domain name is www.example.com
and your Prod environment’s URL is mc-1234-4321.us-east-1.elb.amazonaws.com
. Set the CNAME entry for www.example.com
to dualstack.mc-1234-4321.us-east-1.elb.amazonaws.com
.
For more information about configuring your DNS settings, read Pointing DNS records to your public IP addresses.
Use Platform CDN (if available)
If you are on Cloud Platform Enterprise and have Platform CDN enabled, use the CNAME provided in the Global CDN section of the Domains page. The dualstack
prefix in the endpoint ensures that it is IPv6 compatible without the need for a separate AAAA record.