AWS prescriptive-guidance documentation change
Summary
Updated navigation links, corrected service names (AWS Transform MGN to AWS Application Migration Service), improved table formatting, fixed typographical errors, and enhanced section titles.
Security assessment
Changes are primarily editorial and navigational. The security considerations section remains unchanged except for minor formatting adjustments. No vulnerabilities, security incidents, or new security features are addressed or documented.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-foundation-playbook/landing-zone.md b/prescriptive-guidance/latest/large-migration-foundation-playbook/landing-zone.md index 57dfb5d85..a76b3b0f3 100644 --- a//prescriptive-guidance/latest/large-migration-foundation-playbook/landing-zone.md +++ b//prescriptive-guidance/latest/large-migration-foundation-playbook/landing-zone.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Foundation playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Foundation playbook for AWS large migrations](introduction.html) @@ -11 +11 @@ Infrastructure considerationsOperations considerationsSecurity considerations -A _landing zone_ is a well-architected AWS environment that is scalable and secure. By establishing standards for the landing zone, such as defining the number of accounts and designing the subnets and security groups, you build a solid foundation. This foundation gives you the ability to enable, provision, and operate your environment for both business agility and governance at scale while accelerating your cloud adoption journey. For more information about landing zones and strategies for building them, see [Setting up a secure and scalable multi-account AWS environment](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-aws-environment/). +A _landing zone_ is a well-architected AWS environment that is scalable and secure. By establishing standards for the landing zone, such as defining the number of accounts and designing the subnets and security groups, you build a solid foundation. This foundation gives you the ability to enable, provision, and operate your environment for both business agility and governance at scale while accelerating your cloud adoption journey. For more information about landing zones and strategies for building them, see [Setting up a secure and scalable multi-account AWS environment](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-aws-environment/welcome.html). @@ -28 +28 @@ Some key factors of the landing zone that can affect your large migration progra -This section reviews the infrastructure, operations, and security questions that you should consider when building your AWS landing zone. It also contains recommendations for how to design and deploy your landing zone to support a large migration project. As you answer the questions in this section, these decisions become migration principles, which you document according to the instructions in [Document your decisions as large migration principles](./document.html). +This section reviews the infrastructure, operations, and security questions that you should consider when building your AWS landing zone. It also contains recommendations for how to design and deploy your landing zone to support a large migration project. As you answer the questions in this section, these decisions become _migration principles_ , which you document according to the instructions in [Document your decisions as large migration principles](./document.html). @@ -34,2 +34,2 @@ Have you considered? | Description | Actions -How much data will you migrate per day and per week? | The desired migration velocity dictates the type of network connection and network throughput requirements. It also can affect the wave planning selection criteria. | After you have completed the portfolio assessment, determine the total amount of storage needed for all migrated resources in the cloud. Use this value to calculate the amount of time required to migrate the data using the current network bandwidth. You might need to increase the bandwidth to meet the migration timeframes, or you might need to use alternatives, such as AWS Snow Family solutions. In the [foundation playbook templates](samples/foundation-playbook-templates.zip), you can use the _Data replication calculator_ (Microsoft Excel format) to calculate the required bandwidth for each migration wave. -What is the average write speed of the source servers in each wave? | The bandwidth required to transfer the replicated data is based on the write speed of the participating source servers. The amount of bandwidth required for server replication is the average write speed of your source servers multiplied by the number of servers in the largest wave. | During portfolio assessment, you need to determine the average number of data writes performed per by each server. In the [foundation playbook templates](samples/foundation-playbook-templates.zip), you can use the _Data replication calculator_ (Microsoft Excel format) to understand the bandwidth required for migration traffic. The bandwidth required for migration traffic is in addition to the bandwidth used for normal business activity. After the migration is complete, you no longer need the additional bandwidth to support the migration activities. +How much data will you migrate per day and per week?| The desired migration velocity dictates the type of network connection and network throughput requirements. It also can affect the wave planning selection criteria.| After you have completed the portfolio assessment, determine the total amount of storage needed for all migrated resources in the cloud. Use this value to calculate the amount of time required to migrate the data using the current network bandwidth. You might need to increase the bandwidth to meet the migration timeframes, or you might need to use alternatives, such as AWS Snow Family solutions. You can use the attached _Data replication calculator_ (Microsoft Excel format) to calculate the required bandwidth for each migration wave. +What is the average write speed of the source servers in each wave?| The bandwidth required to transfer the replicated data is based on the write speed of the participating source servers. The amount of bandwidth required for server replication is the average write speed of your source servers multiplied by the number of servers in the largest wave.| During portfolio assessment, you need to determine the average number of data writes performed per by each server. You can use the attached _Data replication calculator_ (Microsoft Excel format) to understand the bandwidth required for migration traffic. The bandwidth required for migration traffic is in addition to the bandwidth used for normal business activity. After the migration is complete, you no longer need the additional bandwidth to support the migration activities. @@ -43 +43 @@ Do any servers need to retain their source IP address? | The safest and easiest - * Carefully assess cross subnet communications between servers. + * Carefully assess cross‑subnet communications between servers. @@ -47 +47 @@ Do any servers need to retain their source IP address? | The safest and easiest -How much latency is acceptable between the source and AWS? | It is common to start the migration with VPN links because they can be set up quickly and then transition to a direct connection established using AWS Direct Connect. VPN links generally have higher and more variable latency, which affects data throughput and, more importantly, application response times. | If you are using a high or variable latency connection type, review each application’s requirements and plan the migration waves accordingly. Plan to put applications that require low latency connections in later waves, when alternative connection types are available. +How much latency is acceptable between the source and AWS?| It is common to start the migration with VPN links because they can be set up quickly and then transition to a direct connection established using AWS Direct Connect. VPN links generally have higher and more variable latency, which affects data throughput and, more importantly, application response times.| If you are using a high or variable latency connection type, review each application's requirements and plan the migration waves accordingly. Plan to put applications that require low latency connections in later waves, when alternative connection types are available. @@ -68 +68 @@ Are there any compliance requirements for your workloads? | Workloads might hav -Does your security team need to review and approve any tools or services that you plan to use during the migration? | A large migration project to the AWS Cloud uses many services, such as AWS Transform MGN, AWS Database Migration Service (AWS DMS), AWS DataSync, and portfolio discovery tools (such as Flexera One). Some organizations require that all new tools and services are approved before use. | Work with the migration team to identify all of the tools, services, and applications that you expect to use in the migration. Work with the security team to review the company policies and approve these tools accordingly before the migration starts. +Does your security team need to review and approve any tools or services that you plan to use during the migration?| A large migration project to the AWS Cloud uses many services, such as AWS Application Migration Service, AWS Database Migration Service (AWS DMS), AWS DataSync, and portfolio discovery tools (such as Flexera One). Some organizations require that all new tools and services are approved before use.| Work with the migration team to identify all of the tools, services, and applications that you expect to use in the migration. Work with the security team to review the company policies and approve these tools accordingly before the migration starts. @@ -78 +78 @@ Platform foundation -On-premises considerations +On-premises considerations for a large migration