AWS resource-explorer documentation change
Summary
Removed announcement about immediate access feature launch and minor wording update regarding Direct Connect.
Security assessment
Purely removes outdated feature announcement and makes non-security-related terminology change ('AWS Direct Connect' to 'Direct Connect'). No security implications identified.
Diff
diff --git a/resource-explorer/latest/userguide/vpc-interface-endpoints.md b/resource-explorer/latest/userguide/vpc-interface-endpoints.md index 668bdebcd..f7cb1f933 100644 --- a//resource-explorer/latest/userguide/vpc-interface-endpoints.md +++ b//resource-explorer/latest/userguide/vpc-interface-endpoints.md @@ -7,2 +6,0 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -AWS Resource Explorer now provides immediate access to resource search and discovery capabilities in a Region. With this launch, you no longer need to activate Resource Explorer to discover your resources. [Learn more](https://docs.aws.amazon.com/resource-explorer/latest/userguide/manage-immediate-resource-discovery-experience.html) - @@ -11 +9 @@ AWS Resource Explorer now provides immediate access to resource search and disco -You can use AWS PrivateLink to create a private connection between your VPC and AWS Resource Explorer. You can access Resource Explorer 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 Resource Explorer. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Resource Explorer. You can access Resource Explorer 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 Resource Explorer.