-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
alias not working with imported certificate #5773
Comments
Hello @sri-sp. Can you double check if in the ACM certificate that you imported, do both aliases |
the certs are for [staging.*************.com] and [ *.staging.**************.com] so it should have to work for both am i right ! |
Yeah that should work...what copilot does under the hood is essentially adding the aliases to the LB rules to make sure LB route requests from these host headers to the correct target group (ECS service), and add the certificates to the LB. However, i wonder if you updated the A-records for |
Thank you for the clarification. Yes, I have updated the A-records for "staging.***********.com" and "my.staging.**********.com" to resolve to the environment's LB DNS. However, I'm still encountering an HTTPS error when trying to access the application via HTTPS. Is there anything else I should check or configure to resolve this issue? |
You can go to the EC2 console and see if the Load Balancer is configured correctly but that's the only place where Copilot makes changes...it could be the DNS cache on your local device. Could you try to use other devices to access the URL? |
This issue is stale because it has been open 60 days with no response activity. Remove the stale label, add a comment, or this will be closed in 14 days. |
This issue is closed due to inactivity. Feel free to reopen the issue if you have any further questions! |
I have obtained a certificate in PFX format, which I converted to PEM encoded format successfully.
I imported the PEM certificate into AWS Certificate Manager (ACM) using OpenSSL, following the steps outlined in this AWS blog post.
I added the certificate to my environment and deployed the application using the Copilot command copilot env deploy.
However, I am unable to access the application via HTTPS. It throws an insecure HTTPS error when I try to access it.
here is my manifest file
====================
Any help or insights into resolving this HTTPS error would be highly appreciated.
The text was updated successfully, but these errors were encountered: