CLOUD PATTERNS
AWS work
Cloud systems that are repeatable, secure, and diagnosable — not a collection of manual console settings.
Infrastructure as code
- AWS CDK stacks written in TypeScript
- Environment-aware configuration and resource naming
- Repeatable deployment patterns
- Explicit network and security boundaries
Compute and events
- AWS Lambda workloads for analysis and processing
- SNS topics and Lambda subscriptions for event-driven flows
- Runtime configuration, memory, timeout, and execution behavior
- API integrations between internal services
Networking and security
- VPC-connected workloads and private service endpoints
- Security groups and controlled network access
- IAM policies scoped to required actions
- Operational access designed around explicit permissions
Architecture shape
flowchart TD
A["Infrastructure as code (AWS CDK, TypeScript)"] --> B["Private network + scoped permissions (VPC, security groups, IAM)"]
B --> C["Event source (SNS)"]
C --> D["Lambda processing"]
D --> E["Service integration"]
E --> F["Observable outcome and actionable feedback"]
classDef compute fill:#0e7490,color:#fbfaf6,stroke:#0e7490
classDef outcome fill:#12212b,color:#b9eee8,stroke:#12212b
class C,D compute
class F outcome
Engineering approach
- Prefer infrastructure that can be reviewed as code.
- Make resource dependencies and permissions visible.
- Design for failure, retries, timeouts, and useful logs.
- Separate environment configuration from application behavior.