AWS prescriptive-guidance documentation change
Summary
Updated documentation links, improved section headers, fixed URL formatting, and enhanced clarity in migration guidance
Security assessment
Changes focus on documentation structure, formatting, and clarity improvements rather than addressing security vulnerabilities. The updates emphasize CI/CD pipelines and testing best practices but don't introduce new security-specific content or address identified vulnerabilities. The contraction fix (can't) and URL corrections are maintenance updates without security implications.
Diff
diff --git a/prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md b/prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md index da5b04125..2383ebc8a 100644 --- a//prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md +++ b//prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Containerizing traditional Java EE applications for the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Containerizing traditional Java EE applications for the AWS Cloud](introduction.html) @@ -7 +7 @@ -Discovery and planningClustering optionsVendor-specific packagesTarget container platformAutomated testing +Start the discovery and planning processUnderstand clustering options for high availability and scalabilityAssess the compatibility of vendor-specific packagesSelect a target container platformPrepare for automated testing @@ -11 +11 @@ Discovery and planningClustering optionsVendor-specific packagesTarget container -This section describes an approach for containerizing traditional Java EE applications in the AWS Cloud. For more general migration guidelines, see [Mobilize your organization to accelerate large-scale migrations](https://docs.aws.amazon.com//prescriptive-guidance/latest/strategy-migration/welcome.html) in the AWS Prescriptive Guidance documentation. +This section describes an approach for containerizing traditional Java EE applications in the AWS Cloud. For more general migration guidelines, see [Mobilize your organization to accelerate large-scale migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration/welcome.html) in the AWS Prescriptive Guidance documentation. @@ -40 +40 @@ Choosing the right container platform for Java EE depends on your business needs -Migrating Java EE applications to a new application server requires code or configuration changes other than business logic. Without an automated test and build process for your current application, you can’t verify that your code and configuration changes won’t break existing business logic. We recommend that you establish an automated build and test pipeline in the first phase of the project, which includes modernizing manual test processes and unmaintained application build settings (such as build.xml in Apache Ant) with mainstream build tools such as [Maven](https://maven.apache.org/) (Apache Maven documentation) or [Gradle](https://gradle.org/) (Gradle documentation). For more information, see [Automatically build and deploy a Java application to Amazon EKS using a CI/CD pipeline](https://docs.aws.amazon.com//prescriptive-guidance/latest/patterns/automatically-build-and-deploy-a-java-application-to-amazon-eks-using-a-ci-cd-pipeline.html) in the AWS Prescriptive Guidance documentation. +Migrating Java EE applications to a new application server requires code or configuration changes other than business logic. Without an automated test and build process for your current application, you can't verify that your code and configuration changes won't break existing business logic. We recommend that you establish an automated build and test pipeline in the first phase of the project, which includes modernizing manual test processes and unmaintained application build settings (such as build.xml in Apache Ant) with mainstream build tools such as [Maven](https://maven.apache.org/) (Apache Maven documentation) or [Gradle](https://gradle.org/) (Gradle documentation). For more information, see [Automatically build and deploy a Java application to Amazon EKS using a CI/CD pipeline](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/automatically-build-and-deploy-a-java-application-to-amazon-eks-using-a-ci-cd-pipeline.html) in the AWS Prescriptive Guidance documentation.