Secure Integrations With Any Cloud, Any Network | Confluent Cloud
Apr 9, 2024Erick Lee

Summary
This post details how Confluent Cloud enables secure integrations with external data sources and sinks through various networking features. It explains the use of Public Egress IPs for IP-based firewalling, AWS Gateway and Azure VNet Service Endpoints for secure traffic within cloud networks, DNS Forwarding for resolving private FQDNs in peered networks, and Egress Access Points for PrivateLink connections. It provides specific examples for AWS S3 Sink Connector and HTTP source connector, outlining configuration steps and underlying technologies like TLS, VPC Interface Endpoints, and Azure Private Endpoints.
More from the Confluent Private Cloud Broker Density and Policy Enforcement trail
- Proven: Up to 73% Fewer Brokers With Confluent Private Cloud – and More
- Unified Stream Manager GA in Confluent Platform 8.1
- Introducing Confluent Private Cloud
- Introducing Private Network Interface (PNI) on AWS: Lower Kafka Networking Costs by 50%
- Cluster Linking for Azure Private Link is available in Confluent Cloud