AWS lambda: Fix broken documentation links
Summary
Corrected double slashes in AWS documentation URLs for MSK, EC2, and VPC guides.
Security assessment
Changes only fix URL formatting; no security implications or content modifications.
Evidence
- 1. Create a security group for your interface Amazon VPC endpoints, `endpointSecurityGroup`, that allows inbound TCP traffic on 443 from `clusterSecurityGroups`. Follow the procedure in [Create a security group](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/working-with-security-groups.html#creating-security-group) in the Amazon EC2 documentation to create a security group. Then, follow the procedure in [Add rules to a security group](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule) in the Amazon EC2 documentation to add appropriate rules.
Diff
diff --git a/lambda/latest/dg/services-msk-tutorial.md b/lambda/latest/dg/services-msk-tutorial.md index 906a64d8e..576540c73 100644 --- a//lambda/latest/dg/services-msk-tutorial.md +++ b//lambda/latest/dg/services-msk-tutorial.md @@ -38 +38 @@ An AWS account with the following preconfigured resources: -**To fulfill these prerequisites, we recommend following[Getting started using Amazon MSK](https://docs.aws.amazon.com//msk/latest/developerguide/getting-started.html) in the Amazon MSK documentation.** +**To fulfill these prerequisites, we recommend following[Getting started using Amazon MSK](https://docs.aws.amazon.com/msk/latest/developerguide/getting-started.html) in the Amazon MSK documentation.** @@ -105 +105 @@ You can configure the following steps using the AWS Management Console. - 1. Create a security group for your interface Amazon VPC endpoints, `endpointSecurityGroup`, that allows inbound TCP traffic on 443 from `clusterSecurityGroups`. Follow the procedure in [Create a security group](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/working-with-security-groups.html#creating-security-group) in the Amazon EC2 documentation to create a security group. Then, follow the procedure in [Add rules to a security group](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule) in the Amazon EC2 documentation to add appropriate rules. + 1. Create a security group for your interface Amazon VPC endpoints, `endpointSecurityGroup`, that allows inbound TCP traffic on 443 from `clusterSecurityGroups`. Follow the procedure in [Create a security group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html#creating-security-group) in the Amazon EC2 documentation to create a security group. Then, follow the procedure in [Add rules to a security group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule) in the Amazon EC2 documentation to add appropriate rules. @@ -115 +115 @@ When adding your inbound rules, create a rule for each security group in `cluste - 2. Create an endpoint connecting the Lambda service to the Amazon VPC containing your Amazon MSK cluster. Follow the procedure in [Create an interface endpoint](https://docs.aws.amazon.com//vpc/latest/privatelink/create-interface-endpoint.html). + 2. Create an endpoint connecting the Lambda service to the Amazon VPC containing your Amazon MSK cluster. Follow the procedure in [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html). @@ -146 +146 @@ When adding your inbound rules, create a rule for each security group in `cluste - 3. Create an endpoint connecting the AWS STS service to the Amazon VPC containing your Amazon MSK cluster. Follow the procedure in [Create an interface endpoint](https://docs.aws.amazon.com//vpc/latest/privatelink/create-interface-endpoint.html). + 3. Create an endpoint connecting the AWS STS service to the Amazon VPC containing your Amazon MSK cluster. Follow the procedure in [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html). @@ -183 +183 @@ When adding your inbound rules, create a rule for each security group in `cluste -Some of this traffic is allowed by default security group rules, so if your cluster is attached to a single security group, and that group has default rules, additional rules are not necessary. To adjust security group rules, follow the procedures in [Add rules to a security group](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule) in the Amazon EC2 documentation. +Some of this traffic is allowed by default security group rules, so if your cluster is attached to a single security group, and that group has default rules, additional rules are not necessary. To adjust security group rules, follow the procedures in [Add rules to a security group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule) in the Amazon EC2 documentation.