Infrastructure Troubleshooting
Diagnose failed diffs and deployments, AWS permissions, quotas, retained resources, and configuration errors.
Open the failed infrastructure deployment and use the Overview and Logs tabs. Find the first resource-level failure; later cancellation messages are usually consequences.
Connection or Permission Failure
- Confirm the project points to the intended AWS connection, account, region, and role.
- Verify the StationOps connection stack still exists and is healthy.
- Check whether an organisation owner changed the underlying AWS connection.
- Confirm any AWS CodeConnection required by the configuration is available.
Resource Creation Failure
- Check AWS service quotas and regional availability.
- Look for globally unique names already owned by another account.
- Check network ranges, ports, certificates, DNS ownership, and dependency order.
- For retained resources, confirm an earlier deployment did not leave a resource that conflicts with the new configuration.
Invalid or Unexpected Diff
- Compare the configuration with the last successful deployment.
- Inspect the underlying JSON and generated analysis output.
- Recheck every environment tab and the shared components.
- Confirm component IDs were not renamed unintentionally.
- Stop before deploying if the diff deletes or replaces stateful production resources unexpectedly.
Stuck Deployment
AWS resource stabilisation can take time. Read the current cycle and AWS event detail before abandoning it. Use Abandon Deployment only when the action is offered and the external resource state has been checked.
Create a new deployment only after changing the failed configuration or external condition.