12. Cloud platforms and years of experience
Answer as submitted
“Yes — AWS 6+ yrs (certified), Azure 4+ yrs (AZ-204/500) and GCP 3+ yrs (cloud architect).”
Expanded answer
Yes — AWS for 6+ years (certified across Solutions Architect Professional, Security, Database, DevOps Engineer Professional and Advanced Networking), Azure for 4+ years (AZ-204 and AZ-500) and GCP for 3+ years, plus Oracle Cloud exposure. The work covers the full path to production: VPC and network design, IAM and least privilege, containers on ECS/EKS and AKS, serverless for event-shaped work, managed data services (RDS, DynamoDB, DocumentDB, Neptune, Cosmos DB, Cloud SQL/BigQuery), messaging (SQS/SNS, EventBridge, Service Bus, Pub/Sub), infrastructure as code with CDK, CloudFormation and Terraform, and pipelines that authenticate through OIDC instead of long-lived keys.
| Decision | Where it is applied | Why it is done this way |
|---|---|---|
| Infrastructure as code | CDK / CloudFormation / Terraform | Environments are reproducible and reviewed; no console edit becomes drift. |
| Runtime shape | ECS/EKS, AKS, Cloud Run, Lambda | Functions for event work, containers for steady services, managed data behind them. |
| Pipeline identity | OIDC federation to a short-lived role | No static cloud credential exists in the repo or in CI variables. |
| Observability | CloudWatch / App Insights / Cloud Monitoring + OpenTelemetry | Dashboards, traces and SLO alarms ship with the deployable unit. |
| Network & perimeter | private subnets, security groups, WAF, private endpoints | Data services are never reachable from the public internet. |
| Scaling & cost | auto scaling with budgets and alarms | Growth is automatic and its cost is visible before the invoice. |
| Portability | same architecture mapped across AWS, Azure and GCP | Multi-cloud experience is the ability to re-map the design, not to memorise service names. |
Live cloud delivery workflow proof
The running component below changes its decision/result view through real event binding. Select a step to see the platform decision, the reasoning behind it, and the measurement the environment reports.
Choose a delivery step
Select a step to inspect the platform decision, the reasoning and the measured result.
$ cdk deploy / terraform apply — same stack for dev, staging and prod
Environments are declared as code, so a change is reviewed in a pull request, reproducible in another account, and never an undocumented console edit.
stack v42 deployed to dev + prod manual changes pending: 0 · drift detected: none
What "cloud experience" means in practice
Source files
Select a file to inspect the proof with syntax highlighting and line numbers. The first file is the code running the component above; the other two are the production shapes of the same decisions.
Acceptance criteria
- Names AWS, Azure and GCP with the years and the certifications behind each.
- Distinguishes infrastructure, runtime choice, pipeline identity, observability and cost.
- Shows an interactive proof of choosing a delivery step and reading its measurement.
- Keeps identity keyless (OIDC) and data services off the public internet.
- Defers service inventories, landing-zone redesign and multi-region topology to a later topic.