Cname for AWS API Gateway custom domain
Clash Royale CLAN TAG #URR8PPP Cname for AWS API Gateway custom domain the concept is simple. Create a Cname switch that points to blue / green deployment channels via AWS API Gateway. The API has two stages for blue and green mapped back into an environment variable which in turns maps back into the Lambda alias associated with it's own dedicated version. Therefore there are now two separate channels for conducting deployments into. All of this works fine. The issue arises when a Cname is created in Route53 to point to either of the API Gateways blue or green custom domains. The SSL cert is held in AWS Certificate Manager. When we call the blue endpoint via the Cname we get an SSL error curl -Il -H "Host:blue-api.example.com" -H "x-api-key:xxxxxxxxx" -X GET https://cname-api.example.com/questions/health curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect Whereas when we call the custom domain directly it works c...