{"id":24555,"date":"2025-05-14T12:06:11","date_gmt":"2025-05-14T12:06:11","guid":{"rendered":"https:\/\/northbaysolutions.com\/case-studies\/data-center-migration-from-on-premises-to-aws-cloud-for-ibl-ltd\/"},"modified":"2025-10-22T10:12:52","modified_gmt":"2025-10-22T10:12:52","slug":"data-center-migration-from-on-premises-to-aws-cloud-for-ibl-ltd","status":"publish","type":"post","link":"https:\/\/northbaysolutions.com\/case-studies\/data-center-migration-from-on-premises-to-aws-cloud-for-ibl-ltd\/","title":{"rendered":"Data center migration from on-premises to AWS Cloud for IBL Ltd"},"content":{"rendered":"

\"Data<\/span><\/div><\/div><\/div><\/div><\/div>

Meet Our Customer<\/strong><\/p>\n<\/div>

IBL Mauritius<\/a> is a diversified conglomerate based in Mauritius, boasting a rich history of over 190 years. The group operates across nine business clusters, encompassing more than 280 brands in sectors such as agro-industry, building and engineering, commercial, financial services, hospitality, life sciences, logistics, manufacturing and processing, and property. Its agro operations offer sugar cane growing, milling and refining in Mauritius and the East African region. With a presence in 22 countries worldwide, IBL employs approximately 37,950 team members, making it one of Mauritius' largest employers. The group's strategic objective is to be recognized as a leading international entity, anchored in a robust investment portfolio, a culture of excellence, and world-class expertise.<\/p>\n<\/div><\/div><\/div>

The Challenge<\/strong><\/p>\n<\/div>

When IBL engaged NorthBay Solutions, it was for a very specific reason: they were seeking an experienced partner to guide them on their data center migration<\/a> from on-premises to AWS Cloud. Few of their challenges were addressed during this migration.<\/p>\n

    \n
  1. Transferring large volumes of data from on-premises systems to AWS while ensuring data integrity and minimal downtime.<\/li>\n
  2. Ensuring consistent user access across environments.<\/li>\n
  3. Implementing and managing multi-factor authentication (MFA) for user authentication.<\/li>\n
  4. Configuring a DR site in a different AWS account for ensuring seamless failover processes.<\/li>\n
  5. Ensuring that multi-account setups and the use of AWS Control Tower align with best practices and prevent mismanagement.<\/li>\n
  6. Maintaining centralized logging, auditing, and compliance reporting across multiple AWS accounts.<\/li>\n<\/ol>\n<\/div>

    The Implication<\/strong><\/p>\n<\/div>

    Transitioning to the new environment brings several operational and strategic considerations. The following key implications were taken into account:<\/p>\n

      \n
    1. Increased administrative tasks during the migration phase, including account setup, backup configurations, and user access management.<\/li>\n
    2. Potential for service disruption if the migration and cutover are not carefully planned.<\/li>\n
    3. Higher initial costs due to resource provisioning and data transfer fees.<\/li>\n
    4. Staff need to familiarize themselves with AWS services<\/a>, such as Elastic Disaster Recovery, FSx<\/li>\n
    5. Dependence on AWS's uptime and support infrastructure for critical business operations.<\/li>\n<\/ol>\n<\/div>

      Solution<\/strong><\/p>\n<\/div>

      Following are the highlights of the solution provided to IBL which were based upon AWS best practices of architecture design, high availability, security and performance.<\/p>\n

        \n
      1. Used AWS Organizations and Control Tower for account provisioning and centralized governance.<\/li>\n
      2. Implemented identity and access management.<\/li>\n
      3. Configured MFA on accounts to enhance security.<\/li>\n
      4. Utilized AWS DataSync and Elastic Disaster Recovery to facilitate seamless data and application migration.<\/li>\n
      5. Configured Site to Site VPN between on premises to Production Site and DR Site.<\/li>\n
      6. Deployed DR systems using EDR for EC2, DataSync for FSX and also S3 bucket synchronization to ensure availability during disaster.<\/li>\n
      7. Implemented centralized logging and security tools like AWS Security Hub, GuardDuty, and CloudTrail.<\/li>\n<\/ol>\n<\/div>

        AWS Services<\/strong><\/p>\n<\/div>

        The project heavily utilized AWS services<\/a> to ensure scalability and efficiency:<\/p>\n<\/div>

        AWS Control Tower<\/a>, Amazon VPC<\/a>, Amazon EC2<\/a>, Amazon S3<\/a>, Amazon FSx<\/a>, AWS Elastic Disaster Recovery<\/a>, AWS MGN<\/a>, AWS DataSync<\/a>, Amazon EBS<\/a>\n<\/div>
          <\/ul>\n\n