Service management for Aiven for MySQL®
Manage the lifecycle of your Aiven for MySQL® service, including power state, naming, tags, forks, cloud region, users, and advanced parameters.
How service lifecycle actions relate
Renaming a service reuses the forking mechanism: It creates a fork under a new name, then removes the original service. That means renaming has the same backup prerequisite as forking, even though the renaming steps don't mention it directly. Powering a service off and on, forking it, and moving it to a new cloud or region each move the service through a transitional state. Tagging a service and editing its advanced parameters, by contrast, take effect without moving or recreating any infrastructure.
Things to know
- Permissions differ by action: powering a service on or off, forking it, renaming it, and deleting it all use the same project-level permission as creating a service. Managing service users needs a separate permission scoped to that specific service.
- You're notified before automatic deletion: a service left powered off long enough is eventually deleted, but Aiven notifies you first, giving you time to power it back on or fork it if you still need the data.
- Terraform doesn't cover every action: tags, advanced parameters, and service users all have Terraform resources, but there's no Terraform equivalent for powering a service on or off. Use the Aiven Console or Aiven CLI instead.
Related pages