Category: AWS PrivateLink

AWS customers running on-premises workloads that leverage Amazon S3 previously needed to set up proxies running on Amazon EC2 to access S3 gateway endpoints. With AWS PrivateLink for Amazon S3, you can provision interface VPC endpoints (interface endpoints) in your virtual private cloud. These endpoints are directly accessible from applications that are on-premises over VPN and AWS Direct Connect, or in a different AWS region over VPC peering.

The most valuable data for many companies is often the most sensitive and most regulated, such as electronic health records or financial data. Talend Data Fabric combines data integration, data integrity, and data governance in a single, unified platform that makes it easy to collect, transform, clean, govern, and share your data. Learn about Talend’s integration with AWS PrivateLink that allows customers to send data without using the public internet.

Customers often need to rely on third-party solutions to extract and transform data from sources such as Slack and Zendesk. Some vendors, however, do not support all of the sources and rely on multiple products to perform ETL and persist data into Snowflake. This post details how Amazon AppFlow simplifies the data transfer process, and how customers can use AWS PrivateLink for transmitting data over AWS rather than via the public internet.

Customers want to guarantee private connectivity to MongoDB Atlas running on AWS. All dedicated clusters on MongoDB Atlas are deployed in their own VPC, so customers usually connect to a cluster via VPC peering or public IP access-listing. AWS PrivateLink allows you to securely access MongoDB Atlas clusters from your own VPC. In this post, follow step-by-step instructions to configure AWS PrivateLink for MongoDB Atlas, ensuring private connectivity to your data.

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.