SSL Certificate Issue When Accessing AWS Hosted Application On-Premises

Question

I'm facing an SSL certificate issue after migrating an on-premises application to AWS. We've successfully hosted the application on EC2 instances with an Application Load Balancer (ALB) in front, and we've set up an alias record on Route 53 to point to the ALB. The application can now be accessed from outside the on-premises network, and it correctly displays the SSL certificate from a third party. We've imported the correct SSL certificate to AWS Certificate Manager (ACM), and the ALB is configured to use this certificate.

However, we've encountered a challenge when trying to access the application from within the on-premises network. In this scenario, the application presents an invalid SSL certificate. Strangely, it appears to be showing an instance metadata SSL certificate, with "Amazon RSA 2048 M02" listed as the issuer.

Has anyone encountered a similar issue or have any insights into why the correct SSL certificate is displayed externally, but a different and incorrect certificate is presented within the on-premises network? Your expertise and guidance would be greatly appreciated in resolving this SSL certificate discrepancy.

Thank you in advance for your help!

Answer

Hard to pin it down because of the many moving parts in your network setup. Did you verify that your local DNS resolves correctly? And can you check how you connect your on-premise network to AWS and how you route requests towards the application when you come through the on-prem connection? It reads to me as if you are just not ending up on the ALB with your internal requests, but on another interface.

Answer

Are you running Split Horizon on Route53 with an Inbound Endpoint Resolver?
If you are running Split Horizon, you may want to check what the record resolves too incase its tied to something different.

SSL Certificate Issue When Accessing AWS Hosted Application On-Premises

相关内容