<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mohammed Munem on Medium]]></title>
        <description><![CDATA[Stories by Mohammed Munem on Medium]]></description>
        <link>https://medium.com/@mmunem?source=rss-aad14c7ee6f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DQWjRA9VXo1ytxXr.</url>
            <title>Stories by Mohammed Munem on Medium</title>
            <link>https://medium.com/@mmunem?source=rss-aad14c7ee6f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:16:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mmunem/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Experiences of Rehosting on-prem Customer Workloads Using AWS Application Migration Service (AWS…]]></title>
            <link>https://medium.com/@mmunem/experiences-of-rehosting-on-prem-customer-workloads-using-aws-application-migration-service-aws-a824805a927c?source=rss-aad14c7ee6f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a824805a927c</guid>
            <category><![CDATA[aws-migration]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[lift-and-shift]]></category>
            <dc:creator><![CDATA[Mohammed Munem]]></dc:creator>
            <pubDate>Wed, 09 Nov 2022 19:44:41 GMT</pubDate>
            <atom:updated>2022-11-09T19:50:51.080Z</atom:updated>
            <content:encoded><![CDATA[<h3>Experiences of Rehosting on-prem Customer Workloads Using AWS Application Migration Service (AWS MGN)</h3><h3>Customer Scenario*</h3><p>Cyberdyne Systems, is a global robotics retailer with operations in 40 countries. Following a number of high-profile outages in 2020, the CIO and board decided to pursue a cloud-first strategy and to migrate existing workloads to AWS cloud. As of now, notice has been tendered to ten co-lo datacentres with an anticipated end date of December 31st, 2022.</p><p>Cyberdyne Systems enlisted the help of AWS Partner, Daemon to migrate its key business applications to AWS cloud using the framework of AWS’s Migration Application Programme (MAP) which includes three key phases:</p><ol><li>Assess</li><li>Mobilize</li><li>Migrate &amp; Modernize</li></ol><p>The focus of this article is on the Application migration workstream of the Mobilize phase highlighted below, wherein migration teams build a foundation for successful migrations by migrating a small set of business applications to the cloud.</p><p>*<em>Fictional company names are used where permission for a public case study could not be obtained</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/0*enjwYNzbXhdZDzY6.png" /></figure><p>Figure 1: Phase 2 (Mobilize) highlighted in a customer’s migration journey</p><h3>Applications Identified for Rehosting (Lift and Shift) during Mobilize</h3><p>The Cyberdyne Systems migration team have identified the following six applications for migration using the <em>Rehosting</em> or Lift and Shift method:</p><ul><li>MyHR HRIS System: bespoke HRIS system developed in-house</li><li>PraiseYou: bespoke employee appraisal platform</li><li>TechDocs: internal WIKI (based on MediaWiki) for technical documentation</li><li>GitLab: self-hosted GitLab VCS for SWE teams</li><li>cyberdynesystems.io website: uses WordPress</li><li>Event Planner: custom event planning application built using FileMaker Pro</li></ul><h3>AWS Application Migration Service (MGN)</h3><p>Some of the applications identified above including GitLab use a database backend such as PostgreSQL. While this is a great opportunity to consider <em>Replatforming</em> these to a service such as Amazon RDS for PostreSQL, there is no current appetite for this. Instead all servers and their backend databases will be migrated using the MGN service as illustrated below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sqfDdaxnwl-iv6aJ.png" /></figure><p>Figure 2: MGN is the recommended tool for Lift and Shift migrations</p><p><a href="https://aws.amazon.com/blogs/architecture/accelerating-your-migration-to-aws/">https://aws.amazon.com/blogs/architecture/accelerating-your-migration-to-aws/</a></p><p>At a high-level, MGN uses block-level continuous replication to migrate all data held on on-premises servers to replication volumes attached to <em>Replication</em> instances in a Staging Area in AWS. Once the source and destination volumes are fully synchronised, a cutover process is invoked which results in an appropriate-sized EC2 instance being launched with the replication volume data. This is further illustrated below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Al-pmEphtWJIdmZw.png" /></figure><p>Figure 3: MGN Service and Network Architecture</p><p><a href="https://docs.aws.amazon.com/mgn/latest/ug/Network-Settings-Video.html">Service architecture and network architecture overview — Application Migration Service</a></p><h3>Migration Steps using MGN</h3><ol><li>AWS Replication Agent installed on source on-prem server</li><li>Source servers added to the Application Migration Service console</li><li>Replication commences</li><li>When replication completes, launch a test instance and SSH or RDP to the instance to carry out functional tests, including connectivity and acceptance tests.</li><li>Once satisfied with the test instance, mark as ‘Ready for cutover’</li><li>Launch the cutover instance and finalise cutover upon successful launch</li></ol><p>This is illustrated below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SI_loQ1Bv5eEhZm_.png" /></figure><p>Figure 4:<a href="https://aws.amazon.com/application-migration-service/"> https://aws.amazon.com/application-migration-service/</a></p><h3>Operating System Considerations</h3><p>While attempting to install the AWS Migration Agent on the PraiseYou server, the migration team realised that Windows 2003 is no longer supported. This can be common with large scale migrations to cloud where a lot of legacy applications are hosted on non-supported operating systems. A current list of supported operations systems can be found here:<a href="https://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html"> Supported operating systems — Application Migration Service</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*PeQij6XAtn69DEcD.png" /></figure><p>Figure 5: Windows 2003 and other legacy operating systems are not supported</p><h3>Networking Considerations</h3><h4>Replication traffic to AWS</h4><p>MGN uses TCP port 1500 to replicate the blocks from the source server via the AWS Replication Agent to AWS. The on-premises Network/Security teams must ensure that appropriate firewall ACLs are created to allow replication traffic to reach the AWS replication servers.</p><h4>Prepare Subnets and Security Groups for Launch</h4><p>Test and Cutover instance subnets must be defined to ensure successful launches. Furthermore, security groups should also be created and available for inclusion in the EC2 Launch template to ensure that the launch succeeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*x7TD5E6vJ9SgBwVU.png" /></figure><p>Figure 6: Security Group rules need to be defined to ensure the continued secure operation of migrated workloads</p><p>Source:<a href="https://aws.amazon.com/blogs/aws/new-descriptions-for-security-group-rules/"> https://aws.amazon.com/blogs/aws/new-descriptions-for-security-group-rules/</a></p><p>It is the customer’s responsibility to identify the exact security group rules that need to be defined. AWS does not provide tooling for firewall rules/security group rules discovery.</p><p>Cyberdyne Systems’ migration team had to spend an additional two weeks to gain a definitive understanding of the least privileges security group rules required for MyHR and PraiseYou applications. Unfortunately, these legacy applications were not maintained well and had missing documentation, especially around security. Daemon assisted Cyberdyne Systems in the security group discovery exercise by analysing VPC Flow Logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*L79vVkNXP9vyLZPD.png" /></figure><p>Figure 7: Analysing VPC flow logs by ingesting them to the OpenSearch service and displaying using Kibana.</p><h3>Closing Thoughts</h3><p>In an ideal world, rehosting or lift and shift would not be used as a cloud migration approach as it does not leverage the agility and elasticity of cloud services and can often be more expensive than hosting on-premises. However, as Daemon consultants, we are especially pragmatic with our customers and understand the <em>Bigger Picture</em> and the motivations and constraints that drive their decisions. To this end, we look for the best processes and technologies to help them migrate the workloads to cloud.</p><p>However, all migrations require wider buy-in from diverse customer teams and as I’ve highlighted above, failure to consider things such as support for operating systems and network requirements may unnecessarily stall or delay a migration.</p><h3>Further Reading</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fsheetsu.com%2Ftables%2F6b653f09b5&amp;dntp=1&amp;display_name=Sheetsu&amp;url=https%3A%2F%2Fsheetsu.com%2Ftables%2F6b653f09b5&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=sheetsu" width="700" height="297" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2d2e31370bdad9dc4a1114d4811e278/href">https://medium.com/media/d2d2e31370bdad9dc4a1114d4811e278/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a824805a927c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Secure Landing Zone for your Cloud Workloads: AWS Control Tower and the problems it solves.]]></title>
            <link>https://medium.com/daemon-engineering/a-secure-landing-zone-for-your-cloud-workloads-aws-control-tower-and-the-problems-it-solves-4fc893ccd0e3?source=rss-aad14c7ee6f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fc893ccd0e3</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws-control-tower]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-landing-zone]]></category>
            <dc:creator><![CDATA[Mohammed Munem]]></dc:creator>
            <pubDate>Mon, 07 Nov 2022 14:47:15 GMT</pubDate>
            <atom:updated>2022-11-08T07:56:41.367Z</atom:updated>
            <content:encoded><![CDATA[<p>This article describes the requirements and complexities of implementing a secure landing zone in AWS cloud. Its purpose is to prove the value of the AWS Control Tower service and demonstrate the head-start it provides to your cloud team while addressing the extensibility required for the majority of implementations.</p><p>I spent 3.5 years at AWS Professional Services with the majority of my time spent on customer projects with a landing zone requirement. These were for both greenfield, enabling mass migrations from on-premises and also where customers’ had an existing footprint which saw unmanaged account sprawl.</p><h3><strong>Micro-segmentation</strong></h3><p>An enterprise may have hundreds, if not thousands of applications. With cyber security being front and centre of all digital transformation programmes, more and more organisations are adopting a micro-segmentation strategy to reduce the blast radius and damage caused by a cyber security incident. The UK government’s National Cyber Security Centre (NCSC) describes micro-segmentation as “… <a href="https://www.ncsc.gov.uk/blog-post/virtualisation-security-design-principles">a technique whereby the workload of a system is divided into segments, based on security needs. Necessary controls are then applied on a per-segment basis.</a>”</p><p>Customers often use multiple accounts to isolate their resources because they provide natural boundaries for security, access, and billing. Applying a micro-segmentation approach to AWS workloads entails confining applications to dedicated AWS accounts (AKA segments) with a highly controlled least-privileges approach to connectivity between this dedicated account and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j7qvR6BtxRfx1wcR.png" /><figcaption>Source: <a href="https://aws.amazon.com/blogs/industries/defining-an-aws-multi-account-strategy-for-telecommunications-companies/">https://aws.amazon.com/blogs/industries/defining-an-aws-multi-account-strategy-for-telecommunications-companies/</a></figcaption></figure><h3>Managing Multiple AWS Accounts</h3><p>Whereas managing a single account is trivial, ensuring a solid infrastructure and security baseline across multiple accounts is much more involved. Here are some of the fundamental questions that need answering in order to build out a landing zone.</p><ul><li>‘Vending’ accounts: what mechanism will you adopt to create AWS accounts for use by application teams?</li><li>SSO: how do you ensure proper authentication/authorization for AWS console and API access, preferably using a customer’s existing Identity Provider (IdP) such as Active Directory or Azure AD?</li><li>Guardrails: how do you ensure both detective and preventative guardrails are consistently applied across accounts?</li><li>Logs: how do you centralise logs from your sprawling accounts so that this can feed into your incident management process?</li><li>CI/CD: while the AWS Console is a great introduction to the AWS services, preparing accounts using the ClickOps approach is not scalable and will necessarily introduce risk as humans are in the loop. Instead, a GitOps approach to building cloud infrastructure is required. Together with a selected Infrastructure-as-Code (IaC) platform, a CI/CD workflow will automatically test, build and configure the infrastructure required by a new AWS account.</li><li>Change management: most enterprises implement ITIL tooling such as Service Now to manage their IT changes. When a development team requests AWS accounts for their application, this will go through a change management process which usually includes one or more approvals stages. The architecture below describes how JIRA Service Desk can be integrated with AWS via the Service Catalog service:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WxuJHsq1dBVA_-13.png" /><figcaption>Source: <a href="https://controltower.aws-management.tools/ops/itsm/jsd/">https://controltower.aws-management.tools/ops/itsm/jsd/</a></figcaption></figure><ul><li>Backups and DR: with the mantra of “everything fails all the time” at the forefront, how should these requirements be implemented across multiple accounts?</li></ul><h3><strong>AWS Organizations</strong></h3><p>Released in 2017, you can create a single AWS Organization and use policy-based management with Service Control Policies (SCPs) for multiple accounts. Using the AWS Organizations API, you can for example <a href="https://docs.aws.amazon.com/organizations/latest/APIReference/API_CreateAccount.html">CreateAccount</a>, <a href="https://docs.aws.amazon.com/organizations/latest/APIReference/API_CloseAccount.html">CloseAccount</a> and assign consistent metadata to accounts by using the <a href="https://docs.aws.amazon.com/organizations/latest/APIReference/API_TagResource.html">TagResource</a> API</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kzEXrS10pKFAE7fv.jpg" /><figcaption><a href="https://aws.amazon.com/blogs/industries/defining-an-aws-multi-account-strategy-for-telecommunications-companies/">https://aws.amazon.com/blogs/industries/defining-an-aws-multi-account-strategy-for-telecommunications-companies/</a></figcaption></figure><h3><strong>AWS Single Sign-On (AWS SSO)</strong></h3><p>Integrated with AWS Organizations, AWS SSO is a service that makes it easy to centrally manage SSO access to multiple AWS accounts and business applications. Its support for SAML 2.0 allows AWS SSO to integrate with your on-premises IdP such as Azure AD as illustrated below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/0*dbMd8SHgCT9X4Ikj.png" /><figcaption>Source: <a href="https://aws.plainenglish.io/aws-single-sign-on-sso-with-azure-active-directory-ad-ae67030f3b04">https://aws.plainenglish.io/aws-single-sign-on-sso-with-azure-active-directory-ad-ae67030f3b04</a></figcaption></figure><p>AWS SSO provides not only seamless AWS Console access but also command line/programmatic access through automatically generated code snippets containing sts-generated temporary access keys as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/0*nCAUzkEA1N1ALv8n.png" /><figcaption><a href="https://aws.amazon.com/blogs/security/aws-single-sign-on-now-enables-command-line-interface-access-for-aws-accounts-using-corporate-credentials/">https://aws.amazon.com/blogs/security/aws-single-sign-on-now-enables-command-line-interface-access-for-aws-accounts-using-corporate-credentials/</a></figcaption></figure><h3>Managing Logs for Multiple Accounts</h3><p>There are two types of logs that infrastructure in our accounts will generate and by default, the log destination is the local account.</p><ul><li>AWS CloudTrail logs: API access logs</li><li>CloudWatch: application and service logs.</li></ul><p>In order to centralise our CloudTrail and CloudWatch logs, we can consolidate them in a dedicated log archive account. If using AWS Organizations, we can consider <a href="https://docs.aws.amazon.com/awscloudtrail/latest/userguide/creating-trail-organization.html">creating an organization trail</a> to log data for all AWS accounts in your organization, kept in a separate account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/0*3pw9iS4DzZx55mOp.png" /><figcaption>Source: <a href="https://aws.amazon.com/blogs/mt/restrict-access-by-member-account-to-a-centralized-cloudtrail-logging-bucket/">https://aws.amazon.com/blogs/mt/restrict-access-by-member-account-to-a-centralized-cloudtrail-logging-bucket/</a></figcaption></figure><p>The log archive account’s S3 bucket will resemble the functionality of a WORM (Write Once, Read Many) drive in that while all accounts will log to this bucket, none will be able to modify/delete logs once written. The access to the log archive account will be strictly controlled and logged. Also, <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiFactorAuthenticationDelete.html">MFA delete</a> should be enabled to prevent the accidental deletion of log files.</p><h3>The Case for AWS Control Tower</h3><p>In the above, I looked at the typical requirements of a multi-account environment and suggested individual solutions, most of which may be automated using respective service APIs. For example, using the Organizations API, we can invoke the <a href="https://docs.aws.amazon.com/organizations/latest/APIReference/API_CreateAccount.html">CreateAccount</a> action. However, combining and consolidating these solutions to create a landing zone solution is no easy task.</p><p><strong>Customized Landing Zone Frameworks</strong></p><p>In the past, there have been solutions published by AWS including the <em>Customized Landing Zone Solution</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*3ksTfq2f1d9MU0kZIPo63Q.png" /><figcaption>AWS Landing Zone Implementation Guide: May 2019</figcaption></figure><p>While the above solution was easily integrated into a GitOps workflow, the sheer number of moving parts created a lot of overhead for customers. The author remembers one of his customers spending a number of days troubleshooting a failed pipeline.</p><p><strong>Enter AWS Control Tower</strong></p><p>The successor to the Customized Landing Zone Solution, AWS Control Tower, was generally available in June 2019. As a managed service, AWS Control Tower removes the management overhead of previous solutions and provides an automated landing zone that deploys best-practices blueprints within an hour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2y7rRri2yFShOr4e6xhAA.jpeg" /><figcaption>Source: <a href="https://www.slideshare.net/CloudHesive/aws-control-tower-250839050?from_action=save">https://www.slideshare.net/CloudHesive/aws-control-tower-250839050?from_action=save</a></figcaption></figure><p>Features include:</p><ul><li>Account Factory: powered by AWS Service Catalog, allows simple provisioning of new AWS accounts with pre-approved account configurations.</li><li>Guardrails:<br>- Preventive and Detective<br>- Mandatory and Optional</li></ul><p>The value of having ready-made guardrails cannot be understated. For example, creating a preventative Service Control Policy (SCP) involves careful application of IAM policy logic and extensive testing to ensure you haven’t inadvertently created holes that may be exploited.</p><ul><li>Dashboard: continuous visibility into your AWS environment including the ability to check your OUs and accounts against guardrail compliance.</li></ul><p><strong>But…</strong></p><p>Although AWS Control Tower does provide a great multi-account starter framework, out of the box it is not useful to the majority of organisations. Merely providing the facility to vend an AWS account is not enough. Accounts often require customisations around VPC CIDR/AZ allocation, custom IAM roles and guardrails. Also, AWS SSO cannot and does not automatically integrate with your IdP as part of the Control Tower deployment. This will need to be configured after the fact.</p><p>AWS recommend the <a href="https://docs.aws.amazon.com/controltower/latest/userguide/cfct-overview.html">Customizations Framework for Control Tower (CfCT)</a> which uses AWS Control Tower lifecycle events to trigger the deployment of customisations to a newly vended account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwxGVpwBnw7zA8fCdW3knQ.jpeg" /><figcaption>Source: <a href="https://www.slideshare.net/CloudHesive/aws-control-tower-250839050?from_action=save">https://www.slideshare.net/CloudHesive/aws-control-tower-250839050?from_action=save</a></figcaption></figure><p>However, CfCT uses AWS native IaC with CloudFormation and this doesn’t help customers who’ve adopted TerraForm IaC.</p><p><strong>Enter Terraform Account Factory (AFT)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qIC85m4-xICNZJQK.png" /><figcaption><a href="https://aws.amazon.com/blogs/aws/new-aws-control-tower-account-factory-for-terraform/">https://aws.amazon.com/blogs/aws/new-aws-control-tower-account-factory-for-terraform/</a></figcaption></figure><p>The AFT Terraform module uses a similar approach to CfCT and uses a GitOps model to trigger account customisations upon a commit. Customers often ask how they can utilise readily-available CloudFormation templates published by AWS, e.g <a href="https://github.com/awslabs">https://github.com/awslabs</a>. Thankfully, Terraform has the <a href="https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudformation_stack">aws_cloudformation_stack resource</a> which allows the launching of CloudFormation templates from within a Terraform one.</p><h3>Concluding remarks</h3><p>Account micro-segmentation is a common pattern to reduce the blast radius of the resources within an account being compromised. It is also a great cost management boundary as the alternative is insisting upon and enforcing tagging of resources in a multi-application/environment account. A multi-account framework helps you automate best practices across your AWS estate and ensures consistency from a configuration management perspective.</p><p>AWS Control Tower is a managed service which takes away the undifferentiated heavy lifting associated with creating your own landing zone. It provides in less than one hour, an account vending solution and a sensible set of guardrails along with basic AWS SSO integration. Lifecycle events allow further customisation using solutions such as Account Factory for Terraform.</p><p><strong>References:</strong></p><p><a href="https://docs.aws.amazon.com/controltower/latest/userguide/what-is-control-tower.html">https://docs.aws.amazon.com/controltower/latest/userguide/what-is-control-tower.html</a></p><p><a href="https://docs.aws.amazon.com/controltower/latest/userguide/taf-account-provisioning.html">https://docs.aws.amazon.com/controltower/latest/userguide/taf-account-provisioning.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fc893ccd0e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daemon-engineering/a-secure-landing-zone-for-your-cloud-workloads-aws-control-tower-and-the-problems-it-solves-4fc893ccd0e3">A Secure Landing Zone for your Cloud Workloads: AWS Control Tower and the problems it solves.</a> was originally published in <a href="https://medium.com/daemon-engineering">daemon-engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Understand the 7 Rs Strategies for Moving Applications to the Cloud]]></title>
            <link>https://medium.com/daemonthinking/how-to-understand-the-7-rs-strategies-for-moving-applications-to-the-cloud-81a5f9b7e527?source=rss-aad14c7ee6f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/81a5f9b7e527</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[application-modernization]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-migration-strategy]]></category>
            <dc:creator><![CDATA[Mohammed Munem]]></dc:creator>
            <pubDate>Fri, 15 Jul 2022 09:19:39 GMT</pubDate>
            <atom:updated>2022-08-11T16:17:50.392Z</atom:updated>
            <content:encoded><![CDATA[<p>Businesses of all sizes are undergoing some form of digital transformation to continue serving their customers and remain relevant, especially in commoditised markets. And “<a href="https://www.gartner.com/en/newsroom/press-releases/2021-11-10-gartner-says-cloud-will-be-the-centerpiece-of-new-digital-experiences">There is no business strategy without a cloud strategy</a>” as observed by Milind Govekar, distinguished vice president at Gartner.</p><p>In our always-on era, you will experience customers churn to your digitally agile competition as a result of poor user experiences often caused by legacy technology stacks. The author recalls working with a customer on a strategic <em>change-the-bank programme</em> whose unpublished goal was to prevent churn to digital native challenger banks that were “born in the cloud”.</p><p>Inspired by the storytelling of <a href="https://www.google.co.uk/books/edition/The_Phoenix_Project/H6x-DwAAQBAJ">The Phoenix Project</a>, which in turn was inspired by Eli Goldratt’s <a href="https://www.google.co.uk/books/edition/_/HyxLDQAAQBAJ">The Goal</a>, I present the 7 <em>Rs</em> strategies for cloud migrations as enunciated in the <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/migration-strategies.html">Guide for AWS large migrations</a> by AWS.</p><h3>Background</h3><p>Sirius Cybernetics Corp. (SCC), once a household name in domestic robots has seen a steady decline in their revenues over the last three years. A new breed of agile startups has entered the market is able to respond quickly to their customers and are constantly pushing out features against their roadmap. SCC’s board understand that they need to pivot quickly to agile platforms in order to serve their customers better and to attract new ones. To this end, the SCC board have embraced cloud computing as part of their overall digital transformation strategy.</p><p>SCC have hired a new CIO, Adam Tyrell, a cloud veteran who has overseen large-scale cloud migrations at Fortune 500 companies such as Acme Corp. and Globex. Following his 90-day Plan to a letter, Adam announced SCC’s “Cloud first” strategy and began handing in notice to their six colo providers. SCC have two years to migrate all of their workloads to AWS cloud.</p><p>Adam quickly assembled a core team of PMs, Engineers and Enterprise Architects to form SCC’s first Cloud Centre of Excellence (CCoE). Their first responsibility was to produce an accurate inventory of SCC’s workloads including information about cloud migration goals, e.g. agility/cost/speed. Once the inventory was published, SCC began looking at the options around migrating their applications/workloads to the cloud.</p><h3>Cloud Migration Strategies</h3><p>In this article, we look at the 7 <em>Rs</em> migration strategies as illustrated below and incorporate research from Gartner and cross-reference these with use cases from Sirius Cybernetics Corp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CouAL6vjjPt8GA6-.png" /><figcaption><a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-database-migration/planning-phase.html">https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-database-migration/planning-phase.html</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2H_aKEeoGwXLhPqH" /><figcaption><a href="https://www.gartner.com/document/4008355">Quick Answer: How Much of My Application Portfolio Can I Lift and Shift to the Cloud?</a> Bill Swanton</figcaption></figure><h3>Retire</h3><p>Getting rid of applications during a migration programme is a quick-win for migration teams. There are various reasons for retiring (decommissioning or archiving) applications, including:</p><ul><li>realising that an application offers little, if any, business value. This is especially true where the cost of running/maintaining an application outweighs its value to the business. SCC’s employee directory <em>FindMe</em> is a good example of an application to retire. It was developed by a former intern before the advent of SCC’s Confluence Cloud rollout.</li><li>removing <em>zombie applications</em> or <em>idle applications</em> which experience low utilisation over a significant time period, e.g. between 2 and 20 percent over a period of 90 days with no inbound network connectivity. There are a number of VMs/applications in SCC’s <em>HackWeek</em> sandbox VLAN which have not been decommissioned following their creation.</li></ul><p>Stephen Orban <a href="https://aws.amazon.com/blogs/enterprise-strategy/6-strategies-for-migrating-applications-to-the-cloud/">mentions</a> that he “…found that as much as 10% (I’ve seen 20%) of an enterprise IT portfolio is no longer useful, and can simply be turned off.” Similarly, SCC have identified 8% of the identified applications as no longer in use company-wide. Some applications such as <em>FinanceWeb</em> duplicate the functionality of application <em>YouFin</em> and were still in use by employees who had not been trained to use <em>YouFin</em>.</p><h3>Retain</h3><p>Some applications cannot be migrated outside of a data centre due to physical dependencies on things such as USB licensing dongles. The choice here is to either replace the application or retain as-is. Again, in SCC’s case, time constraints drive the later. A good use case is SCC’s call centre analytics platform, <em>VoIPAnalyze</em> which uses a USB dongle to validate its licence.</p><h3>Rehost</h3><p>Although lift-and-shift (Rehosting) is often associated with data centre exits, it is almost always the option of last resort. You are unable to leverage cloud managed services and gain nothing in terms of agility for your applications. However, there may be compelling reasons to rehost such as in the case of SCC’s in-house Finance application <em>YouFin</em> which was developed by a niche software consultancy who have since dissolved. While decisions around replacing the application are ongoing, the project kick-off is expected to be after the planned data centre exit. This leaves no scope for <em>YouFin</em> to be replaced with e.g. a SaaS offering nor the time to <em>Replatform</em> (AKA lift-tinker-and-shift). However, running a Cloudamize Assessment against servers/VMs hosting applications such as <em>YouFin</em> will provide suggestions around capacity planning in the cloud, e.g. EC2 instance type/sizes thereby offering some optimisation. Interestingly, Gartner’s research shows that only 15% of applications considered were selected to be rehosted to the cloud.</p><h3>Relocate</h3><p>Also referred to as a hypervisor-level lift and shift, it is a migration strategy specific to VMC (VMware Cloud on AWS) whereby a VM is migrated intact to AWS cloud. SCC has 4 ESXi clusters containing 120 VMs servicing its core business applications which are earmarked for migration to VMC. Due to time constraints, a rehost was not considered.</p><h3>Replatform</h3><p>Also affectionately referred to as “lift-tinker-and-shift”, here you are not fundamentally changing the application architecture nor carrying out a complete refactoring of code. Instead, you are slightly augmenting the application to benefit from some cloud services such as managed databases e.g Amazon RDS. 22% of applications needed to be revised to run on cloud platforms according to the same Gartner report. The migration team have identified 20 applications at SCC whose backends can be switched to RDS MySQL.</p><h3>Repurchase</h3><p>Where an application cannot be easily remediated by the other “R” modernisation options, replacing the application with a custom-built application or moving to a SaaS application are the remaining options. The SaaS option is especially prevalent where an organisation has identified a <em>Buy before build</em> strategy. As an example, SCC’s ageing Customer CRM application <em>ContactRM</em> had already been targeted for replacement by a SaaS application, Salesforce. As SaaS applications completely remove the management overhead of an application, it is not surprising that Gartner has reported <em>Replace</em> as a popular choice with 40% opting for this choice.</p><h3>Rearchitect</h3><p>Here, much of the application code can be reused but its structure is changed to run better in the cloud or to simply take the opportunity to move from a monolithic architecture to a service-oriented one. It can be argued that the effort required to re-architect an application is better used in rebuilding it. However, rearchitecting may be a short-term tactical move in consideration of resource constraints. Predictably, Gartner identified only 2% of applications as falling into this category. SCC’s HR system <em>People1st</em> has been earmarked for rearchitecting with significant progress already being made with containerising its key components and decoupling the front-end from the business logic.</p><h3>Conclusion</h3><p>While fast-growing and agile startups “born in the cloud” may develop applications with a serverless or FaaS-first goal, most enterprises are at the beginning of their cloud journeys and often bring decades of software “baggage” with them. They cannot rearchitect their applications on-the-fly and it may take several years to realise the true agility benefits of the cloud.</p><p>It can be argued that enterprises are creating additional technical debt in the cloud by adopting a defacto Rehosting strategy. However, locating workloads in the cloud gives enterprises access to managed cloud services such as RDS, SES and others. Therefore, application architectures can be augmented to take advantage of cloud services through a Replatforming exercise, bringing them one step closer to modernizing their applications.</p><p>Once workloads are in the cloud, the evolution of their architecture continues as depicted by Gartner below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RnPiKIcyvcaqsRML.png" /><figcaption><a href="https://www.gartner.com/document/4002112">https://www.gartner.com/document/4002112</a></figcaption></figure><p><em>Mohammed Munem is a Principal Consultant at </em><a href="https://dae.mn/"><em>Daemon</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81a5f9b7e527" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daemonthinking/how-to-understand-the-7-rs-strategies-for-moving-applications-to-the-cloud-81a5f9b7e527">How to Understand the 7 Rs Strategies for Moving Applications to the Cloud</a> was originally published in <a href="https://medium.com/daemonthinking">Daemon thinking</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>