AWS prescriptive-guidance documentation change
Summary
Updated URL formatting in two documentation links by adding double slashes
Security assessment
Both changes are purely URL syntax corrections without any security context, vulnerability references, or security feature documentation additions.
Diff
diff --git a/prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md b/prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md index 17369c373..79a51442d 100644 --- a//prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md +++ b//prescriptive-guidance/latest/modernization-containerize-javaee/migration-approach.md @@ -9 +9 @@ 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. @@ -38 +38 @@ 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.