01
Design AWS workloads
Map requirements to suitable managed services, account and network boundaries, availability patterns, data flows, scaling behavior, and failure recovery.
AWS cloud engineering
CategoryCloud & DevOps
AWS Codex Skills
AWS Codex Skills give Codex a disciplined workflow for designing, provisioning, securing, testing, and operating workloads on Amazon Web Services. Download the skills for infrastructure as code, serverless applications, containers, delivery pipelines, observability, cost reviews, and changes that need a safe rollback path.
AWS architectureInfrastructure as codeCloud securityOperations
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete aws cloud engineering task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A cloud change can deploy successfully and still create an expensive, insecure, or fragile system.
AWS work crosses identity, networking, compute, data, observability, deployment, resilience, and cost. The right service depends on workload behavior and operational constraints, not novelty.
These skills make Codex inspect the account model, region, existing infrastructure, security boundaries, quotas, recovery objectives, and delivery process before proposing a change.
What the downloadable skills can do
What AWS Codex Skills can help accomplish
02
Build infrastructure as code
Create or improve AWS CDK, CloudFormation, Terraform, and supporting configuration with reviewable plans and controlled state.
03
Develop cloud applications
Work on Lambda, API Gateway, ECS, EKS, S3, CloudFront, queues, event-driven systems, databases, and application integrations.
04
Secure and operate systems
Apply least privilege, encryption, secrets handling, logs, metrics, alarms, backups, cost controls, deployment checks, and rollback procedures.
A repeatable working process
How the aws cloud engineering workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Inspect the cloud context
Record accounts, regions, environments, identity boundaries, networks, services, data sensitivity, quotas, budgets, and ownership.
02
Choose the architecture deliberately
Compare service fit, operational load, availability, performance, security, portability, and total cost before committing.
03
Implement through controlled code
Make focused application and infrastructure changes, review plans, protect state and credentials, and preserve environment separation.
04
Verify and prepare recovery
Run tests and policy checks, inspect deployment health and spend signals, confirm backups, and document rollback.
Useful across real projects
Where AWS Codex Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Serverless systems
Build functions, APIs, queues, events, workflows, storage, permissions, retries, idempotency, and observability.
Container platforms
Develop ECS or EKS services, images, task definitions, networking, autoscaling, secrets, health checks, and deployment strategies.
Data platforms
Design ingestion, storage, processing, databases, analytics, access controls, retention, backups, and cost-aware queries.
Platform foundations
Create accounts, networks, identity patterns, shared services, CI/CD, policy checks, monitoring, and reusable infrastructure modules.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Design an AWS architecture
02Write CDK or CloudFormation
03Build a serverless API
04Configure ECS or EKS
05Review IAM permissions
06Create a deployment pipeline
07Add monitoring and alarms
08Investigate AWS cost or reliability issues
Who benefits most
Who Is This For?
These skills are designed for people who need dependable aws cloud engineering work with a visible process.
Cloud engineers
Build and operate AWS systems with explicit security, reliability, cost, and recovery decisions.
Backend developers
Connect applications to AWS compute, storage, databases, events, identity, and observability services.
Platform and DevOps teams
Create reusable infrastructure, delivery pipelines, account standards, controls, and operational tooling.
Solution architects
Turn workload requirements into reviewable architectures and implementation plans.
Good to know:
The skills can prepare and validate AWS changes, but account access, credentials, production deployment, destructive operations, compliance decisions, and material spending require explicit authorization and qualified review.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the AWS skills
Keep SKILL.md with architecture, infrastructure, security, cost, deployment, and operational references.
Choose project or personal scope
Use project scope for one AWS workload, or personal scope for reusable cloud-engineering practices.
Document the AWS environment
Provide accounts, regions, services, network boundaries, IaC tool, environments, deployment process, budgets, and recovery targets.
Configure safe access
Use approved profiles or roles with least privilege, protect secrets, and require review for production or destructive actions.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Can the skills write AWS CDK or CloudFormation?+
Yes. They can create, review, test, and explain infrastructure code while following the repository's chosen language and deployment process.
Do they support Terraform on AWS?+
Yes. They can work with modules, plans, state boundaries, providers, imports, policy checks, and controlled applies.
Can they deploy AWS resources?+
Only when explicitly authorized and supplied with suitable access, an approved plan, validation checks, and a recovery path.
Will they review AWS security?+
They can inspect identity, network exposure, encryption, secrets, logging, data handling, and common misconfigurations. Formal assurance still needs security review.
Can they help reduce AWS costs?+
They can analyze architecture, utilization, storage, data transfer, scaling, commitments, and idle resources when trustworthy usage and billing data are available.
Make the work repeatable
Give Codex an AWS workflow that treats architecture, security, cost, deployment, and recovery as one engineering problem.
Clear context. Purposeful work. Relevant checks. A result others can understand.