Infrastructure as code
AWS environments written in Terraform, so the environment is a reviewable artefact rather than a sequence of console clicks nobody remembers.
Infrastructure that only one person can rebuild is a liability. I define AWS environments as Terraform code so they are reproducible, reviewable and recoverable — and I have used exactly that approach to move a live platform's infrastructure, users and application data across AWS accounts with minimal downtime.
AWS environments written in Terraform, so the environment is a reviewable artefact rather than a sequence of console clicks nobody remembers.
Moving infrastructure, users and application data between AWS accounts with minimal downtime — rehearsed against a full test environment mirroring production before cutover.
Docker containers behind Nginx on Linux hosts, wired into CI/CD pipelines.
EC2 behind Application Load Balancers with Auto Scaling Groups, sized against real load tests rather than guesswork.
Projects where I have already done this, written up as case studies.
High-scale event ticketing platform stress-tested to 100,000 concurrent users.
Read case study: The Ticket CentralUS real-estate platform — cross-account AWS migration, HLS live streaming, first Play Store release.
Read case study: PropQwizThat is work I have done. On PropQwiz I migrated the complete AWS infrastructure, users and application data across AWS accounts with minimal downtime, writing the target environment as Terraform infrastructure-as-code and rehearsing against a full test environment that mirrored production.
Because a console-built environment cannot be reviewed, diffed or rebuilt. Terraform makes the environment a versioned artefact — which is what turns a migration from a high-risk event into a repeatable operation.
Yes. Docker, Nginx and Linux hosts wired into CI/CD, so deployment is part of the same system rather than a separate manual step.
If aws & cloud infrastructure is what you need, tell me about the system, the constraints and the timeline.