1
Check the pipeline
Open the Pipeline status page and locate the affected change. Review its deployment status, test results, messages, and logs, starting with the first explicit error.
Diagnose and recover
Troubleshooting
Start with the pipeline, correlate the failure with AWS telemetry, and collect the identifiers needed for a quick support handoff.
Recommended Diagnostic Flow
2
Review CloudWatch
Follow the CloudWatch links from the pipeline to inspect application and infrastructure logs, metrics, and triggered alarms. Beta and Production use separate AWS accounts, so confirm the environment first.
3
Inspect the running application
Enterprise customers, and Premium customers when this capability becomes available, can use secure access to ECS Fargate containers for deeper Magento debugging when logs and metrics are not sufficient.
4
Contact support
If the issue remains unresolved, contact us by email. Include enough context for the team to identify the exact deployment and reproduce the problem.
Support checklist
Include these details
- Deployment or Change ID
- Environment: Beta or Production
- Approximate failure time and timezone
- Short description of the expected and actual behavior
- Relevant error message or copied log excerpt
- Steps already attempted
Avoid sharing passwords, private repository keys, access tokens, or other secrets in screenshots and support messages. Redact sensitive values while leaving deployment identifiers and relevant errors visible.