Replicating production infrastructure from London → Mumbai
A scoped, low-risk migration that mirrors your proven AWS environment into ap-south-1 — same architecture, one production footprint, one extended pipeline.
replication
Executive summary
This proposal outlines the approach, scope, and commercial terms for replicating the client's existing AWS production infrastructure from the London Region into the AWS Mumbai Region (ap-south-1). The client currently operates a fully validated, production-grade environment in London spanning Development, UAT, and Production, supported by an established GitLab CI/CD pipeline.
The objective of this engagement is not to redesign the existing architecture, but to faithfully mirror the proven London production environment in Mumbai. In line with the client's requirements, only a single Production environment will be deployed in the Mumbai region; Development and UAT environments are excluded from this scope unless requested as a separate engagement.
The existing GitLab CI/CD pipeline will be extended to support deployments to both the London and Mumbai regions, preserving the current deployment workflow and minimizing operational disruption for the client's engineering team.
This engagement is estimated at approximately 60 hours of effort, delivered by a two-person team comprising a Lead DevOps Engineer and a Senior DevOps Engineer, over an estimated project duration of 1.5 weeks (7–8 working days).
Project background
The client currently maintains a fully operational AWS infrastructure in the London Region, comprising three distinct deployment environments: Development, UAT, and Production. This infrastructure is stable, production-proven, and already supported by GitLab CI/CD pipelines that automate deployments to the London region.
The client now wishes to establish equivalent application infrastructure in the AWS Mumbai Region (ap-south-1) to support regional expansion, data residency requirements, or improved latency for users in South Asia.
Objective
Replicate what already works — reduce risk and accelerate delivery by reusing a proven design rather than starting from scratch.
Single production environment
Unlike London, only one Production environment will be deployed in Mumbai. Dev and UAT are excluded unless requested separately.
Pipeline extension
The existing GitLab CI/CD pipeline is extended to target both London and Mumbai, preserving the current workflow.
Scope of work
Twenty-six activities across five delivery areas, grouped the way the build actually happens.
Infrastructure assessment and migration planning precedes all build activity.
Foundation & networking
- VPC
- Public & private subnets
- Security groups
- Route tables
- Internet gateway
- NAT gateway (if required)
Compute, storage & data
- EC2
- EBS
- Amazon RDS migration / setup
- ElastiCache
Delivery & access
- Application load balancer
- Route 53
- Certificate Manager (SSL)
- CloudFront
- API Gateway
- Lambda
Security, messaging & ops
- IAM roles & policies
- AWS KMS
- Amazon SES
- CloudWatch monitoring & logs
Deployment & handover
- GitLab CI/CD config for Mumbai
- Application deployment
- End-to-end testing & validation
- Production readiness verification
- Documentation & handover
Estimated effort
Approximately 60 hours, broken down by task area.
Team allocation
A focused, senior two-person team.
Lead DevOps Engineer
Architecture & readinessOversees architecture validation, migration planning, security, and production readiness.
Senior DevOps Engineer
Build & deliveryHandles infrastructure provisioning, deployment, CI/CD configuration, and testing.
Timeline
1.5 weeks (7–8 working days) end to end.
Assumptions
- Existing London infrastructure will remain unchanged.
- The existing architecture will be reused without major modifications.
- Only one Production environment will be created in Mumbai.
- Existing GitLab repositories and deployment pipelines are available.
- Required AWS access, DNS access, SSL certificates, and application source code will be provided by the client.
- Any new application development, feature enhancements, or infrastructure redesign is outside the scope of this proposal.
If any technical challenges or AWS service limitations arise during the replication process, we will assess the issue, discuss available alternatives with the client, and proceed with the most appropriate solution upon approval.
Deliverables
- Production-ready AWS infrastructure in Mumbai (ap-south-1)
- Infrastructure configured to mirror the London production environment
- Database migrated and validated
- GitLab CI/CD pipeline extended to support Mumbai deployments
- Application successfully deployed
- Monitoring and logging configured
- Infrastructure tested and validated
- Documentation and deployment handover
Next steps
Ready to mirror London in Mumbai?
We welcome the opportunity to walk through scope, timeline, or approach in more detail. On approval, we'll schedule a kickoff to confirm access requirements and begin provisioning.