Project objective
Address slow analytics, weak perimeter security, limited MFA, legacy databases, and cloud compatibility problems without disrupting necessary on-premises operations.
What I produced
- Assessed hardware and software vulnerabilities in the existing environment.
- Proposed AWS Systems Manager for unified operations, EMR for analytics, Aurora for database scaling, and EKS for containerized ETL workflows.
- Recommended next-generation firewall and VPN upgrades with modern authentication.
- Created a five-step transition plan covering requirements, assessment, architecture, phased migration, testing, optimization, and security.
Key decisions
- Keep workloads on-premises when operational or compatibility needs require it.
- Move compute-intensive analytics and scalable data processing to AWS.
- Migrate in phases and validate performance, security, identity, and replication before proceeding.
- Treat monitoring, patching, IAM, and configuration management as ongoing operations.
5 phasesRequirements through ongoing optimization
4 AWS servicesManagement, analytics, containers, and database
Phased migrationTesting before each expansion
Validation and analysis
- Mapped each modernization step to a documented problem in the current environment.
- Defined why each workload belongs on-premises or in AWS.
- Included testing and optimization checkpoints in the migration sequence.