AWS infrastructure automation platform delivering production-ready cloud infrastructure through codified patterns and automated deployment pipelines.
Last Updated: 2024-01 · Version: 1.0.0
Fastish is an infrastructure-as-a-service platform that reduces time-to-production for AWS workloads. The platform encodes infrastructure decisions into reusable AWS CDK constructs and CloudFormation templates, enabling engineering teams to deploy compliant, well-architected infrastructure without deep AWS expertise.
The platform implements patterns from the AWS Well-Architected Framework across all five pillars:
| Pillar | Implementation | Reference |
|---|---|---|
| Operational Excellence | Infrastructure as code, automated deployments, runbooks | OPS Pillar |
| Security | Least privilege IAM, encryption, network isolation | SEC Pillar |
| Reliability | Multi-AZ deployments, auto-scaling, health checks | REL Pillar |
| Performance Efficiency | Right-sizing, caching, serverless where appropriate | PERF Pillar |
| Cost Optimization | Spot instances, on-demand scaling, cost allocation tags | COST Pillar |
Fastish infrastructure automation directly improves DORA (DevOps Research and Assessment) metrics, the industry-standard measure of software delivery performance established by Google Cloud's State of DevOps research:
| Metric | Definition | Without Fastish | With Fastish | Improvement |
|---|---|---|---|---|
| Deployment Frequency | How often code is deployed to production | Weekly/Monthly | On-demand | 10-30x increase |
| Lead Time for Changes | Time from commit to production | Days to weeks | 30-45 minutes | 95%+ reduction |
| Change Failure Rate | Percentage of deployments causing failures | 15-45% | <5% | Codified patterns |
| Mean Time to Recovery | Time to restore service after incident | Hours | Minutes | IaC + rollback |
flowchart LR
subgraph "Deployment Frequency"
A[Manual Infrastructure] -->|Weeks| B[Production]
C[Fastish CDK] -->|Minutes| D[Production]
end
subgraph "Lead Time"
E[Requirements] --> F[Design] --> G[Implementation] --> H[Testing] --> I[Deploy]
J[Requirements] --> K[Configure CDK Context] --> L[Deploy]
end
Deployment Frequency (DORA Definition): Self-service infrastructure provisioning eliminates ticket-based workflows. Teams deploy when ready, not when infrastructure teams have capacity. This aligns with the DevOps principle of flow.
Lead Time for Changes (DORA Definition): Pre-built, tested CDK constructs eliminate design and implementation phases. Configuration-driven deployment reduces lead time from weeks to under an hour. See Accelerate: The Science of Lean Software for research on lead time impact.
Change Failure Rate (DORA Definition): Codified patterns enforce organizational standards. CloudFormation validation catches misconfigurations before deployment. Nested stack architecture isolates blast radius.
Mean Time to Recovery (DORA Definition): Infrastructure-as-code enables rapid environment recreation per IaC best practices. CloudFormation automatic rollback reverts failed deployments. Observability stack provides immediate visibility into failures.
flowchart TB
subgraph "Open Source Layer"
WEBAPP[aws-webapp-infra<br/>Serverless Apps]
EKS[aws-eks-infra<br/>Kubernetes]
DRUID[aws-druid-infra<br/>Analytics]
CDK[cdk-common<br/>Constructs Library]
end
subgraph "Platform Services Layer"
ORCH[Orchestrator<br/>Release Automation]
PORTAL[Portal<br/>Subscriber Management]
NET[Network<br/>Shared Infrastructure]
REPORT[Reporting<br/>Cost Attribution]
end
subgraph "AWS Foundation"
CF[CloudFormation<br/>Resource Provisioning]
CP[CodePipeline<br/>CI/CD]
COG[Cognito<br/>Identity]
DDB[DynamoDB<br/>State Store]
end
CDK --> WEBAPP
CDK --> EKS
CDK --> DRUID
WEBAPP --> ORCH
EKS --> ORCH
DRUID --> ORCH
ORCH --> CP
PORTAL --> COG
PORTAL --> DDB
REPORT --> DDB
CP --> CF
The deployment pipeline implements AWS CodePipeline with CodeBuild for a fully automated CI/CD workflow:
sequenceDiagram
participant User
participant Portal
participant Orchestrator
participant CodePipeline
participant CodeBuild
participant CloudFormation
participant AWS
User->>Portal: Request Infrastructure
Portal->>Portal: Validate Subscriber (Cognito)
Portal->>Orchestrator: Trigger Release Pipeline
Orchestrator->>CodePipeline: StartPipelineExecution
rect rgb(240, 240, 240)
Note over CodePipeline,CodeBuild: Source Stage
CodePipeline->>CodePipeline: Checkout from GitHub (CodeConnection)
end
rect rgb(240, 240, 240)
Note over CodePipeline,CodeBuild: Build Stage
CodePipeline->>CodeBuild: Maven Build
CodeBuild->>CodeBuild: mvn clean install
CodeBuild->>CodeBuild: cdk synth
end
rect rgb(240, 240, 240)
Note over CodePipeline,CloudFormation: Deploy Stage
CodePipeline->>CloudFormation: CreateChangeSet
CloudFormation->>CloudFormation: ExecuteChangeSet
CloudFormation->>AWS: Provision Resources
end
AWS-->>CloudFormation: Resources Created
CloudFormation-->>CodePipeline: Stack Outputs
CodePipeline-->>Orchestrator: Pipeline Success
Orchestrator-->>Portal: Update Deployment Status
Portal-->>User: Infrastructure Ready
The build process uses Mustache templating with Jackson YAML for type-safe configuration:
flowchart LR
subgraph "Input"
CTX[cdk.context.json<br/>AWS Account, Region]
TPL[*.mustache templates<br/>YAML Configuration]
end
subgraph "Processing"
RES[Template Resolution<br/>environment/version path]
MUS[Mustache Engine<br/>Variable Substitution]
JAC[Jackson YAML<br/>YAML Parsing]
POJO[Java POJOs<br/>Type-Safe Config]
end
subgraph "Output"
CDK[CDK Constructs<br/>L2/L3 Abstractions]
CFN[CloudFormation<br/>JSON/YAML Templates]
AWS[AWS Resources<br/>Deployed Infrastructure]
end
CTX --> RES
TPL --> RES
RES --> MUS
MUS --> JAC
JAC --> POJO
POJO --> CDK
CDK --> CFN
CFN --> AWS
Processing Stages:
| Stage | Technology | Purpose | Reference |
|---|---|---|---|
| Template Resolution | Java ClassLoader | Load templates from {environment}/{version}/ path |
Resource Loading |
| Mustache Processing | JMustache | Logic-less template variable substitution | Mustache Manual |
| YAML Parsing | Jackson YAML | Convert YAML to Java objects | Jackson Docs |
| CDK Synthesis | AWS CDK | Generate CloudFormation from constructs | CDK Concepts |
Production-ready serverless web application infrastructure implementing a multi-tier architecture following AWS Serverless Application Lens patterns.
flowchart TB
subgraph "Public Subnet"
IGW[Internet Gateway]
NAT[NAT Gateway<br/>Egress Only]
end
subgraph "Private Subnet"
COG[Cognito User Pool<br/>Authentication]
APIGW[API Gateway<br/>REST API]
LAMBDA[Lambda Functions<br/>Business Logic]
DDB[(DynamoDB Tables<br/>NoSQL Storage)]
end
subgraph "Edge Services"
SES[SES<br/>Transactional Email]
R53[Route 53<br/>DNS Management]
end
Client([Client Application]) --> IGW
IGW --> APIGW
APIGW -->|Cognito Authorizer| COG
APIGW -->|Lambda Proxy| LAMBDA
LAMBDA --> DDB
COG -->|Email Verification| SES
SES --> R53
LAMBDA -->|External APIs| NAT
NAT --> IGW
| Component | AWS Service | Purpose | Configuration | Reference |
|---|---|---|---|---|
| Network | Amazon VPC | Network isolation with public/private subnets | 2 AZs, /16 CIDR | VPC User Guide |
| Authentication | Amazon Cognito | User pools with JWT tokens, MFA support | Email verification, password policy | Cognito Developer Guide |
| Database | Amazon DynamoDB | NoSQL with on-demand capacity | PAY_PER_REQUEST billing | DynamoDB Developer Guide |
| Amazon SES | DKIM-signed transactional email | Domain + email verification | SES Developer Guide | |
| API | Amazon API Gateway | REST API with Lambda proxy integration | Cognito authorizer, CORS | API Gateway Developer Guide |
| Compute | AWS Lambda | Serverless functions in VPC | Java 21, ARM64 | Lambda Developer Guide |
Deployment Metrics:
- Time: 15-20 minutes
- Stacks: 6 (1 main + 5 nested)
- Monthly Cost: $50-500 depending on traffic
Enterprise-grade Kubernetes cluster following EKS Best Practices Guide with production observability and autoscaling.
flowchart TB
subgraph "Control Plane (AWS Managed)"
EKS[EKS API Server<br/>Kubernetes 1.28+]
ETCD[(etcd<br/>Cluster State)]
end
subgraph "Data Plane"
subgraph "Managed Node Group"
NG[Bottlerocket Nodes<br/>On-Demand]
end
subgraph "Karpenter Provisioned"
KARP[Mixed Nodes<br/>Spot + On-Demand]
end
end
subgraph "Networking Layer"
VPCCNI[VPC CNI<br/>Pod Networking]
ALB[ALB Controller<br/>Ingress]
CERT[cert-manager<br/>TLS Certificates]
end
subgraph "Observability Layer"
OTEL[OpenTelemetry Collector<br/>Telemetry Pipeline]
GRAF[Grafana Cloud<br/>Mimir, Loki, Tempo]
CW[CloudWatch<br/>Container Insights]
end
subgraph "Security Layer"
EBS[EBS CSI Driver<br/>Persistent Volumes]
SEC[Secrets Store CSI<br/>AWS Secrets Manager]
POD[Pod Identity Agent<br/>IAM Roles for Pods]
end
EKS --> NG
EKS --> KARP
NG --> VPCCNI
KARP --> VPCCNI
VPCCNI --> ALB
ALB --> CERT
NG --> OTEL
KARP --> OTEL
OTEL --> GRAF
OTEL --> CW
NG --> EBS
NG --> SEC
NG --> POD
AWS Managed EKS Add-ons (EKS Add-ons):
| Add-on | Version | Purpose | Reference |
|---|---|---|---|
| vpc-cni | Latest | Pod networking with VPC IPs | VPC CNI |
| coredns | Latest | Cluster DNS | CoreDNS |
| kube-proxy | Latest | Service networking | kube-proxy |
| aws-ebs-csi-driver | Latest | EBS persistent volumes | EBS CSI |
| eks-pod-identity-agent | Latest | IAM for pods | Pod Identity |
| amazon-cloudwatch-observability | Latest | Container Insights | Container Insights |
Helm Chart Add-ons:
| Chart | Purpose | Reference |
|---|---|---|
| cert-manager | TLS certificate automation | cert-manager.io |
| aws-load-balancer-controller | ALB/NLB provisioning | AWS LB Controller |
| karpenter | Node autoscaling | karpenter.sh |
| secrets-store-csi-driver | External secrets mounting | Secrets Store CSI |
Deployment Metrics:
- Time: 25-35 minutes
- Stacks: 4+ (1 main + nested)
- Monthly Cost: $150-2000+ depending on node count
Apache Druid OLAP analytics platform on EKS with integrated AWS managed services for real-time and batch analytics, following Druid documentation best practices.
flowchart TB
subgraph "Data Ingestion"
KAFKA[Amazon MSK<br/>Kafka Streaming]
S3IN[S3 Bucket<br/>Batch Ingestion]
end
subgraph "Druid Cluster on EKS"
subgraph "Master Services"
COORD[Coordinator<br/>Segment Management]
OVER[Overlord<br/>Task Scheduling]
end
subgraph "Query Services"
ROUTER[Router<br/>Query Routing]
BROKER[Broker<br/>Query Execution]
end
subgraph "Data Services"
HIST[Historical<br/>Segment Storage]
MM[MiddleManager<br/>Ingestion Tasks]
end
end
subgraph "AWS Managed Storage"
RDS[(RDS PostgreSQL<br/>Metadata Store)]
S3DEEP[S3 Bucket<br/>Deep Storage]
S3MSQ[S3 Bucket<br/>MSQ Scratch]
end
subgraph "Query Clients"
CONSOLE[Druid Console<br/>Web UI]
JDBC[JDBC/Avatica<br/>SQL Clients]
API[HTTP API<br/>Native Queries]
end
KAFKA --> MM
S3IN --> MM
MM --> OVER
OVER --> COORD
COORD --> RDS
MM --> S3DEEP
HIST --> S3DEEP
CONSOLE --> ROUTER
JDBC --> BROKER
API --> BROKER
ROUTER --> BROKER
BROKER --> HIST
Druid Process Types (Architecture):
| Process | Role | Scaling | Reference |
|---|---|---|---|
| Coordinator | Segment management, load balancing | 2 replicas (HA) | Coordinator |
| Overlord | Task scheduling, ingestion management | 2 replicas (HA) | Overlord |
| Broker | Query routing, result merging | Horizontal | Broker |
| Router | API gateway, console hosting | Horizontal | Router |
| Historical | Segment storage, query serving | Horizontal | Historical |
| MiddleManager | Ingestion task execution | Horizontal | MiddleManager |
AWS Service Integration:
| Service | Druid Component | Configuration | Reference |
|---|---|---|---|
| RDS PostgreSQL | Metadata Storage | db.t3.medium, Multi-AZ | Metadata Storage |
| S3 | Deep Storage | Standard tier, lifecycle policies | S3 Extension |
| S3 | MSQ Scratch Space | Temporary query results | MSQ |
| MSK | Real-time Ingestion | kafka.m5.large, 3 brokers | Kafka Ingestion |
Deployment Metrics:
- Time: 35-45 minutes
- Stacks: 5 (1 main + 4 nested)
- Monthly Cost: $500-5000+ depending on data volume
Enterprise AWS CDK constructs library providing reusable L2 and L3 constructs for all infrastructure projects.
flowchart LR
subgraph "AWS Service Constructs"
direction TB
COMPUTE[Compute<br/>Lambda, EKS]
STORAGE[Storage<br/>S3, EBS]
DATABASE[Database<br/>DynamoDB, RDS]
NETWORK[Network<br/>VPC, API GW, ALB]
SECURITY[Security<br/>IAM, Cognito, KMS]
MESSAGING[Messaging<br/>SQS, SNS, SES]
ANALYTICS[Analytics<br/>Athena, MSK, Kinesis]
DEVOPS[DevOps<br/>CodeBuild, ECR]
end
subgraph "Build Pipeline"
CTX[CDK Context<br/>cdk.context.json] --> TPL[Template Resolution<br/>ClassLoader]
TPL --> MUS[Mustache Processing<br/>JMustache]
MUS --> YAML[YAML Parsing<br/>Jackson]
YAML --> POJO[Java POJOs<br/>Config Objects]
POJO --> CDK[CDK Synthesis<br/>Construct Tree]
end
CDK --> COMPUTE
CDK --> STORAGE
CDK --> DATABASE
CDK --> NETWORK
CDK --> SECURITY
CDK --> MESSAGING
CDK --> ANALYTICS
CDK --> DEVOPS
Supported AWS Services:
| Category | Services | Reference |
|---|---|---|
| Compute | Lambda, EKS, ECS | Lambda, EKS |
| Storage | S3, EBS, EFS | S3, EBS |
| Database | DynamoDB, RDS, ElastiCache | DynamoDB, RDS |
| Networking | VPC, API Gateway, ALB, NLB | VPC, API GW |
| Security | IAM, Cognito, KMS, Secrets Manager | IAM, Cognito |
| Messaging | SQS, SNS, SES, EventBridge | SQS, SNS |
| Analytics | Athena, MSK, Kinesis, Glue | Athena, MSK |
| DevOps | CodeBuild, CodePipeline, ECR | CodeBuild, ECR |
Internal services that coordinate deployment automation, multi-tenant management, and usage tracking. These services are not open source but integrate with the open source infrastructure projects.
flowchart TB
subgraph "Orchestrator Service"
AGENTS[CodeBuild Agents<br/>mvn, synth, deploy]
PIPES[CodePipeline V2<br/>Release Pipelines]
ASSETS[S3 Bucket<br/>Build Artifacts]
end
subgraph "Portal Service"
APIGW[API Gateway<br/>REST API]
AUTH[Cognito<br/>User Authentication]
DATA[(DynamoDB<br/>Subscriber Data)]
FN[Lambda<br/>Business Logic]
end
subgraph "Network Service"
VPC[Transit VPC<br/>Hub Network]
PEER[VPC Peering<br/>Spoke Connections]
DNS[Route 53<br/>Private Hosted Zones]
end
subgraph "Reporting Service"
BCM[BCM Data Export<br/>Cost & Usage]
METER[(DynamoDB<br/>Usage Records)]
ATHENA[Athena<br/>Cost Analysis]
end
APIGW --> FN
FN --> AUTH
FN --> DATA
FN --> PIPES
PIPES --> AGENTS
AGENTS --> ASSETS
FN --> VPC
VPC --> PEER
PEER --> DNS
PIPES --> METER
BCM --> ATHENA
| Service | Purpose | Key Technologies | Integration |
|---|---|---|---|
| Orchestrator | Release pipeline automation | CodePipeline V2, CodeBuild | Deploys aws-*-infra stacks |
| Portal | Multi-tenant subscriber management | API Gateway, Cognito, DynamoDB | Triggers orchestrator pipelines |
| Network | Shared infrastructure connectivity | Transit Gateway, VPC Peering | Connects subscriber VPCs |
| Reporting | Usage metering and cost attribution | BCM Data Export, Athena | Tracks deployment costs |
gantt
title Platform Deployment Timeline
dateFormat mm:ss
axisFormat %M:%S
section Phase 1 - Foundation
IAM Roles & OIDC Provider :p1a, 00:00, 5m
BCM Data Export Config :p1b, 00:00, 5m
section Phase 2 - Core Services
Orchestrator Agents :p2a, after p1a, 15m
Reporting Infrastructure :p2b, after p1a, 15m
section Phase 3 - Platform
Portal Backend :p3, after p2a, 15m
section Phase 4 - Frontend
Portal UI (Amplify) :p4, after p3, 10m
| Phase | Components | Duration | CloudFormation Stacks |
|---|---|---|---|
| Phase 1 | IAM roles, OIDC provider, BCM configuration | 5-10 min | 2 |
| Phase 2 | CodeBuild agents, reporting DynamoDB tables | 15-20 min | 4 |
| Phase 3 | API Gateway, Cognito, Lambda functions | 10-15 min | 3 |
| Phase 4 | Amplify hosting, CloudFront | 5-10 min | 2 |
Total Platform Deployment: 35-55 minutes
| Tool | Version | Purpose | Installation | Verification |
|---|---|---|---|---|
| Java | 21+ (LTS) | CDK constructs runtime | SDKMAN or Adoptium | java --version |
| Maven | 3.8+ | Build automation | Maven Download | mvn --version |
| AWS CLI | 2.x | AWS API access | AWS CLI Install | aws --version |
| AWS CDK CLI | 2.221.0+ | CDK synthesis and deployment | npm install -g aws-cdk |
cdk --version |
| Node.js | 18+ (LTS) | CDK CLI runtime | Node.js Downloads | node --version |
| GitHub CLI | Latest | Repository cloning | GitHub CLI | gh --version |
- AWS Credentials: Configure via AWS CLI or environment variables
# Verify credentials
aws sts get-caller-identity- CDK Bootstrap: One-time setup per account/region (CDK Bootstrapping)
cdk bootstrap aws://<account-id>/<region>This creates:
- S3 bucket for CDK assets
- ECR repository for Docker images
- IAM roles for CloudFormation deployment
# 1. Clone repositories
gh repo clone fast-ish/cdk-common
gh repo clone fast-ish/aws-webapp-infra
# 2. Build projects
mvn -f cdk-common/pom.xml clean install
mvn -f aws-webapp-infra/pom.xml clean install
# 3. Configure deployment
cp aws-webapp-infra/infra/cdk.context.template.json \
aws-webapp-infra/infra/cdk.context.json
# Edit cdk.context.json with your AWS account details
# 4. Deploy
cd aws-webapp-infra/infra
cdk synth # Validate templates (outputs to cdk.out/)
cdk diff # Preview changes
cdk deploy # Provision resources| Parameter | Type | Description | Example |
|---|---|---|---|
:account |
String | AWS account ID (12 digits) | 123456789012 |
:region |
String | AWS region | us-west-2 |
:environment |
String | Environment name (maps to template path) | prototype |
:version |
String | Version identifier (maps to template path) | v1 |
:domain |
String | Route 53 hosted zone domain | example.com |
| Technology | Version | Purpose | Reference |
|---|---|---|---|
| AWS CDK | 2.221.0 | Infrastructure definition in Java | AWS CDK |
| CloudFormation | - | Resource provisioning | CloudFormation |
| Mustache | 0.9.x | Configuration templating | Mustache Manual |
| Jackson | 2.17.x | YAML/JSON processing | Jackson Docs |
| Technology | Version | Purpose | Reference |
|---|---|---|---|
| Amazon EKS | 1.28+ | Managed Kubernetes | EKS User Guide |
| Karpenter | 0.37+ | Node autoscaling | Karpenter Docs |
| Bottlerocket | Latest | Container-optimized OS | Bottlerocket |
| Helm | 3.x | Kubernetes package manager | Helm Docs |
| Technology | Version | Purpose | Reference |
|---|---|---|---|
| Apache Druid | 28+ | Real-time OLAP | Druid Docs |
| Amazon MSK | 3.5+ | Managed Kafka | MSK Developer Guide |
| Amazon Athena | v3 | SQL on S3 | Athena User Guide |
| Amazon Kinesis | - | Real-time streaming | Kinesis Developer Guide |
| Technology | Purpose | Reference |
|---|---|---|
| Grafana Cloud | Metrics (Mimir), Logs (Loki), Traces (Tempo), Profiles (Pyroscope) | Grafana Cloud Docs |
| OpenTelemetry | Telemetry collection and export | OpenTelemetry Docs |
| CloudWatch | AWS-native monitoring | CloudWatch User Guide |
| Prometheus | Metrics collection | Prometheus Docs |
Every component implements defense-in-depth:
| Layer | Implementation | AWS Services | Reference |
|---|---|---|---|
| Network | Private subnets, security groups, NACLs | VPC, Security Groups | VPC Security |
| Identity | Least privilege IAM, Pod Identity, OIDC | IAM, Cognito | IAM Best Practices |
| Data | Encryption at rest (KMS), in transit (TLS 1.3) | KMS, ACM | Encryption |
| Compute | Bottlerocket AMI, ECR image scanning | EKS, ECR | Container Security |
| Audit | CloudTrail, CloudWatch Logs, VPC Flow Logs | CloudTrail, CloudWatch | Logging |
| Principle | Implementation | Reference |
|---|---|---|
| Infrastructure as Code | All resources in CDK, version controlled in Git | IaC Whitepaper |
| Automated Deployment | CodePipeline orchestration, zero manual steps | CI/CD on AWS |
| Immutable Infrastructure | Replace resources, never patch in place | Immutable Infrastructure |
| Observability | Metrics, logs, traces from deployment | Observability |
| Rollback Capability | CloudFormation automatic rollback | Stack Failure Options |
| Strategy | Implementation | Reference |
|---|---|---|
| Right-sizing | Karpenter selects optimal instance types | Right Sizing |
| Spot Instances | Karpenter Spot integration for fault-tolerant workloads | Spot Best Practices |
| On-demand Scaling | DynamoDB on-demand, Lambda pay-per-invocation | Serverless Pricing |
| Cost Allocation | Tagging strategy, BCM export, Athena analysis | Cost Allocation Tags |
| Document | Audience | Description |
|---|---|---|
| Usage Examples | All | Real-world deployment scenarios from modernization to AI |
| Glossary | All | Platform terminology and AWS service definitions |
| Changelog | All | Version history and release notes |
| Document | Audience | Description |
|---|---|---|
| Capacity Planning | Architects, DevOps | Sizing recommendations and cost estimates |
| Network Requirements | Network Engineers | CIDR planning, ports, security groups |
| IAM Permissions | Security, DevOps | Minimum permissions for deployment |
| Document | Audience | Description |
|---|---|---|
| Deployment Validation | DevOps, SRE | Post-deployment health checks and verification |
| Upgrade Guide | DevOps, SRE | Version upgrades and rollback procedures |
| Troubleshooting | Operations | Common issues and resolutions |
| Document | Audience | Description |
|---|---|---|
| cdk-common API | Engineers | Construct library reference |
| aws-webapp-infra | Engineers | Serverless web application |
| aws-eks-infra | Engineers | EKS Kubernetes cluster |
| aws-druid-infra | Engineers | Apache Druid analytics |
| Resource | Description |
|---|---|
| AWS CDK Developer Guide | Official CDK documentation |
| AWS CDK API Reference | CDK construct library reference |
| CloudFormation User Guide | CloudFormation resource reference |
| EKS Best Practices Guide | Production EKS guidance |
| Serverless Application Lens | Serverless architecture patterns |
| Well-Architected Framework | All five pillars documentation |
| Resource | Description |
|---|---|
| DORA Metrics | DevOps Research and Assessment |
| Accelerate Book | Science of DevOps research |
| Apache Druid Documentation | Druid architecture and operations |
| Kubernetes Documentation | Official Kubernetes docs |
| Karpenter Documentation | Karpenter autoscaler reference |
| Repository | Description |
|---|---|
| aws-webapp-infra | Serverless web application infrastructure |
| aws-eks-infra | Amazon EKS Kubernetes cluster |
| aws-druid-infra | Apache Druid analytics platform |
| cdk-common | Shared CDK constructs library |
| Channel | Purpose | Response Time |
|---|---|---|
| GitHub Issues | Bug reports, feature requests | Best effort |
| Documentation | Self-service guides | Immediate |
| Troubleshooting Guide | Common issues | Immediate |
When opening an issue, please include:
- Project and version (e.g., aws-eks-infra v1.0.0)
- AWS region
- CDK CLI version (
cdk --version) - Error message or unexpected behavior
- Relevant
cdk.context.json(redact account IDs)
All open source projects are licensed under the MIT License.
Last Updated: 2024-01 · Source: github.com/fast-ish