Category: AWS PrivateLink

Many organizations prefer to connect to SaaS or managed services over a VPN. If you are an independent software vendor that has to periodically change your network configuration, these customer VPNs present a challenge. The solutions detailed in this post describe different approaches to isolating virtual private clouds that host applications and services from an enterprise network. You can use these strategies to add more services to your customers with no changes to customer network configurations, avoiding delays.

The amount and variety of existing and newly-generated data in today’s connected world is unparalleled. As this growth continues, so does the opportunity for organizations to extract real value from their data. Teradata Vantage is a modern analytics platform that combines open source and commercial analytic technologies. It can drive autonomous decision-making by helping you to operationalize insights, solve complex business problems, and enable descriptive, predictive, and prescriptive analytics.

Before making a purchasing decision, AWS customers tell us they want to know if a tool or application will integrate with AWS services running in their cloud environment. To meet this need for customers, we are excited to introduce AWS Service Ready. This program identifies and validates products from APN Technology Partners that integrate with specific AWS services, and recommends these products to customers.

There are AWS PrivateLink-enabled SaaS offerings from APN Partners for everything from managed databases to analytics tools and fraud detection APIs. By integrating with AWS PrivateLink, these offerings make it easy to consume fully-managed services while still maintaining a private network configuration that used to require you to host applications yourself. To help you find SaaS products like these, we are excited to feature solutions from APN SaaS Partners who fully support AWS PrivateLink access to their applications.

Customers looking to consume AWS PrivateLink-enabled services from service providers need a mechanism to route traffic from their VPCs and on-premises networks to PrivateLink VPC endpoints. The service providers, in turn, want to make it easy to consume their PrivateLink-enabled services by managing such routing mechanisms. In this post, we describe four DNS mechanisms to route traffic from customer networks to the PrivateLink VPC endpoints.