Announcing AWS PrivateLink Support on Splunk Cloud Platform

Moving to Splunk Cloud Platform has a lot of benefits, including flexibility, agility, and scalability. However, we understand that migrating to cloud is not a trivial task and can also bring up security concerns especially when it comes to having your data traverse the internet.

By default, Splunk Cloud Platform addresses this concern by enabling encryption of data in flight using TLS 1.2+ for ingest and HTTPS for search data. While our industry-leading standards meet the security requirements of the majority of Splunk Cloud Platform customers, organizations in highly regulated environments require additional capabilities to help ensure their compliance and security needs are met. For a subset of customers in the financial, healthcare, and public sector — sending their mission-critical data over the public internet (or publicly accessible IPs) had been a soaring pain point, thwarting their transition to cloud. 

We wanted to eliminate this barrier!

I am excited to announce support for private connectivity on the Splunk Cloud Platform through AWS PrivateLink. Private Connectivity enables our customers in regulated environments with an AWS presence to send data (Forwarder and HEC traffic) to their Splunk Cloud stack over private endpoints, without ever exposing it over the public internet. Starting today, private connectivity is available as an opt-in connectivity option with PCI, HIPAA, IRAP, and FedRAMP Moderate subscriptions at no additional cost*.

As a true SaaS provider, we want to offer solutions that are scalable, widely acceptable, and easy to onboard, all while ensuring your needs are being met. Through AWS PrivateLink and Splunk Cloud's self-service capabilities (Admin Config Service APIs), we provide a seamless onboarding experience for customers seeking private connectivity in their environment.

Sending data through private connectivity offers several benefits:

Security

• Unidirectional network communications: The connection is always initiated from your AWS VPC (service consumer) and flows into the Splunk Cloud Platform through service endpoints configured specifically for your Splunk Cloud stack. The VPC endpoint service on the Splunk stack is configured to only permit connections from AWS Account IDs provided by you.
  
  
• Clearly defined security boundaries: You can configure security group(s) and create endpoint policies that apply to service endpoints and Splunk controls. These security groups help ensure that the service endpoints are only exposed to connections over Private Connectivity
   

Simplified Operations

• Designed to work with overlapping CIDR blocks: Using AWS PrivateLink eliminates the need for coordinating and negotiating IP address spaces, allowing for better manageability as your needs scale. 
  
  
• Requires minimal DNS registration of private IP addresses: Since there is no need to coordinate IP space and routing, you are in complete control of provisioning and managing the DNS records required to resolve to Splunk’s endpoint service. 
   

Bolster Your Compliance Posture

• By preventing your mission-critical data from traversing the internet, private connectivity reduces your exposure to threats and helps you expand your Splunk Cloud Platform – all while working within your security and compliance boundaries. 

We hope you enjoy using private connectivity as much as our preview customers have. You can learn more about the functionality and evaluate if it is the right choice for you by reviewing the private connectivity Overview and the Getting started guide.

^{*Customers are responsible for AWS data transfer costs associated with their VPC. For more info, refer to AWS Private link pricing.}

^{AWS is a trademark of Amazon.com, Inc. or its affiliates.}