1 Answer
- Newest
- Most votes
- Most comments
2
Found an email dated Jan 14th of this year that notified us about the cert migration. More info found here:
answered a year ago
Yes, that must be why. Thanks!
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Similar issue. Client does some form of cert-pinning, their process that connects to our Elastic Beanstalk application is now broken until we walk them through getting new cert downloaded and installed. Old cert valid 2022-06-03 to 2023-07-30 New cert valid 2023-02-27 to 2023-07-30 Not seeing any bulletin about this happening. Looks like the intermediate CA changed? Old one says "Amazon", new one says "Amazon RSA 2048 M01"
EDIT: Whoops, found an email and article about it, clear as day: https://aws.amazon.com/blogs/security/amazon-introduces-dynamic-intermediate-certificate-authorities/