Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Private Endpoints for App Services

  • Capella App Services
  • concept
Private endpoints for App Services let applications in your cloud provider’s private network connect to App Services without sending data across the public Internet.

A private endpoint connects the private network where your applications run to the network that contains your Capella infrastructure. Your application traffic stays on your cloud provider’s network. This can improve security and lower data transfer costs.

What You Can Reach Over a Private Endpoint

Applications in your private network can reach the following over a private endpoint:

  • Couchbase Lite sync

  • Admin API access

  • Metrics API access, such as Prometheus exporters

Private endpoint connections and public Internet connections provide the same App Services capabilities. You can use a private endpoint for some operations and the public Internet for others.

Private Endpoints and Public Access

Private endpoints do not replace the public App Endpoint. Couchbase Lite clients outside your private network, such as mobile devices, still connect through the public Internet using TLS. Through the public Internet, the Admin API and Metrics API accept connections only from IP addresses on your allowed IP list.

Requirements

  • Your application’s private network and App Services must use the same cloud provider and run in the same region.

  • Capella supports private endpoints for App Services on Amazon Web Services only.

See Also