Data Ingest and Search are core Splunk Cloud Platform capabilities that customers rely on. However, customers primarily in the financial, public and healthcare sectors are increasingly concerned about traversing their data workloads over the public Internet. To support these requirements, we introduced AWS PrivateLink support on the Splunk Cloud Platform.
Private Connectivity helps insulate data exchange channels between a customer’s AWS cloud environment and Splunk Cloud Platform from the public Internet. Since Oct '22, compliance customers with an AWS presence can send their ingest data (Forwarder and HEC traffic) to their Splunk Cloud Platform stack over private endpoints, without exposing it over the public internet.
Expanding on this foundational capability, I am excited to announce that starting today customers with compliance subscriptions, such as PCI, HIPAA, IRAP, and FedRAMP moderate, will be able to perform their core search and access APIs flowing through the Search endpoints via AWS Privatelink.
Powered by Splunk Cloud Platforms's Admin Config Service APIs, onboarding private connectivity (both for search and data ingest) on your stack is completely self-serviceable. 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 PrivateLink pricing. AWS is a trademark of Amazon.com, Inc. or its affiliates.
