We switched from Comodo wild-card SSL CA to a free version from AWS through the Certificate Manager. The domain is registered on Namecheap and the only way we could get the website to route traffic over HTTPS (it is hosted on a static S3 bucket) was to use Route 53 as the DNS server.

After transferring all the DNS records to Route 53 and configuring the endpoints in CloudFront the website is working fine. However the sub-domains (e.g api. and worker.) which are pointed to EC2 instances configured through Elastic Beanstalk running the backend servers are not handling traffic over HTTPS. This means the iOS/Android apps are not working.

I tried configuring the load balancer listener with the new wild-card SSL from ACM with no luck. What else do I need to do or how would you go about debugging the problem?

  • Please be more specific with what you mean when you say "with no luck." That doesn't give us much to go on. – Michael - sqlbot Jul 18 '18 at 23:50
  • Sorry, that was confusing. I can add a second listener on port 443 as HTTPS, with the ACM generated SSL in addition to the HTTP on port 80 in the EC2 dashboard > Load Balancers. There is no difference in the behavior of api.<ourdomain>.co – cvb0rg Jul 19 '18 at 1:15
  • Also, if I go to EBS and go to Configuration on one of the 2 applications > load balancer, I only see the HTTP on port 80. If I try to add the HTTPS on port 443 here (with the correct ACM SSL and policy) and Apply, the env will fail to update with the error something like: "Creating Load Balancer listener failed Reason: A listener already exists on this port for this load balancer ..." – cvb0rg Jul 19 '18 at 1:20
  • That's unexpected. Can we see some screen shots of the balancer config as well as the error when it occurs? Also, with CloudFront, the cert would be in the us-east-1 region of ACM, but for EB, the cert needs to be in the region where are running beanstalk. I assume you're familiar with this and that it isn't the issue, since it doesn't seem to match your description of the problem... but it does cause some confusion, on occasion, so potentially worth mentioning. – Michael - sqlbot Jul 19 '18 at 10:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.