# Resource creation cancelled: Resource creation timed out after 60 minutes (AWS::CloudFormation::Stack)

- **ID:** `aws/cloudformation-stack-creation-timeout`
- **Domain:** aws
- **Category:** runtime_error
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

A CloudFormation stack creation exceeded the default 60-minute timeout, typically due to a slow resource provisioning (e.g., large RDS instance, complex nested stack).

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| CloudFormation API 2010-05-15 | active | — | — |
| AWS CLI 2.13.0 | active | — | — |

## Workarounds

1. **Increase the stack creation timeout using the CloudFormation console or CLI: 'aws cloudformation create-stack --stack-name my-stack --template-body file://template.yaml --timeout-in-minutes 120'. Set a value appropriate for the expected provisioning duration.** (90% success)
   ```
   Increase the stack creation timeout using the CloudFormation console or CLI: 'aws cloudformation create-stack --stack-name my-stack --template-body file://template.yaml --timeout-in-minutes 120'. Set a value appropriate for the expected provisioning duration.
   ```
2. **Optimize the CloudFormation template: break large stacks into nested stacks with individual timeouts, or use 'DependsOn' sparingly to reduce sequential dependencies. Consider using 'AWS::CloudFormation::WaitCondition' with a custom timeout for long-running resource creation.** (75% success)
   ```
   Optimize the CloudFormation template: break large stacks into nested stacks with individual timeouts, or use 'DependsOn' sparingly to reduce sequential dependencies. Consider using 'AWS::CloudFormation::WaitCondition' with a custom timeout for long-running resource creation.
   ```

## Dead Ends

- **** — Simply retrying the stack creation without increasing timeout or optimizing resource provisioning will hit the same timeout again. (95% fail)
- **** — Deleting the failed stack and recreating it with the same template doesn't address the root cause; the timeout will recur. (80% fail)