AWS scheduler documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in the PrivateLink connectivity description
Security assessment
This is a minor terminology update without security implications. The change doesn't alter the security posture or describe new security features of VPC interface endpoints.
Diff
diff --git a/scheduler/latest/UserGuide/vpc-interface-endpoints.md b/scheduler/latest/UserGuide/vpc-interface-endpoints.md index 0fa93face..57157d2f2 100644 --- a//scheduler/latest/UserGuide/vpc-interface-endpoints.md +++ b//scheduler/latest/UserGuide/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 Amazon EventBridge Scheduler. You can access EventBridge Scheduler 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 EventBridge Scheduler. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon EventBridge Scheduler. You can access EventBridge Scheduler 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 EventBridge Scheduler.