0

First of all I tried to google, read a lot blogs & aws official documentation and couldn't find anything that works in my case.

Scenario & Problem:

I have a godaddy domain and a beanstalk environment. Also, I issued ACM certificate and assigned it to beanstalk through configuration. I can see the issued certificate in loadbalancer attached to beanstalk env. I have setup (godaddy) A record to elastic IP of my beanstalk instance & www to beanstalk dns x.us-west-2.beanstlak.com. Http is working absolutely fine. But no luck with https.

Loadbalancer Listener: 

HTTPS 443 HTTP 80 Change 07xxaab5-afqq-4tyb-bbz-0eaxxxw37 (ACM)

Any help would be appreciated.

Improve this question
15
  • You should not direct requests to your EB instance - it all needs to go through your load balancer. It's your load balancer that is configured with your cert. Commented Apr 4, 2017 at 0:38
  • I have load balancer attached to beanstalk environment. (through configuration -> HTTPS -> 443). So, when I open mydomain.co.uk shouldn't it hit my elastic IP, which has a load balancer attached...right? Commented Apr 4, 2017 at 0:42
  • Wrong. Your EIP has nothing to do with your load balancer. Commented Apr 4, 2017 at 0:43
  • its not an old balancer. I created a complete new load balancing environment. After successful launch, i went to configuration of beanstalk environment to set HTTPS (443) then selected my pre-issued ACM certificate for domain. Also you can check the loadbalancer listener i updated in question. Commented Apr 4, 2017 at 0:46
  • 1
    Well then it's not going to work for you. Commented Apr 4, 2017 at 0:57

1 Answer 1

Reset to default
2

To synthesize an answer based on the comment thread:

Usage of ELB requires that you can point your DNS names to the ELB via either CNAME or Alias (ANAME) records. You cannot use A records with ELB.

If you are using a DNS provider that does not support Alias record types, you will not be able to point your zone apex (e.g. example.com) to your ELB. In this situation, you still are able to point other names, such as www.example.com to the ELB, as that can be a CNAME record, which all providers support.

Your setup is currently working just fine with HTTPS except for the fact that www.legitclaims.co.uk is not listed as a valid name on your certificate. Only legitclaims.co.uk is:

enter image description here

Improve this answer
10
  • okay. putting awseb-e-g-AWSEBLoa-xxxxx-xxxxx.us-west-2.elb.amazonaws.com WWW record in godaddy should work..right ? Commented Apr 4, 2017 at 1:15
  • Yes, that should work, as a CNAME record. Commented Apr 4, 2017 at 1:16
  • awesome! If it works I can redirect to www. let me check and get back to you. Commented Apr 4, 2017 at 1:17
  • Well, you need to serve your zone apex with HTTPS as well (if even just to do the redirect), which you can't do with your current DNS situation. Commented Apr 4, 2017 at 1:21
  • I switched my x.us-west-2.beanstalk.com to awseb-e-g-AWSEBLoa-xxxxx-xxxxx.us-west-2.elb.amazonaws.com as CNAME WWW record. I am not sure how much time it takes to update records. But getting not secure with https on mydomain.co.uk Commented Apr 4, 2017 at 1:25

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.