AWS PrivateLink provides private connectivity between your Amazon VPCs and services such as Instana SaaS—keeping your telemetry data (traces, metrics, logs) completely off the public internet. PrivateLink uses Elastic Network Interfaces (ENIs) to create interface endpoints that securely route traffic through AWS’s backbone infrastructure.
Why Use PrivateLink with Instana?
Combining AWS PrivateLink and IBM Instana unlocks several key benefits for customers running regulated, distributed, or mission-critical workloads:
• End-to-end private observability — No public IPs or internet exposure
• In-Region and Cross-Region support — Monitor workloads across any AWS region
• High-performance data ingestion — Uses AWS’s low-latency backbone
• Compliance-ready — Aligns with strict data residency and industry regulations
• Lower cost — Based on early customer deployments, network egress fees are reduced by 70–90% compared to NAT gateways
How to Get Started?
The setup process is simple and well-documented. To use AWS PrivateLink with Instana, you’ll:
1. Request AWS PrivateLink setup via IBM Support
2. Identify your Instana endpoint service name
3. Create a VPC Interface Endpoint (via AWS Console or CLI)
5. Verify metrics via the AWS Monitoring tab
You can find the detailed walkthrough—including screenshots and CLI commands—here:
AWS PrivateLink for Instana is currently available in:
We’re actively working to expand coverage. Additional regions, including Singapore, and GovCloud, are part of our 2025 roadmap for new SaaS deployments.
💬 Have questions or want to share feedback?
#AWS