Category: Operations
- Server is already deployed and reachable.
- You have project permissions to manage instance actions.
- You reviewed impact windows for reboot, resize, or network changes.
- Use reboot for normal restart and power cycle only when server is unresponsive.
- Shut down gracefully before planned maintenance or large configuration changes.
- Resize CPU and memory based on observed workload metrics.
- Review storage usage and expand volume before critical disk exhaustion.
- Update firewall or security group rules when services change.
- Use server activity logs to track who executed lifecycle actions.
- After reboot or resize, instance returns to running state.
- SSH access and critical services respond normally after each action.
- Monitoring dashboards show improved resource headroom after scaling.
- Resizing during peak traffic windows without maintenance notice.
- Power cycling before checking console logs and process status.
- Changing multiple networking rules at once and locking out access.