2 個答案
- 最新
- 最多得票
- 最多評論
0
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.
已回答 4 年前
0
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
已回答 10 個月前
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前