AWS Platform Build and GCP Migration
£3000-5000 GBP
Posted 1 minute ago
•
Ends in 6 days
£3000-5000 GBP
Paid on delivery
AWS platform build and GCP to AWS migration (FastAPI, React, Bedrock, Terraform, Bitbucket) DESCRIPTION: We are a UK EdTech SaaS company currently running on Google Cloud. We are looking for an experienced AWS DevOps engineer to do four things: design and build our AWS platform, migrate us off GCP, move our code to Bitbucket, and modernise our release process. Phase 1 is a fixed-price project. After that, we want ongoing support and ad-hoc work from the right person. CURRENT STACK (GCP) - Backend: Python FastAPI containers on Cloud Run - Frontend: React / Vite / TypeScript on Firebase Hosting - Database: Cloud SQL PostgreSQL 15 with pgvector - Cache: Memorystore (Redis) - Secret Manager, Artifact Registry - Claude models via Vertex AI (EU), plus self-hosted PII pseudonymisation services (Presidio, GLiNER) - GitHub (3 repos) with Cloud Build triggers; Terraform partly in place - Auth: Microsoft 365 / Entra ID SSO plus email/password - Environments: dev, staging, demo, prod PHASE 1 SCOPE (FIXED QUOTE) 1. AWS foundation: multi-account setup (Organizations / Control Tower), IAM Identity Center with least privilege, CloudTrail, GuardDuty, Security Hub, budgets and cost alerts. Primary region eu-west-2 (London). 2. Platform, fully in Terraform: ECS Fargate for the API and pseudonymisation services, S3 + CloudFront for the frontend, RDS PostgreSQL with pgvector, ElastiCache, Secrets Manager, ECR, WAF, private networking with VPC endpoints, CloudWatch logs, metrics and alerting. 3. Amazon Bedrock: Claude models in an EU region with IAM-scoped access, private endpoints, quotas and logging configured to our data policy. Our developers make the application code change; you provide the infrastructure and a working reference example. 4. Migration: Postgres migration with minimal downtime, DNS cutover, tested rollback plan, GCP decommission plan. 5. Source control and CI/CD: move all repos from GitHub to Bitbucket Cloud with full history. Rebuild pipelines in Bitbucket Pipelines using OIDC to AWS (no long-lived keys). Set up the Jira integration. 6. Release model: move to continuous delivery. Trunk-based development. Every merge to main is built once, tested, scanned and deployed automatically to staging. Production is a one-click approved promotion of the same artifact. Ephemeral preview environments per pull request replace dev. Demo is a stable environment running the current production release with seeded data. Zero-downtime deploys and automated rollback. 7. Backups: AWS Backup with production backups held in the UK, plus a tested restore. 8. Handover: architecture diagram, runbooks and a recorded walkthrough for our team. IMPORTANT - We hold ISO 27001, ISO 42001 and ISO 9001. You will follow our security policies and produce evidence for change management, access control and logging. - We handle school data, including children's data. You must sign an NDA and data processing terms before access, and work only through accounts we provide. No production data on personal devices. UK or EU based preferred. PHASE 2 (TO DISCUSS AFTER) Ongoing support retainer (monitoring, patching, cost reviews, incident response) and ad-hoc projects. TO APPLY, PLEASE INCLUDE - Fixed price and timeline for Phase 1, split into milestones - Your day rate for ongoing support - Two GCP to AWS (or similar) migrations you have delivered - AWS certifications held - Your experience with Bedrock and Bitbucket Pipelines Applications that do not answer these points will not be considered.
Project ID: 40829365
About the project
22 proposals
Open for bidding
Remote project
Active 7 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
22 freelancers are bidding on average £3,568 GBP for this job


Hi there, Thank you for outlining your requirements in such detail. I understand the importance of a secure, seamless migration from GCP to AWS—especially for a SaaS platform handling sensitive school data under strict compliance standards. I have extensive experience designing AWS environments with security and cost controls at the forefront, leveraging Control Tower, IAM Identity Center, WAF, and full Terraform automation. I have delivered two end-to-end migrations for EdTech and fintech clients, including a Python/React stack from GCP (Cloud Run, Cloud SQL, Firebase) to AWS (ECS Fargate, RDS, S3/CloudFront, ElastiCache) with minimal downtime and robust rollback strategies. Both involved CI/CD replatforming (including Bitbucket Pipelines with OIDC integration and Jira), full source control history migration, and zero-downtime deployment models. I am an AWS Certified Solutions Architect and DevOps Engineer. My experience with Bedrock includes provisioning secure, quota-managed access to foundation models, setting up private endpoints, and building reference implementations for development teams. I have also managed Bitbucket Pipelines for trunk-based, one-click release workflows, with automated deploys, ephemeral environments, and disaster recovery built-in. For this project, I will provide a multi-account AWS setup, migration planning with tested rollback, fully Terraform-managed infrastructure, CI/CD pipelines in Bitbucket, and comprehensive handover materials. I am committed to following your ISO and data security requirements, with full documentation and evidence for auditability. Looking forward to collaborating on a secure, modern AWS platform for your team. Best Regards


Hello, Your AWS foundation and GCP migration requires secure, repeatable infrastructure, not simply a cloud lift-and-shift. I can deliver Phase 1 around a fully Terraform-managed AWS platform in eu-west-2, with multi-account governance, least-privilege IAM, security controls, private networking, ECS Fargate, RDS PostgreSQL with pgvector, ElastiCache, Bedrock access, observability, backups, and documented recovery procedures. I would structure delivery into milestones: 1. Discovery, target architecture, migration plan, compliance evidence plan, and AWS organization foundation. 2. Core platform, networking, security services, data services, secrets, container hosting, and Bedrock reference infrastructure. 3. Repository migration to Bitbucket, OIDC-based pipelines, Jira integration, trunk-based continuous delivery, previews, promotions, rollback, and zero-downtime deployment. 4. PostgreSQL migration rehearsal and cutover, DNS transition, restore testing, GCP decommission plan, runbooks, diagrams, and recorded handover. I will work exclusively through your provided accounts, respect NDA/data-processing requirements, and avoid production data on personal devices. The implementation will include audit-ready evidence for access control, logging, changes, backups, and restores. My proposal can include the requested fixed-price milestone schedule, ongoing support day rate, relevant GCP-to-AWS migration examples, AWS certifications, and Bedrock/Bitbucket Pipelines experience in the


⭐⭐⭐⭐⭐ Hi there, Could you please confirm that you need a secure, Terraform-managed AWS platform and full GCP-to-AWS migration delivered in Phase 1? Your main priorities are a compliant UK AWS foundation, minimal-downtime PostgreSQL migration, and a reliable Bitbucket release process across four environments. Particular care is needed for children’s data, least-privilege access, audit evidence, rollback, and zero-downtime deployments. I have delivered cloud SaaS foundations with Python services, containerized deployments, infrastructure automation, CI/CD pipelines, managed databases, secrets, monitoring, and AI-service integrations. I can structure the work into milestones covering foundation, platform, migration, delivery automation, testing, and handover. ❓ What is your preferred migration window and maximum acceptable PostgreSQL downtime? ❓ Do you already have an AWS Organization, or should Phase 1 start from a new management account? The technical focus is building repeatable AWS infrastructure and automated releases that are secure, observable, and easy for your team to operate. I am ready to begin immediately after the NDA and access process are completed. I hope to hear from you and discuss the milestones, evidence requirements, and ongoing support. Best regards, Phuong Nam D


UK or EU based on request — I’m based in the UK. I’ve delivered two cloud migrations of this type: a GCP Cloud Run/Firebase stack to AWS ECS Fargate + CloudFront for a fintech SaaS, and a multi-account AWS landing zone with Terraform, OIDC pipelines, and RDS pgvector for a healthtech platform (both involved Entra ID SSO). I hold AWS Solutions Architect Professional and Security Specialty. For Phase 1, I’d start by mapping your existing IAM, networking, and data flows into a Control Tower landing zone with eu-west-2 as the home region, then build the ECS, RDS, ElastiCache, and Bedrock infrastructure as Terraform modules. PostgreSQL migration would use DMS with a validation window before cutover, so rollback stays clean. Bitbucket Pipelines with OIDC keeps deployments keyless, and I’d set up trunk-based staging plus a one-click production promotion. Fixed price: I’d scope this at £4,800 across four milestones — AWS foundation and accounts (25%), Terraform platform build (35%), migration and cutover (25%), CI/CD and handover (15%). Day rate for support: £450. Are your four environments currently isolated at the GCP project level, or do they share networking?


Hi, Had a look through the job and this is pretty straightforward from my side. I'd start by confirming the must-have scope and current constraints, then implement in clear steps so nothing important gets missed and the code stays maintainable. I can own the backend/API work, keep the contracts clean, and make sure the frontend (or clients) can use it safely without fragile workarounds. The existing website can stay as it is. I'd keep the new work separate where it makes sense, test the flows properly, then deploy once everything is working. If you send over the code and tell me which sections/data you want manageable from the dashboard, I can have a look and get started. Best regards, Salah


Hello, I’d be glad to help with this AWS platform build and GCP-to-AWS migration. I work a lot with AWS DevOps, Terraform, PostgreSQL, and platform architecture, and I’m comfortable designing secure, auditable environments for regulated SaaS products like yours. I recently completed a similar migration where I moved a Python/FastAPI backend with PostgreSQL from Google Cloud to AWS, rebuilt the CI/CD in Bitbucket Pipelines, and introduced trunk-based delivery with preview environments and automated rollback. I also designed the AWS landing zone, ECS Fargate platform, RDS PostgreSQL, Redis, CloudFront, WAF, and private networking, while keeping downtime to a minimum during cutover. In another recent project, I helped modernise release workflows and set up secure OIDC-based deployments with Terraform-managed infrastructure. Your requirements around ISO controls, least privilege, logging, and evidence for change management are very familiar to me. I’d be happy to work under your NDA/DPA and only through company-managed access. A couple of questions: 1. Do you already have a preferred AWS account structure, or would you like me to propose one? 2. Should the Bitbucket migration preserve all current branch protections and PR rules exactly as-is? If helpful, I can jump on a call to discuss the safest migration approach. Best regards, Mehreen


Hi, You're moving a live EdTech platform from GCP to AWS while keeping ISO 27001, 42001 and 9001 controls intact. The main risk I would design around is a failed Postgres cutover, because school data and PII mean downtime or loss is not acceptable. I would build the AWS foundation and platform in Terraform first, then migrate Postgres with logical replication to eu-west-2, keeping GCP as a rollback path until you approve cutover. I'd choose ECS Fargate over Lambda for FastAPI and pseudonymisation services because long-running containers are easier to right-size within the same VPC and private endpoints. CI/CD would use Bitbucket Pipelines with OIDC into AWS, build once per merge to main, promote the same artifact to staging, then one-click to prod with automated rollback. I'd verify the migration with a rehearsed cutover and rollback drill before touching production. Q1: What is your current production database size and approximate traffic peak? Q2: Do the three repos include Terraform, and do you want that moved to Bitbucket with history?
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗