AWS m2 documentation change
Summary
Updated link text from 'Infrastructure setup requirements for AWS Blu Age Runtime (non-managed)' to 'Infrastructure setup requirements for AWS Blu Age Runtime'.
Security assessment
Change is purely cosmetic (removing '(non-managed)' qualifier). No security implications, vulnerabilities, or new security features documented. Maintains existing security context for IAM/VPC setup.
Diff
diff --git a/m2/latest/userguide/ba-runtime-deploy-container.md b/m2/latest/userguide/ba-runtime-deploy-container.md index 0a4eead54..c6f7b28d6 100644 --- a//m2/latest/userguide/ba-runtime-deploy-container.md +++ b//m2/latest/userguide/ba-runtime-deploy-container.md @@ -146 +146 @@ The following are the contents of `install-app.sh`. - 6. Specifically, for **Amazon ECS managed by AWS Fargate** case, when creating the Task definition, use the IAM role you created as part of the initial Infrastructure setup. Then, while creating the service, expand the **Networking** section, and configure the VPC, subnets, and security group that you created as part of the initial Infrastructure setup. See, [Infrastructure setup requirements for AWS Blu Age Runtime (non-managed)](https://docs.aws.amazon.com/m2/latest/userguide/ba-infrastructure-setup.html). + 6. Specifically, for **Amazon ECS managed by AWS Fargate** case, when creating the Task definition, use the IAM role you created as part of the initial Infrastructure setup. Then, while creating the service, expand the **Networking** section, and configure the VPC, subnets, and security group that you created as part of the initial Infrastructure setup. See, [Infrastructure setup requirements for AWS Blu Age Runtime ](https://docs.aws.amazon.com/m2/latest/userguide/ba-infrastructure-setup.html).