AWS prescriptive-guidance documentation change
Summary
Complete restructuring of document content from technical migration guidance to navigation/UI elements and placeholder content. Removed detailed technical sections about AWS Application Migration Service advantages/disadvantages and replaced with account links, filters, and loading placeholders.
Security assessment
The changes appear to be structural/navigational updates rather than security-related content modifications. No security vulnerabilities, mitigations, or security feature documentation was added/removed. The removed content was technical migration guidance, while added content focuses on site navigation and UI elements.
Diff
diff --git a/prescriptive-guidance/latest/migration-database-rehost-tools/mgn.md b/prescriptive-guidance/latest/migration-database-rehost-tools/mgn.md index c40c6ec62..1764b3575 100644 --- a//prescriptive-guidance/latest/migration-database-rehost-tools/mgn.md +++ b//prescriptive-guidance/latest/migration-database-rehost-tools/mgn.md @@ -1 +1 @@ -[](/pdfs/prescriptive-guidance/latest/migration-database-rehost-tools/migration-database-rehost-tools.pdf#mgn "Open PDF") +Skip to main content @@ -3 +3,4 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing a migration tool for rehosting databases](welcome.html) + * English + * [Contact us](https://aws.amazon.com/contact-us/?nc2=h_ut_cu) + * Support + * My account @@ -5 +7,0 @@ -AdvantagesDisadvantagesBest-fit scenarios @@ -7 +8,0 @@ AdvantagesDisadvantagesBest-fit scenarios -# Migration with AWS Application Migration Service @@ -9 +9,0 @@ AdvantagesDisadvantagesBest-fit scenarios -Most large lift-and-shift migrations to AWS use [AWS Application Migration Service](https://aws.amazon.com/application-migration-service/). This service works on a physical level by moving data that is stored on any directly attached block storage device (such as a hard drive or SAN drive) to the corresponding Amazon Elastic Block Store (Amazon EBS) storage device on AWS. It essentially implements a traditional backup/restore procedure (by cloning the hard drives), but also provides a recovery point objective (RPO) of near seconds and a recovery time objective (RTO) of minutes by achieving Continuous Data Protection (CDP) synchronization mode between the source systems and the target storage devices in the staging area. @@ -11 +11 @@ Most large lift-and-shift migrations to AWS use [AWS Application Migration Servi -## Advantages + * [ ](https://aws.amazon.com/?nc2=h_home) @@ -13 +12,0 @@ Most large lift-and-shift migrations to AWS use [AWS Application Migration Servi -For lift-and-shift migrations of any scale, AWS Application Migration Service has many benefits: @@ -15 +14 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * The replication is easy to set up (it doesn’t require a steep learning curve). + * Filter: All @@ -17 +16,2 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * It’s fast to scale, by rolling out agents on the source machines. + * Sign in to console + * [Create account](https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_su&src=header_signup) @@ -19 +18,0 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * You can use the [Cloud Migration Factory](https://aws.amazon.com/solutions/implementations/cloud-migration-factory-on-aws/) to automate most manual tasks, manage multiple machines, and orchestrate migration waves. @@ -21 +19,0 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * It supports a [wide range of x86 operating system architectures](https://docs.aws.amazon.com/mgn/latest/ug/Supported-Operating-Systems.html). @@ -23 +21 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * It supports any type of source environment (on-premises data center, any other cloud, or another AWS Region). +AWS Prescriptive Guidance @@ -25 +23 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * It is application-agnostic, so it supports any application running on the source servers. + * [Home](/prescriptive-guidance/) @@ -27 +25 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha - * No license or purchase is required. AWS offers pay-as-you-go pricing, so you pay for the service only as long as you use it, without requiring long-term contracts or complex licensing. AWS Application Migration Service provides a free 90-day period per server, which is enough for most migrations. For details, see [AWS Application Migration Service pricing](https://aws.amazon.com/application-migration-service/pricing/) on the AWS website. + * [Accelerating cloud transformation](/prescriptive-guidance/accelerating-cloud-transformation/) @@ -28,0 +27 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha + * [Agentic AI](/prescriptive-guidance/agentic-ai/) @@ -29,0 +29 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha + * [Large migrations](/prescriptive-guidance/large-migrations/) @@ -30,0 +31 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha + * [Migration tools](/prescriptive-guidance/migration-tools/) @@ -32 +32,0 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha -## Disadvantages @@ -34 +33,0 @@ For lift-and-shift migrations of any scale, AWS Application Migration Service ha -When you use block-level replication tools such as AWS Application Migration Service, you might encounter the following corner cases and factors to consider: @@ -36 +34,0 @@ When you use block-level replication tools such as AWS Application Migration Ser - * You can migrate clustered systems with shared block storage, such as Windows Server Failover Cluster (WSFC) or some Microsoft SQL Server Always On availability group clusters, with the same tool, but they require specific procedures and longer cutover windows (a few approaches are described in this [blog post](https://aws.amazon.com/blogs/storage/migrating-your-microsoft-windows-clusters-to-aws-using-cloudendure-migration/)). @@ -38 +36,2 @@ When you use block-level replication tools such as AWS Application Migration Ser - * Systems that have a high rate of data changes (such as OLTP databases) might have higher performance or network requirements, which complicate migration efforts. + * [AWS](/)› + * [Prescriptive Guidance](/prescriptive-guidance/) @@ -40 +38,0 @@ When you use block-level replication tools such as AWS Application Migration Ser - * Network bandwidth must be sufficient for the amount of data to be transferred within the planned migration and cutover time window. This is because Application Migration Service doesn’t provide an offline shipping option, unlike [AWS Snowball](https://aws.amazon.com/snowball/). @@ -42 +39,0 @@ When you use block-level replication tools such as AWS Application Migration Ser - * Migration requires a small downtime window, within an RTO of minutes. AWS Application Migration Service uses EBS snapshots as part of the migration process, and new EBS disks that are created from such snapshots initially have worse performance. With some database read patterns, this might increase the effective cutover window until the migrated database is at full performance. @@ -43,0 +41 @@ When you use block-level replication tools such as AWS Application Migration Ser +# AWS Prescriptive Guidance @@ -44,0 +43 @@ When you use block-level replication tools such as AWS Application Migration Ser +Resources from AWS technology experts and AWS Partners to help accelerate cloud adoption and modernization @@ -45,0 +45 @@ When you use block-level replication tools such as AWS Application Migration Ser +## Guides @@ -47 +47 @@ When you use block-level replication tools such as AWS Application Migration Ser -## Best-fit scenarios +Guidance for planning and implementing strategies, with focus on best practices and tools, for architects, managers, and technical leads @@ -49 +49 @@ When you use block-level replication tools such as AWS Application Migration Ser -AWS Application Migration Service covers almost any lift-and-shift migration fully, with few disadvantages, as discussed in the previous two sections. This tool can handle most of the corner cases, such as database clusters, as long as the longer cutover window required for these systems satisfies your migration requirements. +Loading @@ -51 +51 @@ AWS Application Migration Service covers almost any lift-and-shift migration ful -The following sections cover two scenarios in more depth: +Loading @@ -53 +53 @@ The following sections cover two scenarios in more depth: - * Large-scale migration with multiple migration waves +Loading @@ -55 +55 @@ The following sections cover two scenarios in more depth: - * Single application migration that requires minimal downtime +Loading @@ -56,0 +57 @@ The following sections cover two scenarios in more depth: +Loading @@ -57,0 +59 @@ The following sections cover two scenarios in more depth: +## Patterns @@ -58,0 +61 @@ The following sections cover two scenarios in more depth: +Steps, architectures, tools, and code for implementing common migration, optimization, and modernization scenarios, for builders and other hands-on users @@ -60 +63 @@ The following sections cover two scenarios in more depth: -### Large-scale migration with multiple migration waves +Loading @@ -62 +65 @@ The following sections cover two scenarios in more depth: -An example of a large-scale migration is a data center exit that is characterized by size and speed requirements, and usually involving a specific time constraint (such as the end of the lease contract for the data center). In this case, the scale dictates the approach. The migration waves are determined and grouped by applications, including databases, and each wave has a planned preparation, migration, and final cutover phase with specific downtime requirements. +Loading @@ -64 +67 @@ An example of a large-scale migration is a data center exit that is characterize -Inside each migration wave, the database servers are best moved at scale by using AWS Application Migration Service block-level replication, except for a few exceptions for the following special cases that might require a separate migration approach: +Loading @@ -66 +69 @@ Inside each migration wave, the database servers are best moved at scale by usin - * Most clustered database systems +Loading @@ -68 +71 @@ Inside each migration wave, the database servers are best moved at scale by usin - * Database systems where the rate of change exceeds available network throughput (which might result in a replication lag) +Loading @@ -69,0 +73 @@ Inside each migration wave, the database servers are best moved at scale by usin +## Strategies @@ -70,0 +75 @@ Inside each migration wave, the database servers are best moved at scale by usin +Business perspectives, methodologies, and frameworks for cloud migration and modernization, for CxOs and senior managers @@ -71,0 +77 @@ Inside each migration wave, the database servers are best moved at scale by usin +Loading @@ -73 +79 @@ Inside each migration wave, the database servers are best moved at scale by usin -For each special case, consider the tradeoff between your downtime requirements and the level of effort involved in using another migration tool. In some cases, it’s much easier to use the same migration approach for all systems instead of using separate tools and creating different processes for specific systems. If AWS Application Migration Service doesn’t support the downtime requirements for a specific system, we recommend that you use one of the methods described in the [Migration with native database tools and AWS DMS](./dms.html) section instead. +Loading @@ -75 +81 @@ For each special case, consider the tradeoff between your downtime requirements -### Single application migration +Loading @@ -77 +83 @@ For each special case, consider the tradeoff between your downtime requirements -The single application scenario represents a granular approach for migrating a single business-critical application that requires minimum or near-zero downtime during migration, or a few such applications. The scope of the migration might vary, depending on business criticality and downtime requirements, as opposed to the speed and scale requirements of the previous (large-scale migration) scenario. If the application allows for downtime within the RTO of AWS Application Migration Service, it should be handled in the same way as any large-scale migration described earlier. +Loading @@ -79 +85 @@ The single application scenario represents a granular approach for migrating a s -However, in cases where the cutover time must be as close to the minimum as possible—for example, when the migrated database has read patterns that require a long time to operate at full performance and the cutover windows have to remain small—you should consider a more detailed and granular approach. In general, that approach involves additional steps and requirements, which require more effort and time. One of the steps is to separate the database migration from the application server migration and to use the database migration tools described in the [next section](./dms.html) to keep the source and the target databases in sync. You can use various methods to achieve synchronization. Each method has its own advantages and disadvantages, and involves different tradeoffs between the amount of downtime and the complexity of synchronization. Nevertheless, keeping the database in sync between the source and target environments enables you to unlink the database layer from the application layer. Assuming that application servers don’t store persistent data locally, but pass everything to the database layer, synchronization also removes downtime restrictions from the application layer. +Loading @@ -81 +87 @@ However, in cases where the cutover time must be as close to the minimum as poss -Decoupling the database and application layers enables you to migrate application servers by using AWS Application Migration Service as in the previous scenario. Target application servers can be started in the target environment while source systems are still working, processing the data, and storing it in the database layer. Because the database layer is already in sync with the target, cutover time is minimal—it only involves switching networks and redirecting customer requests from the old source system to the target environment. You can use multiple methods to do this, following the guidance for [blue/green deployments](https://docs.aws.amazon.com/whitepapers/latest/blue-green-deployments/update-dns-routing-with-amazon-route-53.html), typically by switching DNS endpoints, using weighted DNS zones, using [AWS Global Accelerator](https://aws.amazon.com/global-accelerator/) to reduce Time to Live (TTL) DNS propagation delays, and similar methods. +## Content collections @@ -83 +89 @@ Decoupling the database and application layers enables you to migrate applicatio - **Javascript is disabled or is unavailable in your browser.** +1 / 4 @@ -85 +91 @@ Decoupling the database and application layers enables you to migrate applicatio -To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. +[ business-productivity Accelerating cloud transformation Learn more ](/prescriptive-guidance/accelerating-cloud-transformation/) @@ -87 +93 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -[Document Conventions](/general/latest/gr/docconventions.html) +[ ai-ml Agentic AI Learn more ](/prescriptive-guidance/agentic-ai/) @@ -89 +95 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Migration waves, servers, and databases +[ migration Large migrations to the AWS Cloud Learn more ](/prescriptive-guidance/large-migrations/) @@ -91 +97 @@ Migration waves, servers, and databases -Migration with native database tools and AWS DMS +[ migration Migration tools Learn more ](/prescriptive-guidance/migration-tools/) @@ -93 +99 @@ Migration with native database tools and AWS DMS -Did this page help you? - Yes +## More information @@ -95 +101 @@ Did this page help you? - Yes -Thanks for letting us know we're doing a good job! +Services, tools, and resources to help with your large migration journey @@ -97 +103 @@ Thanks for letting us know we're doing a good job! -If you've got a moment, please tell us what we did right so we can do more of it. +### Additional resources @@ -99 +105,5 @@ If you've got a moment, please tell us what we did right so we can do more of it -Did this page help you? - No + * [Migrate and modernize with AWS](/migrate-modernize-build/cloud-migration/) + * [AWS Architecture Center](/architecture/) + * [AWS Documentation](https://docs.aws.amazon.com/) + * [AWS Professional Services](/professional-services/) + * [AWS Partner Network](/partners/) @@ -101 +110,0 @@ Did this page help you? - No -Thanks for letting us know this page needs work. We're sorry we let you down. @@ -103 +112,76 @@ Thanks for letting us know this page needs work. We're sorry we let you down. -If you've got a moment, please tell us how we can make the documentation better. + +### Feedback and support + + * [Send us your feedback](https://docs.aws.amazon.com/forms/aws-doc-feedback?hidden_service_name=ProServe%20Enterprise%20GPS&topic_url=http://aws.amazon.com/prescriptive-guidance/) + * [Contact AWS Support](/premiumsupport/) + + + +[Create an AWS account](https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc1=f_ct&src=footer_signup) + +## Learn + + * [What Is AWS?](/what-is-aws/?nc1=f_cc) + * [What Is Cloud Computing?](/what-is-cloud-computing/?nc1=f_cc) + * [What Is Agentic AI?](/what-is/agentic-ai/?nc1=f_cc) + * [Cloud Computing Concepts Hub](/what-is/?nc1=f_cc) + * [AWS Cloud Security](/security/?nc1=f_cc) + * [What's New](/new/?nc1=f_cc) + * [Blogs](/blogs/?nc1=f_cc) + * [Press Releases](https://press.aboutamazon.com/press-releases/aws) + + + +## Resources + + * [Getting Started](/getting-started/?nc1=f_cc) + * [Training](/training/?nc1=f_cc) + * [AWS Trust Center](/trust-center/?nc1=f_cc) + * [AWS Solutions Library](/solutions/?nc1=f_cc) + * [Architecture Center](/architecture/?nc1=f_cc) + * [Product and Technical FAQs](/faqs/?nc1=f_dr) + * [Analyst Reports](/resources/analyst-reports/?nc1=f_cc) + * [AWS Partners](/partners/work-with-partners/?nc1=f_dr) + + + +## Developers +