Troubleshooting
Separate operation, principal and path before identifying a cause.
Choose a subject
Available lessons and tools
Available lessons and tools are listed below. Other subjects are being prepared; the subject list also shows planned coverage.
Troubleshoot IAM AccessDenied: requests, allows, denies and limits
AccessDenied means an AWS request was not authorized. Before adding permissions, identify the failed principal, action and resource. A mismatched statement, an explicit Deny and a permissions limit require different investigations even when the visible error looks similar.
Troubleshoot S3 403 AccessDenied: operation, permissions and BPA
An S3 403 AccessDenied does not identify one universal cause. First establish which operation failed, who requested it and which resource was targeted. Separate a bucket-policy write from an object read, then distinguish observed evidence from conditions you have not inspected.
Cannot SSH to EC2? Diagnose timeouts, refusal and authentication errors
When SSH to EC2 fails, first identify the connection method and error category. A timeout, a refusal and an authentication error lead to different checks. Establish the intended destination and path before adding public addressing or broad SG rules.
Troubleshoot AWS Lambda timeouts: duration, dependency waits and retries
A Lambda timeout means the function did not finish within its configured deadline; it does not identify the cause. Establish the invocation method and which deadline expired, then investigate input size, downstream waits and function work. Check results and side effects before extending the deadline or invoking again.