2

I have a website -- portaldevservices.com

The domain is managed by route 53 and works fine with http.

I have one ec2 instance.

I recently decided to move to https and put a load balancer in front of the ec2 instance.

From here I created a load balancer edited the A record and the Cname to the credentials of the load balancer. The health check is fine and the ec2 instance was added.

Using Amazon Certificate manager I created a cert and added it to the load balancer.

Here are some credentials/info:

When I try to access https://portaldevservices.com I get this: Website screenshot

hosted zones

load balancer port config

load balancer basic config

load balancer listener

acm certificate

Thanks for the help. I'm a mobile dev so this is my first time really stepping into the backend world.

Solved:

Ok that was a lot easier than I thought. If anyone else experiences this issue all I had to do was add the "www." to the front of my A type

From portaldevservices.com -> www.portaldevservices.com

The https access now works well.

tomrondo
  • 21
  • 1
  • 5
  • Looks like your certificate is for `www.portaldevservices.com`, and you are trying to open `portaldevservices.com ` – Dusan Bajic Dec 27 '17 at 23:01
  • Yes that's what someone suggested to me. I'm unable to make a cert omitting the www. (Or atleast it's been trying to validate for over 24 hrs) – tomrondo Dec 27 '17 at 23:06
  • 2
    1) Domain names need to match, so that is the reason for the error. 2) Your hosted zone screenshot shows no CNAME record for `portaldevservices.com` cert validation; repeat the procedure and follow the instructions carefully. – Dusan Bajic Dec 27 '17 at 23:13

1 Answers1

0

Ok that was a lot easier than I thought. If anyone else experiences this issue all I had to do was add the "www." to the front of my A type

From portaldevservices.com -> www.portaldevservices.com

The https access now works well.

tomrondo
  • 21
  • 1
  • 5