AWS PrivateLink can now be used to access third-party SaaS applications, says Amazon Web Services (AWS). Customers can also use PrivateLink to connect services across different accounts and VPCs within their own organizations.

The vast majority of Amazon EC2 instances now run in Amazon VPCs, says Amazon, with customers relying on the ability to limit access to their VPC from the Internet as a critical component of their security. However, this presents a challenge when using third-party SaaS applications, as customers often have to make a choice between allowing Internet access from their VPC in order to access these SaaS applications, or not using them at all.

Traffic between a customer’s VPC and a AWS PrivateLink-powered service stays within the AWS network and doesn’t traverse the internet, says AWS. Services supported on AWS PrivateLink are delivered using private IP connectivity and security groups.

AWS PrivateLink is generally available in US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), EU (London), EU (Ireland), EU (Frankfurt), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo) and South America (São Paulo) regions.

The announcement was made at the company’s annual re: Invent conference currently under way in Las Vegas, Nevada.

[Image courtesy: Amazon]