aws-deploy-safety

Safe AWS deployments require explicit health-check tuning, secrets injection via Secrets Manager, and rollback triggers. This skill standardizes ECS rolling updates, Blue/Green rollouts with CodeDeploy, and Lambda traffic shifting to prevent misconfigurations and outages.

Configuring secrets references securely requires using Secrets Manager to inject values into ECS task definitions rather than plaintext. This approach enforces deployment guardrails and prevents exposing sensitive data during container rollouts.

Blue/Green deployments with CodeDeploy are needed when risk evaluation warrants gradual traffic shifting and immediate rollback capabilities. This strategy ensures health-check integrity and minimizes outage exposure during Lambda or ECS application updates.

Yes, enforcing safe deployment practices explicitly covers App Runner changes alongside ECS and Lambda. It provides guardrails for health-check tuning and rollout strategies to prevent misconfigurations and ensure reliable application rollouts.

Guardrails for Lambda traffic shifting require explicit rollback mechanisms, audit trails, and strict permissions management. This skill provides risk evaluation guidance to ensure serverless deployments maintain health-check integrity and log retention.

Preventing outages during rollouts involves applying standardized deployment patterns with explicit health checks and rollback triggers. This skill enforces safe configurations for ECS task definitions and Lambda updates to catch misconfigurations before traffic shifts.