The above listed database types will need to be restarted to update load a newly issued *.aptible.in certificate. The current certificate is set to expire March 3, 2023.
Aptible will restart the impacted Databases on Shared Stacks for you on February 2nd.
Additional maintenance periods will be scheduled for updating Databases hosted on Dedicated Stacks. _______
The full timeline for Database certificate updates process process is as follows:
Feb 2 : Database Certificate will be updated on Shared Stacks. Shared Stack databases will be restarted to load the new certificate
Feb 2 through Feb 9 : Testing period for shared stacks. While we do not expect any compatibility issues (we're using the same issuer as the existing certificates), we have seen In rare occasions client applications may also need to be restarted due to client driver and versions. Please use this period to recognize if your App is required to restart, so you can ensure you are prepared for later updating your Dedicated Stack Databases.
Feb 9 : The new certificate will be available for all Dedicated Stacks.
Feb 9 through March 2 : Customers should restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.
March 2: Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them between 10:00 PM and 11:59 PM Eastern
Q: Do I need to "restart", or can I "reload" my databases? A: Both `aptible db:restart` or `aptible db:reload` will work. If you need to restart your database for any reason, either to scale the disk size or container size, the certificate will be updated.
Q: How do I tell if my Database has had the maintenance completed successfully? A: You can use the Database's Activity tab on dashboard.aptible.com to ensure there has been a successful restart operation after Feb 9th. You can also email firstname.lastname@example.org to ask for a list of remaining Databases.
Q: What happens if I don't take any action, or miss restarting a Database? A: Aptible's SRE team will identify any remaining Databases on March 2nd, and restart them between 10:00PM and 11:59PM Eastern.