Design and Develop AWS Cloud Infrastructure for Video & Ad-Tech Platform Migration

Technical Requirements Brief AWS Cloud Infrastructure — Video & Ad-Tech Platform Migration LCM Go Cloud | Confidential | August 2026 1. Overview LCM Go Cloud (an AWS Advanced Tier Services Partner based in Athens, Greece) is seeking an experienced AWS infrastructure specialist to execute the technical delivery of a cloud migration and environment build-out project. The specialist will work under the direction of LCM's Project Manager and will have no direct commercial relationship with the end customer. This document describes the project context, technical scope, required skills, deliverables, and working arrangements. 2. Project Context The customer operates a multi-tenant SaaS platform for video distribution and first-party ad serving, currently running on a single non-AWS Linux host. The platform is built as a PHP 8.1 monolith (no framework) with MySQL 8.0, comprising approximately 212K lines of code, 193 database tables, 118 API endpoints, and 38 scheduled cron jobs. The platform is pre-production — it has not yet served live traffic on AWS. LCM has already delivered a separate Phase 1 project for a related application (Node.js + MongoDB), which is live in production on AWS (eu-central-1, Frankfurt) with a fully operational Multi-AZ, HA environment including ALB, WAF, CloudFront, CI/CD (CodePipeline/CodeDeploy or GitLab CI), and CloudWatch monitoring. The Phase 1 infrastructure is built entirely in AWS CDK (TypeScript). Phase 2 (this project) builds a new, separate AWS environment for the PHP/MySQL platform alongside the existing Phase 1 environment, validates it, launches it into production, and eventually retires the Phase 1 environment once the new platform has absorbed its role. 3. Scope of Work The engagement consists of two sequential phases, both under LCM's Project Manager direction. 3.1. Architecture Advisory (Phase A) Working alongside LCM's Project Manager (who will actively participate in this phase), produce a Target Architecture & Migration Roadmap document that resolves the following open design questions: Compute shape: ECS/Fargate vs. EC2 + Auto Scaling Group Hot-path isolation for the ad-serving endpoint (latency-critical, targeting 1000+ req/sec) Media migration to S3 + CloudFront + MediaConvert WAF scoping: which paths get full inspection vs. lighter treatment White-label CDN/domain/certificate design (multiple publisher brands from day one) Event-data placement for the high-volume ad-event table (RDS/Aurora vs. streaming pipeline) Caching & session strategy (ElastiCache Redis for sessions + ad frequency-capping) Job orchestration with single-execution guarantees (38 cron jobs, no global locking today) Database resilience & failover design (revenue-critical ad server) Launch approach: staged rollout vs. full launch Secrets protection (currently .htaccess-dependent — must be re-verified) Region & data residency confirmation (GDPR, eu-central-1) The advisory phase also includes producing an app request-efficiency recommendations memo — guidance for the customer's dev team on reducing CloudFront/WAF request volume through application-side changes (HLS segment duration, rendition-ladder trimming, cache-control headers, push vs. polling). This requires reading and reasoning about the existing PHP codebase at a pattern level, not rewriting it. 3.2. Setup & Test (Phase B) Based on the architecture confirmed in Phase A, build and validate the AWS environment: Environment build-out: provision the full AWS environment using CDK (TypeScript), consistent with the Phase 1 IaC approach — including VPC, subnets, compute, RDS/Aurora, ElastiCache, S3, MediaConvert, CloudFront, WAF, NAT Gateways, IAM, Secrets Manager, KMS, and CloudWatch. CI/CD pipeline: CodePipeline / CodeDeploy or GitLab CI/CD, covering build, environment promotion, and deployment mechanics. The customer's dev team owns the application build/test steps inside the pipeline. Resilience & validation testing: chaos-engineering methodology (LCM has a proven framework from Phase 1) — documented pass/fail per scenario, explicit latency SLOs for the ad-serving endpoint, failover-time targets for the database layer, and formal acceptance criteria sign-off before go-live. Fix/retest buffer: remediate issues found during testing and re-validate. 3.3. Deliverables Target Architecture & Migration Roadmap document (Phase A) App request-efficiency recommendations memo (Phase A) Provisioned, working AWS environment + CI/CD pipeline (Phase B) Signed-off resilience test report + acceptance criteria (Phase B) 4. Out of Scope Application development — the customer's team writes and maintains the PHP code Application-level security or tenancy logic validation Application bug support or debugging Direct communication with the end customer (all coordination goes through LCM's PM) Commercial, pricing, or contractual discussions 5. Technical Environment AWS region: eu-central-1 (Frankfurt) IaC: AWS CDK, TypeScript (mandatory — must be consistent with the existing Phase 1 codebase) Application stack: PHP 8.1 (no framework, no autoloader), MySQL 8.0, Apache Existing Phase 1 environment: Node.js + MongoDB on EC2, Multi-AZ, ALB, WAF, CloudFront, CodePipeline/CodeDeploy or GitLab CI, CloudWatch — all CDK-managed Key AWS services in scope: EC2 or ECS/Fargate, RDS or Aurora (MySQL), ElastiCache (Redis), S3, CloudFront, WAF, MediaConvert, CodePipeline, CodeDeploy, CloudWatch, IAM, Secrets Manager, KMS, VPC, NAT Gateway, ALB 6. Required Skills & Experience 6.1. Mandatory Strong hands-on experience with AWS infrastructure design and build (3+ years) Proficiency in AWS CDK with TypeScript Experience with Multi-AZ, high-availability architectures on AWS Working knowledge of CloudFront, WAF, ALB, and CDN architecture Experience with RDS or Aurora (MySQL) in production, including Multi-AZ failover CI/CD pipeline design and implementation (CodePipeline/CodeDeploy or GitLab CI/CD) Infrastructure monitoring and alerting (CloudWatch) English fluency (all communication is in English) 6.2. Strongly Preferred AWS Solutions Architect certification (Associate or Professional) Experience with ElastiCache (Redis) for session management and/or rate-limiting patterns Experience with MediaConvert or similar video-transcoding pipelines Familiarity with PHP application deployment patterns (not development — ability to read PHP code and reason about request patterns, caching behavior, and infrastructure implications) Experience with chaos-engineering / resilience-testing methodologies Experience with ad-tech or high-request-volume web platforms 6.3. Nice to Have Experience with ECS/Fargate containerized deployments Familiarity with event-streaming architectures (Kinesis, Firehose) Knowledge of GDPR data-residency requirements in AWS 7. Working Arrangements Reporting: directly to LCM's Project Manager (based in Athens, EET/EEST timezone). Daily async updates; syncs scheduled as needed. Customer interaction: none directly. All communication with the end customer is handled by LCM's PM. The specialist may occasionally join technical calls with the customer's dev team, introduced as part of the LCM team. Identity: the specialist works under LCM's identity throughout the engagement. Access: AWS console/CLI access via a dedicated IAM user provisioned by LCM (not shared credentials). Access to the existing CDK codebase (Git). NDA required before access is granted. Tools: Git (GitLab), AWS Console/CLI, CDK, standard communication tools (to be agreed). 8. Indicative Timeline Target availability: early September 2026. Phase A (Architecture Advisory): 2–3 weeks, working alongside LCM's PM Phase B (Setup & Test): 4–6 weeks (includes build, testing, and fix/retest) Total project duration: approximately 8–10 weeks Phases are sequential — Phase B starts only after Phase A's deliverable is signed off. 9. Ongoing Operational Support (Optional) Following project completion, LCM provides ongoing managed operations to the end customer. If the selected specialist is interested and capable, there may be an opportunity to continue in a part-time operational support role (monitoring, incident response, maintenance) after go-live. This is not a prerequisite for the project engagement — it will be discussed separately if mutually of interest. 10. How to Respond Please provide: A brief summary of relevant AWS project experience (2–3 examples) Confirmation of CDK/TypeScript proficiency Any relevant AWS certifications Availability from early September 2026 Your rate or fee proposal for the project scope described above Whether you would also be interested in ongoing operational support post-project