AWS Direct Connect Concepts: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
PrivateLink is similar to Direct Connect, in that it allows connecting privately between to locations on the network, but unlike Direct Connect, PrivateLink is used as a networking construct '''inside AWS''' to privately expose a service or an application residing in one VPC, that of a service provider, to other consumer VPCs within an AWS Region. | PrivateLink is similar to Direct Connect, in that it allows connecting privately between to locations on the network, but unlike Direct Connect, PrivateLink is used as a networking construct '''inside AWS''' to privately expose a service or an application residing in one VPC, that of a service provider, to other consumer VPCs within an AWS Region. | ||
Also see: {{Internal|Amazon_VPC_Concepts#Relationship_between_Direct_Connect_and_PrivateLink|VPC Concepts | PrivateLink}} | Also see: {{Internal|Amazon_VPC_Concepts#Relationship_between_Direct_Connect_and_PrivateLink|VPC Concepts | PrivateLink}} | ||
Latest revision as of 01:42, 17 January 2023
External
Internal
Overview
AWS Direct Connect is a method used to connect private networks, either from customer premises or data center locations, to AWS, notably to the customer’s VPC environment built within the AWS cloud.
Relationship between Direct Connect and PrivateLink
PrivateLink is similar to Direct Connect, in that it allows connecting privately between to locations on the network, but unlike Direct Connect, PrivateLink is used as a networking construct inside AWS to privately expose a service or an application residing in one VPC, that of a service provider, to other consumer VPCs within an AWS Region.
Also see: