USERTrust RSA Certification Authority certificate

Based on the information provided about the upcoming changes to Apple Push Notification service (APNs) server certificates, here's what you need to know regarding your AWS Elastic Beanstalk deployment:

1. The change in the Certification Authority (CA) for APNs will affect both sandbox and production environments, with updates scheduled for January 21, 2025 (sandbox) and February 24, 2025 (production).

2. If you're using AWS services like Amazon SNS to handle push notifications, you likely won't need to take any direct action on your application side. AWS typically manages these connections and certificate updates automatically.

3. However, since you're deploying your backend using AWS Elastic Beanstalk, the situation may be different. Elastic Beanstalk provides you with more control over your environment, which means you might need to handle certificate updates yourself.

4. To ensure uninterrupted service, you should:

   a. Check your Elastic Beanstalk environment configuration to see if it's using any custom AMIs or if you've made any modifications to the trust store.

   b. If you're using standard Elastic Beanstalk environments without customizations, AWS may handle the certificate update automatically. However, this isn't guaranteed, and you should verify this with AWS support or documentation closer to the update dates.

   c. If you've made custom modifications or are using custom AMIs, you'll likely need to update the trust store yourself to include the new APNs server certificate (SHA-2 Root: USERTrust RSA Certification Authority certificate).

5. As a best practice, it's recommended to:

   a. Keep an eye on AWS Elastic Beanstalk documentation and announcements for any updates related to this APNs change.

   b. Test your push notifications in the sandbox environment after January 21, 2025, and in the production environment after February 24, 2025, to confirm everything is working as expected.

   c. If you're unsure about the impact on your specific setup, consider reaching out to AWS support for clarification.

Remember, while AWS often handles many infrastructure updates automatically, when it comes to more customizable services like Elastic Beanstalk, it's crucial to verify and potentially take action to ensure your applications continue to function correctly with these certificate changes.
Sources
Certificate Authority (CA) for Apple Push Notification (APN) is changing | AWS re:Post
Certificate Authority (CA) for Apple Push Notification (APN) is changing | AWS re:Post

Thanks, Unfortunately EB is not handling the certificate update automatically. I should do it manually, Any steps or recommendations to do it? Many thanks