Account foundations and governance
Review or design AWS account boundaries, environment separation and ownership. Scope AWS Organizations, account provisioning, tagging and audit logging around the organisation. Define how engineers request access, make changes and identify the team responsible for each workload.
Identity, security and networking
Design IAM roles, workload permissions and access paths using least privilege. Review VPCs, subnets, routing, load balancing, DNS and connectivity between services. Include secrets handling, encryption and relevant logging in the architecture and implementation scope.
Workload architecture and managed services
Assess the application, dependencies, traffic and operating requirements before selecting services. Options can include EC2, ECS, EKS, Lambda, RDS and S3. Document the availability, maintenance and cost implications of the proposed design with the engineers who will run it.
Migration and modernisation
Inventory dependencies and organise migration work into testable stages. Define data movement, environment validation, cutover, rollback and ownership for each stage. Plan modernisation where it addresses a workload requirement, with checks for compatibility and business continuity.
Infrastructure as code and delivery
Implement reviewable infrastructure using Terraform or the agreed tooling. Structure state, modules and environment configuration; integrate validation and deployment into version control and CI/CD. Document how changes are reviewed, applied and recovered.
Recovery, observability and cost management
Translate recovery expectations into backup, restore and validation tasks. Review telemetry and alerting for the application and infrastructure. Establish spending and capacity baselines, investigate unused resources and assess rightsizing or scaling changes alongside reliability requirements.