The above listed database types will need to be restarted to load a newly issued *.aptible.in certificate. The current certificate is set to expire February 2, 2026.
You may restart your impacted database at any time of your choosing before January 31st in order to load the new certificate.
Aptible's SRE team will identify any and all databases still using the expiring certificate, and restart them on January 31st, 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 is as follows:
Jan 5 : New Database Certificate will be available on Shared Stacks. You may restart your impacted databases at any time before the maintenance time to complete the update on their own schedule. (Completed)
Jan 11 8:00 PM EST: All remaining Shared Stack databases will be restarted to load the new certificate (Completed)
Jan 12 4:00 PM EST : The new certificate will be available for all Dedicated Stacks. (Completed)
Jan 12 through Jan 31: You may restart any impacted Databases on your Dedicated Stacks at your convenience to update the certificate.
Jan 31: 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 EST
--------
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 years), 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: Either "restart" or "reload" operations will suffice, through "reload" will be quicker. 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 restarted to update the certificate? A: During the maintenance window for Dedicated stacks, you should use 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 January 31st, and restart them between 8:00PM and 11:59PM Eastern.
Completed -
The scheduled maintenance has been completed.
Jan 17, 22:31 EST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 22:00 EST
Scheduled -
In order to upgrade key infrastructure backing our api.aptible.com, we will need to block operations for 3-5 minutes during this maintenance window.
If you request an operation while the block in in place, you will receive the error 'Our Reliability Team has temporarily blocked this operation'.
No running operations will be interrupted, and no other impact is expected.
Jan 15, 12:03 EST
Completed -
The scheduled maintenance has been completed.
Jan 17, 22:30 EST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 22:00 EST
Scheduled -
During this period we will be performing maintenance on our Git server, which is used for Dockerfile based (`git push`) deployments.
The server may be unavailable for deploying new code for a short period (2-5 minutes) during this window, and some deployments happening during this window which are being streamed via the CLI may see the deployment logs disconnected from the CLI. However, those deployment operations already running will keep running normally, and their result can be verified in the Aptible Dashboard (https://app.aptible.com/)
No other impact to running services or the Aptible platform is expected.
Jan 15, 12:00 EST
The above listed database types will need to be restarted to load a newly issued *.aptible.in certificate. The current certificate is set to expire February 2, 2026.
Aptible will restart the impacted Databases on Shared Stacks for you on Sunday January 11th.
--------
Additional maintenance periods will be scheduled for updating Databases hosted on Dedicated Stacks. The full timeline for Database certificate updates process is as follows:
Jan 5 : New Database Certificate will be available on Shared Stacks. You may restart your impacted databases at any time before the maintenance time to complete the update on their own schedule.
Jan 11 8:00 PM EST: All remaining Shared Stack databases will be restarted to load the new certificate
Jan 12 4:00 PM EST : The new certificate will be available for all Dedicated Stacks.
Jan 12 through Jan 31: You may restart any impacted Databases on your Dedicated Stacks at your convenience to update the certificate.
Jan 31: 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 EST
--------
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 years), 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: Either "restart" or "reload" operations will suffice, through "reload" will be quicker. 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 use 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 January 31st, and restart them between 8:00PM and 11:59PM EST.
Completed -
The scheduled maintenance has been completed.
Jan 6, 22:50 EST
Verifying -
Verification is currently underway for the maintenance items.
Jan 6, 22:37 EST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 22:00 EST
Scheduled -
Our team will be performing an upgrade on the bastion hosts for all Dedicated Stacks at January 6th at 10PM EST. The expected impact is that Ephemeral SSH sessions and Database Tunnels will be disconnected, but should immediately be available to reconnect. Operation logs being streamed via the CLI will also be interrupted, but the operations will continue without being impacted. App connectivity, Database connectivity, and internet connectivity will not be impacted by this maintenance. While the maintenance window to complete all upgrades is scheduled for 2 hours, the expected duration of impact of each stack is approximately 5 minutes.
Dec 30, 16:04 EST