We’ve enabled AWS PrivateLink for Observability Cloud, giving you an additional inbound connection to send metrics, traces, and API service data to the platform. With PrivateLink, you can now securely send your data directly to the Observability ingest endpoint from your AWS environment. This is the best practice for secure service connections in AWS so you can prevent your sensitive data from traversing the internet.
Utilizing AWS PrivateLink helps improve your security posture so you can maintain regulatory compliance when you need to prevent sensitive data from traversing the internet. Additionally, sending data directly will allow you to save on data transfer costs.
To get started, you’d contact the Splunk Sales Engineer aligned to your team and provide a few details, including your AWS Account ID, the AWS Region and VPC endpoint ID. The Splunk team will do the rest to configure your PrivateLink.
Splunk Observability Cloud’s PrivateLink is enabled on ALL AWS realms and is limited to connectors in the same AWS region.