AWS serverlessrepo documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network connectivity explanation
Security assessment
Branding terminology update for Direct Connect service. No impact on security posture or documentation of VPC interface endpoints.
Diff
diff --git a/serverlessrepo/latest/devguide/vpc-interface-endpoints.md b/serverlessrepo/latest/devguide/vpc-interface-endpoints.md index e621bc295..c0e4383e8 100644 --- a//serverlessrepo/latest/devguide/vpc-interface-endpoints.md +++ b//serverlessrepo/latest/devguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and AWS Serverless Application Repository. You can access AWS Serverless Application Repository as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Serverless Application Repository. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Serverless Application Repository. You can access AWS Serverless Application Repository as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Serverless Application Repository.