AWS macie documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC interface endpoints documentation
Security assessment
Consistency update in service naming. No changes to security architecture or PrivateLink implementation details that would affect access controls.
Diff
diff --git a/macie/latest/user/vpc-interface-endpoints-macie.md b/macie/latest/user/vpc-interface-endpoints-macie.md index e32e880bd..c02207da4 100644 --- a//macie/latest/user/vpc-interface-endpoints-macie.md +++ b//macie/latest/user/vpc-interface-endpoints-macie.md @@ -9 +9 @@ Considerations for Macie interface endpointsCreating an interface endpoint for M -You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and Amazon Macie. You can access Macie 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 Macie. +You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and Amazon Macie. You can access Macie 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 Macie.