- Newest
- Most votes
- Most comments
Hello.
Did you create the SSL certificate with ACM?
If so, are you accessing EC2 via ALB?
Are you creating an HTTPS listener if you are accessing via ALB?
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html
If you are accessing EC2 directly, does your web server have an SSL certificate obtained using Let's Encrypt or similar?
Potential Causes: Incomplete or Invalid SSL Certificate Chain: Missing certificates or one issued by an untrusted CA can cause warnings. Incorrect Route 53 Record Type: Ensure A or AAAA record points to your EC2 instance's IP address. Improper SSL Termination: Verify SSL termination on your EC2 instance or relevant AWS service (ELB, CloudFront). Outdated Browser Cache: Clear browser cache and cookies to eliminate cached data interference. Weak Server Cipher Suites: Update your web server configuration to support secure cipher suites.
Troubleshooting Steps: Certificate Verification: Use online tools like SSL Labs to check the certificate chain and issuer. Route 53 Configuration: Verify record type and SSL termination location (EC2 or AWS service). Clear Browser Cache: Eliminate potential caching issues. Server Configuration: Review cipher suite support on your web server.
answered 2 years ago
Can you put some more information here, what is your domain name for instance. You can also connect to your instance with the openssl utility to debug it, using a command such as:
openssl s_client -connect domain.tld:port
This will show you the parameters of the certificate that you are using. You can also get more information from the browser itself, usually by clicking on the little lock that shows the warning message and seeing why it does not trust the certificate offered by your server.
You mention creating a certificate in ACM, ACM cannot be used with an EC2 instance, only with a load-balancer. If you are using only an instance and route53, you need to pursue something like https://letsencrypt.org/ for a certificate.
Also do you really mean port 90? That's not a common port on which to run SSL?
Relevant content
asked 7 years ago
Agreed, if the certificate is one that you created on your own wihtout being registered on an official registry, you may get this ind of issues.
Did you create the SSL certificate with ACM? -> yes are you accessing EC2 via ALB? -> no Are you creating an HTTPS listener if you are accessing via ALB? -> no I just install SSL certificate to the domain
HTTPS communication is not possible just by creating a certificate with ACM. To use ACM's SSL certificate, you need to create an HTTPS listener on the ALB. If you are accessing EC2 directly, you need to issue a certificate with Let's Encrypt and configure it on the web server. For Amazon Linux 2023, I think you can issue an SSL certificate by following the steps in the blog below. https://medium.com/@eikachiu/install-certbot-with-nginx-on-amazon-linux-2023-0a908f73ceb1