AWS prescriptive-guidance documentation change
Summary
Fixed URL formatting by adding an extra slash in multiple AWS documentation links (EFS, S3, CI/CD pipeline, database migration). No content changes beyond URL syntax correction.
Security assessment
The changes are purely URL syntax corrections (adding double slashes in paths). There is no mention of security vulnerabilities, mitigations, or new security features. The content about logging to CloudWatch and externalized configuration remains unchanged and represents existing best practices rather than new security documentation.
Diff
diff --git a/prescriptive-guidance/latest/modernization-containerize-javaee/technical-domains.md b/prescriptive-guidance/latest/modernization-containerize-javaee/technical-domains.md index 36fc6428f..4aa7e61f2 100644 --- a//prescriptive-guidance/latest/modernization-containerize-javaee/technical-domains.md +++ b//prescriptive-guidance/latest/modernization-containerize-javaee/technical-domains.md @@ -59 +59 @@ Consider the following containerization options: - 1. [Amazon Elastic File System (Amazon EFS)](https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html) – Amazon EFS is a managed NFS service that’s accessible from containers. Amazon EFS is integrated with Amazon ECS and Amazon EKS. If you use Amazon EFS, you don’t need to write custom scripts to mount EFS volumes to your containers. The first step for this option is to list all the file system paths in your application that are used to read or write. After you identify the file system path to be persisted, you can map the file system path to an EFS file system path. For more information, see [Tutorial: Using Amazon EFS file systems with Amazon ECS ](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/tutorial-efs-volumes.html) in the Amazon ECS documentation. Not all paths are required to be persisted, especially application log files. Most enterprise applications write log files to a local file system. As part of the containerization process, we recommend that you consider changing the logging destination to use Standard Out and Standard Error. This allows you to capture all output to CloudWatch Logs without managing log storage sizing and performance. For more information about logging in Amazon ECS, see [Using the awslogs log driver](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html) in the Amazon ECS documentation. + 1. [Amazon Elastic File System (Amazon EFS)](https://docs.aws.amazon.com//efs/latest/ug/whatisefs.html) – Amazon EFS is a managed NFS service that’s accessible from containers. Amazon EFS is integrated with Amazon ECS and Amazon EKS. If you use Amazon EFS, you don’t need to write custom scripts to mount EFS volumes to your containers. The first step for this option is to list all the file system paths in your application that are used to read or write. After you identify the file system path to be persisted, you can map the file system path to an EFS file system path. For more information, see [Tutorial: Using Amazon EFS file systems with Amazon ECS ](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/tutorial-efs-volumes.html) in the Amazon ECS documentation. Not all paths are required to be persisted, especially application log files. Most enterprise applications write log files to a local file system. As part of the containerization process, we recommend that you consider changing the logging destination to use Standard Out and Standard Error. This allows you to capture all output to CloudWatch Logs without managing log storage sizing and performance. For more information about logging in Amazon ECS, see [Using the awslogs log driver](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html) in the Amazon ECS documentation. @@ -61 +61 @@ Consider the following containerization options: - 2. [Amazon Simple Storage Service (Amazon S3)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) – Amazon S3 is less expensive than Amazon EFS and supports a wider bandwidth than Amazon EFS, but Amazon S3 requires a broader application code change than Amazon EFS. This is because Amazon S3 is not a file system. + 2. [Amazon Simple Storage Service (Amazon S3)](https://docs.aws.amazon.com//AmazonS3/latest/userguide/Welcome.html) – Amazon S3 is less expensive than Amazon EFS and supports a wider bandwidth than Amazon EFS, but Amazon S3 requires a broader application code change than Amazon EFS. This is because Amazon S3 is not a file system. @@ -68 +68 @@ Consider the following containerization options: -The containerization process involves changing and extending the application delivery process. In traditional environments, the application delivery process primarily involves Java artifacts (for example, .war and .ear files). In a container environment, the container image is the delivery unit. In addition to the process for building existing Java artifacts, you must build a process for building and delivering Docker containers. For more information about the pipeline process, 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. +The containerization process involves changing and extending the application delivery process. In traditional environments, the application delivery process primarily involves Java artifacts (for example, .war and .ear files). In a container environment, the container image is the delivery unit. In addition to the process for building existing Java artifacts, you must build a process for building and delivering Docker containers. For more information about the pipeline process, 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. @@ -72 +72 @@ The containerization process involves changing and extending the application del -Traditional application containerizations are often accompanied by database migration. To reduce migration risk, we recommend following the [migration strategy for relational databases](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-database-migration/welcome.html) (AWS Prescriptive Guidance). Containerized environments require externalized configuration, including database connection strings. You can use tools such as [Spring Cloud Config](https://github.com/spring-cloud/spring-cloud-config) (GitHub repository) to externalize the Java application configuration in a distributed environment. +Traditional application containerizations are often accompanied by database migration. To reduce migration risk, we recommend following the [migration strategy for relational databases](https://docs.aws.amazon.com//prescriptive-guidance/latest/strategy-database-migration/welcome.html) (AWS Prescriptive Guidance). Containerized environments require externalized configuration, including database connection strings. You can use tools such as [Spring Cloud Config](https://github.com/spring-cloud/spring-cloud-config) (GitHub repository) to externalize the Java application configuration in a distributed environment.