Increasing reliability with an accelerated migration to AWS
After a 2-day downtime event in its on-premises environment, Metabolic Maintenance decided to migrate to AWS to improve reliability and adopt best practices. However, the company had no in-house AWS expert and did not want to hire a full-time resource. Initially, this left hiring a consultant as their only option, with SOWs ranging from $60k-90k and an estimated migration timeline of 3-4 months. The company also did not have the expertise to manage and monitor its service post-migration.
Metabolic hired one of the consultants but used Platformr to configure its AWS Organization to reduce costs and shrink the migration scope to 4 weeks.
Company Profile
- B2C ecommerce website
- Professional Nutritional Products and Practitioner Supplements
Goals
✔ Migrate to AWS
✔ Increase reliability
✔ Improve security posture
✔ Streamline development process
✔ Manage and monitor cloud health
Solution
Platformr Foundation:
- Set up an AWS Landing Zone to include AWS Control Tower, service control policies (SCPs), AWS Organizational Units, centralized logging, and centralized security with AWS Security Hub
- Implemented central networking solution (hub-spoke model) to allow for an on-prem to cloud connection with AWS Transit Gateway, AWS Route tables, VPC endpoints and a client VPN connection
- Improved security posture and made it easier to manage AWS users and contractors by incorporating AWS Identity Center and AWS IAM user management
- Eliminated security vulnerabilities by enforcing centralized root user management and deleting out root user credentials
- For Infrastructure as Code (IaC), followed the principles of a Security Reference Architecture (SRA) to establish secure boundaries and delegate responsibilities
- Isolated AWS account workloads as a best practice for enhancing security and operational efficiency in cloud environments (grouping AWS resources and workloads into separate AWS accounts based on their functionality and security requirements)
- Deployed budgets at the AWS Organization, workload, and account level with alerts
- Deployed AWS supported Well-Architected lenses
- Leveraged AWS Cost Explorer to gather data and visualize AWS costs and usage over time for increased visibility and improved cost management
- Set up tags for cost reporting
- Set up backup and availability based on business requirements
Workload Factory:
- Set up a secure connection with a VPN
- Created separate development environments (Development, Testing, Staging, Production)
- Established a Disaster Recovery environment to meet customer requirements
Observability:
- Set up alarms to notify company on health metrics using Amazon CloudWatch, Amazon EventBridge, and Amazon Simple Notification Service (SNSs
Results
✔ Saved $25k in professional services fees
✔ Reduced migration timeline from 4 months to 4 weeks
✔ Saved $2500/month by replacing a support team to manage and monitor the environment
AWS Services
- AWS Control Tower
- AWS Backup
- AWS Transit Gateway
- Amazon AppStream 2.0
- AWS IAM Identity Center
- AWS Config
- AWS Security Hub
- AWS CloudTrail
- AWS Key Management Service (KMS)
- AWS DataSync
- Amazon Detective
- Amazon GuardDuty
- Amazon Inspector
- Amazon Macie
- AWS Resource Access Manager
- AWS Well-Architected Tool
- AWS Budgets
- AWS Cost Explorer
- Amazon Route 53
- AWS WAF (Web Application Firewall)
- Amazon VPC
- AWS VPN
- Amazon CloudWatch
- Amazon EventBridge
- Amazon Simple Notification Service (SNS)