Cloud Migration Services

1. Retire

   This involves taking steps to identify everything in your company that has the potential to be migrated to the cloud. At that point, you can also evaluate the value that each application or other asset brings with it. This helps you learn more about what you should keep and, more importantly, what you shouldn't.
2. Rehost

   Rehosting is a popular migration strategy also known as “lift and shift.” It is a quick solution for migrating to the cloud and moves applications, software, and data to cloud with little effort. Rehosting is popular for initial migrations because it involves moving existing physical and virtual servers into an IaaS solution. The IaaS model hosts the infrastructure that is typically found on sites, such as the servers, storage, and networking hardware and offers a virtualized environment through a hypervisor layer. Rehosting may lead your company to re-architecting in the future, once a cloud-based operation is in place.
3. Replatform

   Some legacy applications will be far too complicated for a straight migration. At that point, they may be good candidates for replatforming - meaning instead of changing the core of those applications, they are emulated through a virtual machine. Replatforming, though sometimes costly, is a far better option for your company if you cannot restructure the IT legacy systems at the time of cloud migration.
4. Repurchase

   Repurchasing, when possible is an excellent and fast way to access cloud-based SaaS that is tailored to your business needs by the cloud provider. This would take all of your organization's existing data and applications and transition them into a cloud-based product if such an alternative is available from the original developer.
5. Refactor & Rearchitect

   Refactoring/re-architecting often boosts agility, business continuity, and overall productivity and collaboration. This is typically driven by your company's need to be as scalable as possible. You're essentially taking the application that you already know and are rebuilding it from the ground up for a cloud-based environment, doing so in a way that boosts productivity and collaboration at the same time. However, this strategy tends to be the most expensive and is usually executed after an initial migration via one of the other approaches, like rehosting.
6. Retain

   Some parts of your environment may not migrate and are retained as-is. There are many reasons to maintain an in-house asset, such as riding out the depreciation value or the cost of migration is too high, and your company can maintain more value using the application or service in-house. Depending on the volume of these assets, it may highlight the value of a hybrid cloud environment.

Infrastructure as Code (also known as IaC) is a type of configuration that automates the managing and provisioning of the infrastructure through code - without going through manual processes. All cloud orchestration - provisioning, deployment, configuration, migration, and the related changes will all be handled centrally and uniformly across your dev/qa/uat/prod environments using code managed in a version-control repository like GitHub, CodeCommit or Azure DevOps

Our certified local cloud engineers have decades of combined experience in developing with the following IAC tools and technologies

• Terraform
• AWS CDK
• AWS Cloudformation
• Azure ARM Templates
• Pulumi
• Ansible (Configuration As Code)
• Chef/Puppet (Configuration As Code)

In addition to the above, we also use specialized tools aimed at specific infrastructure and configuration management tasks such as:

• Packer, EC2 Image Builder, and Azure Image Builder to create deployable custom os images.
• Cloud-Init (industry-standard cross-platform cloud instance initialization tool) to execute scripts when provisioning resources (servers)

1. Standards for the design of infrastructure
2. Monitoring of infrastructure and application
3. Security Policy
4. Programming standards
5. Backup recovery services
6. Security & Incident management

Business continuity is basically the planning and preparation your company should take in order to ensure that you remain operational during a disaster. A comprehensive cloud disaster recovery plan will be developed to ensure that systems and applications keep running even if, there’s a breach or in cases of natural disaster. The plan will consider a specific Recovery Point Objective (ideally 24 hours) and a Recovery Time Objective (in minutes).

Our Disaster recovery strategies can be broadly categorized into four approaches, ranging from the low cost and low complexity of making backups to more complex strategies using multiple active Regions.

For instance, below are the suite of strategies that we use to implement DR within AWS cloud. Active/passive strategies use an active site (such as an AWS Region) to host the workload and serve traffic. The passive site (such as a different AWS Region) is used for recovery. The passive site does not actively serve traffic until a failover event is triggered.