Score:0

AWS ALB showing "Not Secure"

vn flag

I configured a route53 cname to forward traffic to an api gateway. By passing the stage and resource name to the cname, the correct stage & resource are called in the API gateway, and they forward traffic to an existing elastic beanstalk that's behind an application load balancer.

The load balancer has a certificate configured on it (with both the www domain www.mysite.com and the wildcard subdomain *.mysite.com configured on it).

The problem is that the whenever I call an endpoint using the cname subdomain, the final URL gets resolved to the url of the elastic beanstalk environment and it shows that the certifcate is invalid (because it was issues for mysite.com not for the custom elastic beanstalk environment URL).

Is there any recommendation on how to handle this? Thank you

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.