Service management for Aiven for PostgreSQL®

Manage the lifecycle of your Aiven for PostgreSQL® service, including power state, naming, tags, forks, cloud region, users, and advanced parameters.

Effect on availability

Migrating to a different cloud provider or region happens without downtime, unlike most other lifecycle actions in this list.
Powering off a service releases its compute entirely, unlike a restart triggered by an advanced parameter change, which keeps the service allocated throughout. You can't power a service on or off with Terraform, since its state attribute is read-only there; use the console or the Aiven CLI instead.
Forking and renaming a service both create a running service from the latest backup. Renaming forks under a new name and deletes the original, so it depends on having a backup even though its own instructions don't mention one.
Some advanced parameters, such as max_connections, restart the service when you change them, unlike migrating, forking, or renaming.