Make changes to an existing MySQL Managed Database.
The user needs read_writeuser grant access to the database.
The database's status needs to be active.
New values set in the allow_list overwrite existing values. To keep existing values, run the List MySQL Managed Databases operation, store the allow_list addresses from the response, and include them with any new addresses in this operation.
Updates to your allow_list may take a short time to complete, making this operation inappropriate for rapid successive updates.
Also allows resizing the database cluster to a larger one. Clusters can't be resized to smaller plans.
All Managed Databases include automatic updates, which apply security patches to the underlying operating system of the Managed MySQL Database. Use the updates object in this operation to modify the maintenance window for these updates.
If your database cluster is configured with a single node, downtime occurs during maintenance updates. Use the updates object to adjust the window to match a time that's the least disruptive to your application and users. Also consider upgrading to a high availability plan to avoid any maintenance downtime.
Major upgrades are optional until the service reaches end of service, and can be done in place.
You can't update engine_config advanced parameter settings for a suspended database. You'll need to resume it first.
A successful request triggers a database_updateevent.
Beta. You can update an existing MySQL Managed Database to move it to a Virtual Private Cloud (VPC) using the private_network object in the request. This support is in beta. Talk to your Akamai account team for more details.
📘
Currently, VPC subnets associated with Managed Database instances don't automatically block outbound connections outside the subnet. To limit network exposure, you should configure Cloud Firewall rules to explicitly deny outbound connections beyond the intended subnet. For more details on configuring rules, see the Cloud Firewall documentation.
Update a MySQL Managed Database
Make changes to an existing MySQL Managed Database.
The user needs
read_writeuser grant access to the database.The database's status needs to be
active.New values set in the
allow_listoverwrite existing values. To keep existing values, run the List MySQL Managed Databases operation, store theallow_listaddresses from the response, and include them with any new addresses in this operation.Updates to your
allow_listmay take a short time to complete, making this operation inappropriate for rapid successive updates.Also allows resizing the database cluster to a larger one. Clusters can't be resized to smaller plans.
All Managed Databases include automatic updates, which apply security patches to the underlying operating system of the Managed MySQL Database. Use the
updatesobject in this operation to modify the maintenance window for these updates.If your database cluster is configured with a single node, downtime occurs during maintenance updates. Use the
updatesobject to adjust the window to match a time that's the least disruptive to your application and users. Also consider upgrading to a high availability plan to avoid any maintenance downtime.Major upgrades are optional until the service reaches end of service, and can be done in place.
You can't update
engine_configadvanced parameter settings for a suspended database. You'll need to resume it first.A successful request triggers a
database_updateevent.Beta. You can update an existing MySQL Managed Database to move it to a Virtual Private Cloud (VPC) using the
private_networkobject in the request. This support is in beta. Talk to your Akamai account team for more details.<
>
Learn more...
Learn more...