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 2, 2024.
The new certificate will be available on Dedicated Stacks starting Friday Feb 16th at 4:00 PM Eastern. After this time, customers may restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.
During this window you should us the Aptible CLI command `aptible maintenance:dbs` to track which databases are required to be restarted.
Please note that you need at least "read" permissions to see the databases requiring a restart. To ensure you are viewing information for all environments, its best this is reviewed by an Account Owner, Aptible Deploy Owner, or any user with privileges to all environments.
If you choose to take no action, Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them on March 1st between 8:00 PM and 11:59 PM Eastern.
--------
This notice pertains to one of three windows scheduled. The full timeline for Database certificate updates process process is as follows:
Feb 14 : New Database Certificate will be available on Shared Stacks.
Feb 16 : All Shared Stack databases will be restarted to load the new certificate
Feb 16 4:00 PM EST : The new certificate will be available for all Dedicated Stacks.
Feb 16 through March 1 : Customers should restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.
March 1: Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them between 8:00 PM and 11:59 PM Eastern
--------
FAQ:
Q: Do I need to test anything? A: While we do not expect any compatibility issues (we're using the same issuer as the past several year), we have seen in rare occasions client applications may also need to be restarted after a database due to issues unrelated to the certificate.
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 needs to be, and can be, restarted to update the certificate? A: During the maintenance window for Dedicated stacks, you should us the Aptible CLI command `aptible maintenance:dbs` to track which databases are required to be restarted. Please note that you need at least "read" permissions to see the databases requiring a restart. To ensure you are viewing information for all environments, its best this is reviewed by an Account Owner, Aptible Deploy Owner, or any user with privileges to all environments.
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 1st, and restart them between 8:00PM and 11:59PM Eastern.