Replace GoDaddy Certificate with ACM Certificate

Question

We set up our website quite some time ago (mfoodonline.com) and secured it with a GoDaddy certificate. We have purposefully let that certificate expire in order to switch to an ACM certificate. We have successfully set up that certificate and attached it and out EC2 instance to a load balancer, but the site is still reporting that the certificate is invalid as it appears to still be using the expired one from goDaddy. Wht is the proper procedure to switch from a manually installed goDaddy certificate to one supplied by ACM?

Answer

I found a second A record (with www appended) that was still poiting to the elastic IP address of the instance. Updated that to the load balancer and all is well.

Answer

You can import third party certificates to ACM and deploy them to ACM supported endpoints. When migrating from third party SSL certificates to ACM managed certificates, it is recommended to -
- Verify that you have selected the right SSL certificate ARN on the Load Balancer/ other supported end points.
- Check the DNS entries made in Route 53 to verify all "A" and "CNAME" records are pointing to the right resources for a domain and there are no records directly pointing to previous configurations.  
- All certificates in ACM are regional resources, including the certificates that you import. To use the same certificate with Elastic Load Balancing load balancers in different AWS Regions, you must import the certificate into each Region where you want to use it. 
- To use a certificate with Amazon CloudFront, you must import it into the US East (N. Virginia) Region.

For more information please refer - https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html

Replace GoDaddy Certificate with ACM Certificate

Relevant content