Amazon Redshift announces support for CNAME
Amazon Redshift now supports Canonical Name (CNAME) or custom domain name, an easy-to-read Domain Name System (DNS) record that routes SQL client connections to either the endpoint of your Amazon Redshift cluster or Amazon Redshift Serverless workgroup. With CNAME, you don’t need to expose your Redshift endpoint in the database connection, which enhances your security and it’s easier to recall and use.
Amazon Redshift now supports Canonical Name (CNAME) or custom domain name, an easy-to-read Domain Name System (DNS) record that routes SQL client connections to either the endpoint of your Amazon Redshift cluster or Amazon Redshift Serverless workgroup. With CNAME, you don’t need to expose your Redshift endpoint in the database connection, which enhances your security and it’s easier to recall and use.
With CNAME, you can quickly route traffic to a new cluster or workgroup in a fail-over case. When disaster happens, connections can be re-routed centrally with minimal disruption. You can configure CNAME for an existing Redshift cluster or Redshift Serverless workgroup by using the Amazon Redshift console, the AWS CLI and the Amazon Redshift API. A validated Transport Layer Security (TLS) certificate for a CNAME is required to keep communication secure and to verify ownership of the domain name. You can use the your AWS Certificate Manager (ACM) account with an AWS KMS key for secure certificate management.
The feature of Amazon Redshift CNAME is available in all commercial regions where Amazon Redshift is available. To learn more, visit the Amazon Redshift management guide.