This is the statement of Andy Jassy – CEO of Amazon Web Service in the opening of re:Invent in 2014. So how do businesses now use this “new standard<\/strong>” effectively? How do\u00a0I move physical and virtualized server systems to the cloud?<\/em>\u00a0And choose what ways and tools to\u00a0maintain the continuity of business activities?<\/strong>\u00a0Perhaps these are the top concerns of business leaders and managers in the current period of digital transformation.<\/p>\n In this article, VTI Cloud will introduce five key stages of moving the system to\u00a0the AWS cloud environment<\/strong>\u00a0so that we can better understand the process of implementing this “new standard”! The article was by Do Thanh Tung \u2013 Solutions Architect of VTI Cloud.<\/p>\n Shifting a certain number of IT assets (not necessarily all) to the cloud environment is seen as “migration.” The migration process can be one or more data centers or multiple complex system components combined with each other rather than necessarily a single system.<\/p>\n Businesses considering moving their systems to the cloud may want to upgrade their system performance, expire their data center leases, or want to expand their business models,… The reason for moving up above the cloud environment may have its own characteristics,\u00a0but there is always a common solution for any case.<\/span><\/p>\n These solutions are based on<\/span>\u00a0the<\/span> knowledge and experience gained from different organizations and businesses that have successfully transformed their traditional IT models to AWS. Therefore, every organization and business that is considering moving its systems to AWS are encouraged to adopt these “best practices”.<\/p>\n In the process of moving, we should start with the simplest applications or systems.<\/span>\u00a0Then continue to optimize the system during the transition, gradually increasing the complexity and finally completing the system movement.<\/p>\n This is the most important period as it sets directions, goals, and potential timelines for shifting to AWS. During this period, it is necessary to have clear and knowledgeable business objectives about the life cycle, architecture, and the links of existing applications\/systems to develop a good plan.<\/p>\n In order to have a plan to shift workloads from traditional data centers to AWS environments, it is critical to have an understanding of the complexity, the mutual dependence between applications, and the level of enterprise dependence on those workloads. In addition, it is also important to get information about their resource usage, configuration, and behavior patterns. This can be used to calculate the Total cost of ownership (TCO) of workloads running on AWS and future migration strategies and implementation plans.<\/p>\n There are quite a few different tools that can be used during this period. AWS also offers a free service, the\u00a0AWS Application Discovery Service.<\/strong> This is a tool used to collect specific information about the application from data centers using agents or agentless. The information collected can then be exported as an Excel file to analyze or use available AWS analytics tools such as Amazon Athena and<\/span>\u00a0<\/strong>Amazon\u00a0QuickSight.<\/strong>\u00a0It also integrates with\u00a0the AWS Migration Hub<\/strong>\u00a0to track the actual migration status of workloads.<\/p>\n This is the implementation phase of the five-step process where the focus is on the actual migration of applications to the AWS environment. Based on a pre-defined migration strategy, it is possible to consider redesigning\u00a0applications<\/strong>\u00a0so that they can be\u00a0more optimized when<\/strong> running on AWS environments. This is followed by the migration and verification of the operation of the application.<\/p>\n Finally,\u00a0testing for<\/strong>\u00a0each application after moving to a new environment is also an important requirement.<\/p>\n In addition, continuous improvement and repeated\u00a0<\/strong>review of design, migration, and authentication phases should be integrated to ensure that the system operates entirely on AWS. For applications\/systems that have been successfully migrated,\u00a0Post Implementation Review is<\/strong>\u00a0always encouraged to ensure that new applications\/systems are successfully migrated in the future.<\/p>\n As with the above stage, AWS offers a variety of solutions and tools that help customers during the transition:<\/p>\n VMware Cloud on AWS<\/p>\n<\/li>\n AWS Server Migration Service<\/p>\n<\/li>\n Database Migration Service<\/p>\n<\/li>\n AWS Data Sync<\/p>\n<\/li>\n AWS Data Transfer Family<\/p>\n<\/li>\n<\/ul>\n Adopting a hybrid model (part ground infrastructure and part of the cloud) or shifting all workloads to AWS will require organizational operational improvements to make the most of what this environment has to offer. AWS provides methods and tools adapted to the operation of applications and systems in the cloud, one of which includes:<\/p>\n DevOps focuses on a combination of application developers, IT operations management, security,… to automate and speed up application deployment. It focuses on core principles such as Infrastructure as Code, Continuous Delivery, automation, monitoring, and security. The services AWS provides such as AWS CodeBuild,<\/strong>\u00a0AWS CodeCommit,\u00a0<\/strong>and AWS CodeDeploy<\/strong>\u00a0can be used to build CI\/CD pipelines for software construction, testing, and deployment.<\/p>\n Serverless, also\u00a0known as Function as a Service (FaaS),<\/strong>is a minimalist cloud computing model where application functions can be individually scheduled for on-demand implementation, often based on events. The use is extremely easy for users, they only have to pay for the time spent instead of the entire cost of the application as in the traditional way where it still has to pay even if the application does not work.<\/p>\n AWS Lambda<\/strong>\u00a0provides the most flexible serverless platform and easily deploys cloud-based serverless applications by different providers today.<\/p>\n AWS has developed the best methods for deploying cloud system architecture based on five key components: Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization.<\/p>\nAbout “migration”<\/strong><\/h2>\n
![\"migration](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/migration-la-gi-1024x655.png\")
<\/p>\nFive phases for moving to AWS<\/strong><\/h2>\n
![\"migration](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/migration-plan.png\")
<\/p>\nPhase 1: Preparing for the moving to AWS and evaluating opportunities<\/h3>\n
Phase 2: Portfolio analysis and planning<\/h3>\n
Phases 3 and 4: Design, move and verify applications<\/h3>\n
![\"moving](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/migration-planning.png\")
<\/p>\n\n
Phase 5: Modern operating model that after moving to AWS will apply<\/h3>\n
\n
DevOps:<\/span><\/strong><\/h4>\n<\/li>\n<\/ul>\n
![\"devops](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/devops-tool.png\")
<\/p>\n\n
Serverless<\/h4>\n<\/li>\n<\/ul>\n
\n
AWS Well-Architected Framework<\/h4>\n<\/li>\n<\/ul>\n
\n
![\"aws](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/01\/aws-well-architected-review.jpg\")
<\/p>\n