A company registered its domain with Amazon Route 53. The company uses Amazon API Gateway in the ca-central-1 Region as a public interface for backend microservice APIs consumed securely by third parties. The company wants the API Gateway URL to use the company's domain name and corresponding certificate so third parties can use HTTPS. Which solution meets these requirements?

To use a custom domain name with API Gateway and enable HTTPS, you need to create a custom domain name in API Gateway. This involves importing the SSL/TLS certificate for your domain into AWS Certificate Manager (ACM) in the same region as your API Gateway. Then, you associate this certificate with the custom domain name in API Gateway. Finally, you configure Route 53 to create an A record (alias) that points your custom domain name to the API Gateway custom domain name endpoint. Incorrect options: Stage variables are for configuration within an API Gateway stage, not for custom domain mapping or certificate management. While Route 53 DNS records are necessary, importing the certificate into us-east-1 is only for CloudFront distributions, not for regional API Gateway custom domains. Importing the certificate into us-east-1 is incorrect for a regional API Gateway custom domain. Also, pointing an A record to the company's domain name itself would create a circular reference.