AWS lambda documentation change
Summary
Fixed URL formatting by adding double slashes after domain names in documentation links
Security assessment
Changes only correct URL syntax without modifying security content. No security implications as VPC peering guidance remains unchanged.
Diff
diff --git a/lambda/latest/dg/configuration-vpc-cross-account.md b/lambda/latest/dg/configuration-vpc-cross-account.md index 63dbc57dc..f176a7e4b 100644 --- a//lambda/latest/dg/configuration-vpc-cross-account.md +++ b//lambda/latest/dg/configuration-vpc-cross-account.md @@ -15 +15 @@ When you allow access between accounts or VPCs, check that your plan meets the s -In this tutorial, you connect two accounts together with a peering connection using IPv4. You configure a Lambda function that is not already connected to a Amazon VPC. You configure DNS resolution to connect your function to resources that do not provide static IPs. To adapt these instructions to other peering scenarios, consult the [VPC Peering Guide](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html). +In this tutorial, you connect two accounts together with a peering connection using IPv4. You configure a Lambda function that is not already connected to a Amazon VPC. You configure DNS resolution to connect your function to resources that do not provide static IPs. To adapt these instructions to other peering scenarios, consult the [VPC Peering Guide](https://docs.aws.amazon.com//vpc/latest/peering/what-is-vpc-peering.html). @@ -140 +140 @@ Create a VPC peering connection request from your function's VPC (the requester -To create your peering connection and prepare your resource's VPC to use the connection, log in to your resource's account with a role that holds the permissions listed in the prerequisites. The steps to log in may be different based on how the account is secured. For more information about how to sign in to an AWS account, see the [AWS Sign-in User Guide](https://docs.aws.amazon.com/signin/latest/userguide/what-is-sign-in.html). In your resource's account, perform the following procedures. +To create your peering connection and prepare your resource's VPC to use the connection, log in to your resource's account with a role that holds the permissions listed in the prerequisites. The steps to log in may be different based on how the account is secured. For more information about how to sign in to an AWS account, see the [AWS Sign-in User Guide](https://docs.aws.amazon.com//signin/latest/userguide/what-is-sign-in.html). In your resource's account, perform the following procedures. @@ -238 +238 @@ Log in to your function's account, then update the VPC configuration. -For more information about considerations you may encounter while updating your route tables, consult [Update your route tables for a VPC peering connection](https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-routing.html). +For more information about considerations you may encounter while updating your route tables, consult [Update your route tables for a VPC peering connection](https://docs.aws.amazon.com//vpc/latest/peering/vpc-peering-routing.html).