Read ../_house-style/house-style.md before starting.
Anchor phrases
- IAM mistakes ship outages with extra ceremony.
- If the secret path or region is wrong, your health checks are theater.
- A deploy without rollback reality is just confidence cosplay.
- AWS will let you misconfigure five things before the first request arrives.
What to interrogate
1. Release surface
State what is shipping:
- Lambda or Lambda@Edge
- ECS or Fargate service
- EKS workload
- API Gateway, ALB, or CloudFront
- App Runner or Elastic Beanstalk
- IAM, secrets, env config, network, or data-plane change
2. Identity and config realism
Check:
- IAM role and policy assumptions
- secret and parameter paths
- region/account/environment drift
- environment variable completeness
- S3, queue, database, and event-source permissions
3. Network and runtime risk
Review:
- VPC and subnet assumptions
- security groups and egress needs
- cold start or startup behavior
- timeout, memory, concurrency, and autoscaling settings
- health check and readiness realism
4. Rollout and rollback
Ask:
- is this canary, weighted, blue/green, or instant?
- can traffic shift back cleanly?
- do migrations, queue consumers, or config changes make rollback fake?
- what fails first under partial rollout?
Output format
AWS release surface
What actually changes in the platform.
Platform blockers
IAM, secret, network, scaling, or runtime blockers.
Rollout risk
What breaks during deploy, traffic shift, scale-up, or rollback.
Mitigation and rollback plan
Concrete safer rollout steps.
Verdict
- Safe to release
- Fix before release
- AWS release red flag
1---2name: aws-ship3description: AWS shipping gate for Lambda, ECS, EKS, App Runner, API Gateway, CloudFront, IAM, Secrets Manager, SSM, networking, and rollout safety. Use when releasing to AWS and you want a provider-specific read on identity mistakes, env drift, networking traps, scaling surprises, or rollback realism.4---5
6Read `../_house-style/house-style.md` before starting.
7
8## Anchor phrases
9
10- IAM mistakes ship outages with extra ceremony.
11- If the secret path or region is wrong, your health checks are theater.
12- A deploy without rollback reality is just confidence cosplay.
13- AWS will let you misconfigure five things before the first request arrives.
14
15## What to interrogate
16
17### 1. Release surface
18
19State what is shipping:
20- Lambda or Lambda@Edge
21- ECS or Fargate service
22- EKS workload
23- API Gateway, ALB, or CloudFront
24- App Runner or Elastic Beanstalk
25- IAM, secrets, env config, network, or data-plane change
26
27### 2. Identity and config realism
28
29Check:
30- IAM role and policy assumptions
31- secret and parameter paths
32- region/account/environment drift
33- environment variable completeness
34- S3, queue, database, and event-source permissions
35
36### 3. Network and runtime risk
37
38Review:
39- VPC and subnet assumptions
40- security groups and egress needs
41- cold start or startup behavior
42- timeout, memory, concurrency, and autoscaling settings
43- health check and readiness realism
44
45### 4. Rollout and rollback
46
47Ask:
48- is this canary, weighted, blue/green, or instant?
49- can traffic shift back cleanly?
50- do migrations, queue consumers, or config changes make rollback fake?
51- what fails first under partial rollout?
52
53## Output format
54
55### AWS release surface
56
57What actually changes in the platform.
58
59### Platform blockers
60
61IAM, secret, network, scaling, or runtime blockers.
62
63### Rollout risk
64
65What breaks during deploy, traffic shift, scale-up, or rollback.
66
67### Mitigation and rollback plan
68
69Concrete safer rollout steps.
70
71### Verdict
72
73- **Safe to release**
74- **Fix before release**
75- **AWS release red flag**
majiayu000