AWS prescriptive-guidance documentation change
Summary
Updated tool references from 'Porting Assistant for .NET' and 'AWS Microservice Extractor' to 'AWS Transform for .NET', removed some tool specifics, adjusted documentation links, and clarified migration guidance
Security assessment
The changes primarily update tool names and references without mentioning security vulnerabilities, mitigations, or security features. The removal of App2Container reference in containerization section simplifies guidance but doesn't indicate a security issue. No evidence of addressing vulnerabilities or describing security controls.
Diff
diff --git a/prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-net-workloads.md b/prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-net-workloads.md index f3fb79eb5..5ee6b9b2e 100644 --- a//prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-net-workloads.md +++ b//prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-net-workloads.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Options, tools, and best practices for migrating Microsoft workloads to AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Options, tools, and best practices for migrating Microsoft workloads to AWS](introduction.html) @@ -17 +17 @@ Choosing a migration path for your .NET workload relies on the following key fac - * **Find the .NET version used** – There are two different .NET implementations supported by Microsoft: .NET Framework (1.0–4.8) and .NET (.NET Core 1.0–3.1 and .NET 5 and later). Both share many of the same components and can run application code written using the different .NET programming languages (such as C#, F#, and VB.NET). Choosing a migration strategy and hosting service depends on the runtime used since .NET Framework runs on Windows while the newer .NET is multi-platform. For the .NET Framework, you can either host on a Windows OS or refactor your code to use the newer .NET. The newer .NET can also be hosted on Linux OS-based services. When modernizing .NET Framework-based workloads, you can use [Porting Assistant for .NET](https://aws.amazon.com/porting-assistant-dotnet/) or the [AWS Toolkit for .NET Refactoring](https://aws.amazon.com/visual-studio-net/) to scan your code and generate a compatibility assessment report. By finding if there are incompatible .NET Framework APIs referenced by your project, you can plan for the complexity of a migration project and decide if and when to refactor your code to use a newer runtime. + * **Find the .NET version used** – There are two different .NET implementations supported by Microsoft: .NET Framework (1.0–4.8) and .NET (.NET Core 1.0–3.1 and .NET 5 and later). Both share many of the same components and can run application code written using the different .NET programming languages (such as C#, F#, and VB.NET). Choosing a migration strategy and hosting service depends on the runtime used since .NET Framework runs on Windows while the newer .NET is multi-platform. For the .NET Framework, you can either host on a Windows OS or refactor your code to use the newer .NET. The newer .NET can also be hosted on Linux OS-based services. When modernizing .NET Framework-based workloads, you can use [AWS Transform for .NET](https://docs.aws.amazon.com/transform/latest/userguide/dotnet.html) to scan your code and generate a compatibility assessment report. By finding if there are incompatible .NET Framework APIs referenced by your project, you can plan for the complexity of a migration project and decide if and when to refactor your code to use a newer runtime. @@ -34 +34 @@ There are three different migration paths to consider when migrating your .NET w - * **Refactor** – Choose this approach if you can invest time and effort into making code and architecture changes that reduce operational overhead and achieve better scaling, high availability, and disaster recovery by using AWS cloud-native services. Refactoring involves modernizing your codebase by porting existing .NET framework applications to .NET (previously .NET Core) or modernizing an existing codebase to run better in the cloud. You can use the [AWS SDK for .NET](https://aws.amazon.com/sdk-for-net/) to call many AWS cloud services from within your .NET code. Tools such as [Porting Assistant for .NET](https://aws.amazon.com/porting-assistant-dotnet/) and [AWS Microservice Extractor for .NET](https://aws.amazon.com/microservice-extractor/) can be used to port your codebase from .NET Framework to .NET and break your monolithic application into microservices. By refactoring your existing .NET workloads to run on [AWS Lambda](https://aws.amazon.com/lambda/), you can use serverless computing to avoid provisioning and managing infrastructure. + * **Refactor** – Choose this approach if you can invest time and effort into making code and architecture changes that reduce operational overhead and achieve better scaling, high availability, and disaster recovery by using AWS cloud-native services. Refactoring involves modernizing your codebase by porting existing .NET framework applications to .NET (previously .NET Core) or modernizing an existing codebase to run better in the cloud. You can use the [AWS SDK for .NET](https://aws.amazon.com/sdk-for-net/) to call many AWS cloud services from within your .NET code. Tools such as [AWS Transform for .NET](https://docs.aws.amazon.com/transform/latest/userguide/dotnet.html) can be used to port your codebase from .NET Framework to .NET. By refactoring your existing .NET workloads to run on [AWS Lambda](https://aws.amazon.com/lambda/), you can use serverless computing to avoid provisioning and managing infrastructure. @@ -72 +72 @@ Replatforming involves changing your hosting environment with little to no code -You can use [AWS Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/) to replatform your .NET Framework workloads. If you package your ASP.NET-based or ASP.NET Core-based applications, then you can quickly deploy and manage applications in AWS without having to learn about the infrastructure that runs those applications. This reduces complexity without restricting choice or control. You simply upload your application and Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. +You can use [AWS Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/) to replatform your .NET Framework workloads. If you package your ASP.NET-based or ASP.NET Core-based applications, then you can quickly deploy and manage applications in AWS without having to learn about the infrastructure that runs those applications. This reduces complexity without restricting choice or control. You simply upload your application, and Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. @@ -106 +106 @@ Containerizing .NET based applications depends on the .NET runtime used. Conside - * **.NET Framework-based applications run on Windows containers** – Adding Docker support to existing applications is done by creating a Docker file that outlines how the application needs to be containerized. You can use [AWS App2Container](https://aws.amazon.com/app2container/) to easily containerize and migrate existing .NET Framework-based applications to AWS. App2Container scans your IIS server to determine the required files and extracts the target application to create a Docker image. You can also use App2Container to create the deployment artifacts needed to host your application in the AWS Cloud. + * **.NET Framework-based applications run on Windows containers** – Adding Docker support to existing applications is done by creating a Docker file that outlines how the application needs to be containerized. @@ -125 +125 @@ The first refactoring option available is to migrate your existing .NET Framewor -You can migrate from the .NET Framework by using [Porting Assistant for .NET](https://aws.amazon.com/porting-assistant-dotnet/), which scans your code files and creates a report that helps plan your application portfolio migration roadmap. Porting Assistant for .NET can also reduce your porting overhead by identifying incompatible .NET Core APIs and packages and finding known replacements. The [AWS Toolkit for .NET refactoring](https://aws.amazon.com/visual-studio-net/) is a Visual Studio extension that reduces the time and effort required for developers to refactor legacy .NET applications to cloud-based alternatives on AWS. It assesses the application source code to recommend possible modernization pathways such as porting to .NET Core, identifies Windows-specific IIS and Active Directory dependency configurations, performs code modifications where possible to enable Linux compatibility, and helps validate the refactored application on AWS services. Migrating .NET Framework applications to .NET enables running them on ARM64-based Graviton processors for a better price to performance ratio. For more information, see [.NET on Graviton](https://github.com/aws/aws-graviton-getting-started/blob/main/dotnet.md) on GitHub and [Graviton2 and containers](https://catalog.workshops.aws/graviton/en-US/amazoncontainers) from _Optimizing cost with AWS Graviton based services_ in the AWS Workshop Studio documentation. +You can migrate from the .NET Framework by using [AWS Transform for .NET](https://docs.aws.amazon.com/transform/latest/userguide/dotnet.html), which scans your code files and creates a report that helps plan your application portfolio migration roadmap. Porting Assistant for .NET can also reduce your porting overhead by identifying incompatible .NET Core APIs and packages and finding known replacements. Migrating .NET Framework applications to .NET enables running them on ARM64-based Graviton processors for a better price-to-performance ratio. For more information, see [.NET on Graviton](https://github.com/aws/aws-graviton-getting-started/blob/main/dotnet.md) on GitHub and [Graviton and containers](https://catalog.workshops.aws/graviton/en-US/amazoncontainers) in the AWS Workshop Studio documentation. @@ -129 +129 @@ You can migrate from the .NET Framework by using [Porting Assistant for .NET](ht -Many development teams want to re-architect their existing monolithic applications into microservices. By moving to microservice-based architectures, your development teams can increase development agility, decrease compute costs, scale services individually, and decrease their deployment times. [AWS Microservice Extractor for .NET](https://aws.amazon.com/microservice-extractor/) simplifies the process of refactoring older monolithic applications into a microservice-based architecture. By identifying components and grouping functionality, development teams can incrementally extract functionality from .NET Framework monolithic applications into .NET services. +Many development teams want to re-architect their existing monolithic applications into microservices. By moving to microservice-based architectures, your development teams can increase development agility, decrease compute costs, scale services individually, and decrease their deployment times. By identifying components and grouping functionality, development teams can incrementally extract functionality from .NET Framework monolithic applications into .NET services.