As the hosting operator, guide your customer through PD AWS Neptune’s power controls after agreeing a temporary interruption with the application owner. Start and Stop operate on the linked Neptune cluster, while Reboot restarts its primary compute instance. Stopping the cluster does not cancel the billing service or retire the resource.

Prepare for the interruption

Open the active customer service and confirm the database and AWS region. Coordinate with the application owner: stopping or rebooting drops active connections. Use the controls offered by that service. If a control is unavailable, your hosting team should check the original service configuration and actual cluster/instance state. A direct endpoint or another service’s control is not a substitute for the offered action.

Customer steps: request one action

1. Open the service’s Overview.
2. Choose Stop for a running database, Start for a stopped one, or Reboot for a restart.
3. Read and confirm the interruption message where one is shown.
4. Follow the request under Activity.
5. Wait for the resulting database state before reconnecting the application or asking for another action.

Work can be queued while AWS completes an earlier operation. A Done entry can mean AWS accepted the operation, rather than that the database has already reached its final state. Repeated clicks are not a useful way to shorten a provider transition.

Understand temporary stopping

AWS automatically restarts a stopped Neptune cluster after seven days. Stopping is not permanent retirement and should not be treated as cancelling all provider charges. Keep required recovery points independently of a temporary stop.

If the database does not reach the expected state, compare the original Activity request with the cluster and affected instance in your AWS account. Follow an operation still processing rather than repeating it to refresh its status.

See the PD AWS Neptune Blesta guide for related tasks, or explore PD AWS Neptune.