Al Watania For Industries infrastructure contained a dedicated VPC on AWS Cloud
- A Multi AZ approach is utilized for HA
- Private subnets are provisioned to isolate workloads.
- CloudTrail is deployed to record events occurring on AWS account
- AWS Managed Backup is configured to ensure business continuity
- A Client-to-Site VPN as well a Next Gen Firewall is configured for Secure Access
- CloudWatch is configured to monitor the servers
- Alarms are configured to trigger SNS email topics
- AWS AD connector is used for extending the directory service to the cloud
- IAM roles have been configured for teams, departments, and individuals.
- AWS Marketplace Solution has been configured for security as well the S3 bucket for backup.
Step 1: Meeting with Stakeholders
Citrus scheduled a readiness assessment meeting with key stakeholders including the Security Team, Network Team, Infra Lead, Application Lead, Operation Lead, and Business Unit Head to discuss the goals for migrating applications to AWS. The team discussed short-term and long-term objectives, risks, and issues related to IT and business application migrations.
Step 2: Analysis of Results
After cross-presentation with the customer, the Citrus team analyzed the results and built an out-brief pitch that contained summary observations and next steps to fill the identified gaps. This was required to build a statement of work for closing the identified gaps and completing the suggested next plan of action.
Step 3: Review of Current AWS Footprint
Citrus reviewed the client’s current AWS footprint, applications, operational processes, and integration. The team had discussions on various topics related to the migration process, including business, governance, people, platform, operations, and security.
The assessment also involved resource discovery for collecting and analyzing the data in the client’s IT environment. As part of our data gathering process, we obtained information pertaining to the on-premise server, including but not limited to its machine type, operating system, currently running applications, memory capacity, CPU utilization, and storage allocation.
Step 4: Migration Process
Citrus presented the customer with a high-level AWS migration plan that included project preparation, project governance, project kick-off, landscape setup, server deployment, AWS readiness, sandbox environment on AWS, and setting up development/production environments. Re-hosting candidates (APP Servers) were migrated using AWSCloudEndure, while Re-Platform was done for the Hana DB servers using Backup and Restore.
To ensure a smooth migration, Citrus executed a mock data transfer by moving data backup file from on-premises to AWS Cloud. This allowed the team to estimate the time required for data transfer. A sandbox system was created as a pilot environment, and a mock migration was undertaken before the real production migration. Data points acquired from the pilot, such as data transfer issues, restoration challenges, time length, and data corruption challenges, were used to plan for the final production switch over.