• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Astra DB Classic Documentation

    • Overview
      • Release notes
      • Astra DB FAQs
      • Astra DB glossary
      • Get support
    • Getting Started
      • Grant a user access
      • Load and retrieve data
        • Use DSBulk to load data
        • Use Data Loader in Astra Portal
      • Connect a driver
      • Build sample apps
      • Use integrations
        • Connect with DataGrip
        • Connect with DBSchema
        • Connect with JanusGraph
        • Connect with Strapi
    • Planning
      • Plan options
      • Database regions
    • Securing
      • Security highlights
      • Security guidelines
      • Default user permissions
      • Change your password
      • Reset your password
      • Authentication and Authorization
      • Astra DB Plugin for HashiCorp Vault
    • Connecting
      • Connecting to a VPC
      • Connecting Change Data Capture (CDC)
      • Connecting CQL console
      • Connect the Spark Cassandra Connector to Astra
      • Drivers for Astra DB
        • Connecting C++ driver
        • Connecting C# driver
        • Connecting Java driver
        • Connecting Node.js driver
        • Connecting Python driver
        • Drivers retry policies
      • Connecting Legacy drivers
      • Get Secure Connect Bundle
    • Migrating
      • FAQs
      • Preliminary steps
        • Feasibility checks
        • Deployment and infrastructure considerations
        • Create target environment for migration
        • Understand rollback options
      • Phase 1: Deploy ZDM Proxy and connect client applications
        • Set up the ZDM Automation with ZDM Utility
        • Deploy the ZDM Proxy and monitoring
          • Configure Transport Layer Security
        • Connect client applications to ZDM Proxy
        • Manage your ZDM Proxy instances
      • Phase 2: Migrate and validate data
      • Phase 3: Enable asynchronous dual reads
      • Phase 4: Change read routing to Target
      • Phase 5: Connect client applications directly to Target
      • Additional resources
        • Glossary
        • Troubleshooting
          • Troubleshooting tips
          • Troubleshooting scenarios
        • Contribution guidelines
        • Release Notes
    • Managing
      • Managing your organization
        • User permissions
        • Pricing and billing
        • Audit Logs
        • Configuring SSO
          • Configure SSO for Microsoft Azure AD
          • Configure SSO for Okta
          • Configure SSO for OneLogin
      • Managing your database
        • Create your database
        • View your databases
        • Database statuses
        • Use DSBulk to load data
        • Use Data Loader in Astra Portal
        • Monitor your databases
        • Manage multiple keyspaces
        • Using multiple regions
        • Terminate your database
        • Resize your classic database
        • Park your classic database
        • Unpark your classic database
      • Managing with DevOps API
        • Managing database lifecycle
        • Managing roles
        • Managing users
        • Managing tokens
        • Managing multiple regions
        • Get private endpoints
        • AWS PrivateLink
        • Azure PrivateLink
        • GCP Private Service
    • Astra CLI
    • Developing with Stargate APIs
      • Develop with REST
      • Develop with Document
      • Develop with GraphQL
        • Develop with GraphQL (CQL-first)
        • Develop with GraphQL (Schema-first)
      • Develop with gRPC
        • gRPC Rust client
        • gRPC Go client
        • gRPC Node.js client
        • gRPC Java client
      • Develop with CQL
      • Tooling Resources
      • Node.js Document API client
      • Node.js REST API client
    • Stargate QuickStarts
      • Document API QuickStart
      • REST API QuickStart
      • GraphQL API CQL-first QuickStart
    • API References
      • DevOps REST API v2
      • Stargate Document API v2
      • Stargate REST API v2
  • DataStax Astra DB Classic Documentation
  • Connect to Google Cloud private endpoints via Astra Portal

Connect to Google Cloud private endpoints via Astra Portal

To better protect your database connection, you can connect to a private endpoint using Astra Portal.

For details about using API calls instead, see Connect to Google Cloud Private Service Connect with the DevOps API.

This information applies to only serverless databases.

Also, private endpoints are available for only intra-region use. The region for your private endpoint in Google Cloud and your Astra DB database must match.

For pricing related to using private endpoints, see Pricing and billing.

The following roles can manage private endpoints:

  • Organization Administrator

  • Database Administrator

Alternatively, you can use a custom role with permissions to manage private endpoints.

For more, see Google Cloud Private Service Connect.

Prerequisites

  1. Access to your existing Google Cloud project.

  2. Create your Astra DB database using Astra Portal.

  3. Ensure you have permission to manage private endpoints.

  4. From the Google Cloud Console, get your Project ID.

  5. Create a Google Cloud Console network, subnetwork, and IP address for your private endpoint. For more, see Creating networks. The steps for private endpoints and sample values are listed below.

  6. Take note of which region your Google Cloud project and Google Cloud based Astra DB use (the chosen region must match).

To increase your security, restrict public access to your database using the access list.

Creating and referencing endpoint values between Google Cloud console and Astra Portal

Setting up the connection between Google Cloud and Astra DB private endpoints involves a few steps in both UIs.

Let’s start in Astra Portal

  1. On your organization’s Astra DB dashboard, click the link for your active, Google Cloud based database.

  2. Navigate to your database’s Settings tab, and notice the Private Endpoints section. At this point, no endpoints have been linked. Example:

    Astra Portal Settings tab with Private Endpoints section
  3. Click Configure Region and enter your Google Cloud Project ID as listed in Google Cloud Console.

  4. After entering your Google Cloud project-ID, click Configure Region.

  5. Astra Portal displays an updated Private Endpoints section, which includes a newly generated Service Name.

  6. Click Add Endpoint.

  7. On Add Private Endpoint, copy the generated Service Name. Example:

    Astra DB Add Private Endpoint copy Service Name

    In Astra Portal, keep the Add Private Endpoint dialog open. We’ll return here with an Endpoint ID after creating it in Google Cloud Console. Also note the region defined for your database. In this example, it is us-east4.

Switch over to Google Cloud Console

Ensure you’re in the Google Cloud project you identified above. Then:

  1. Navigate to Private Service Connect.

  2. So far in this example, no Google Cloud endpoint has been created:

    Google Cloud Private Connect Service with no endpoint created yet
  3. Click + CONNECT ENDPOINT.

  4. On the Connect Endpoint dialog, choose or enter:

    1. Target: Published service.

    2. Target service: Paste in the Service Name value that you copied in Astra Portal.

    3. Endpoint name: Enter any name, such as astra-google-cloud-endpoint. The name must start with a lowercase letter followed by up to 19 lowercase letters and numbers.

    4. Network: Enter a network value. In this example, we entered default.

    5. Subnetwork: Enter a subnetwork value, such as default.

    6. IP address: If not already assigned, click CREATE IP ADDRESS. On the form, enter a name such as static-address. Have Google Cloud assign the IP address automatically, or choose your own value.

      Google Cloud Connect Endpoint with Reserve Static IP Address dialog

      Click RESERVE.

    7. Region: Google Cloud sets the region from a portion of the Service Name that you pasted into the Target service field above. (Verify that the specified region is what you intended!) In this example, we’re using us-east4.

  5. Click ADD ENDPOINT.

Once accepted, Google Cloud displays data for the added endpoint. Example:

Google Cloud Private Service Connect added Endpoint example

Click the linked name of your newly added Endpoint to display the details screen in Google Cloud Console, and copy the Private Service Connect (PSC) ID. Example:

Google Cloud Private Service Connect details

You’ll need to paste in that PCS ID value in Astra Portal.

Return to Astra Portal

Back in Astra Portal, return to the Add Private Endpoint dialog that’s available from your databases’s Settings.

  1. In the Endpoint ID field, paste in the copied PSC ID value. Also enter a brief description of your Astra DB / Google Cloud endpoint.

  2. Click Add Endpoint.

    Astra DB displays the result. Example:

    Astra DB Settings Private Endpoint details

Your private endpoint is defined. However, notice the warning message if you have not taken further action in your Astra DB Settings.

You’ve set up a private endpoint for this database, but access to your database is still open to the public. Learn how to Manage access lists for public access by using the IP Access List options in Astra Portal Settings. You can enable the Restrict public access toggle, and you can manage endpoints with one or more access lists.

Create a DNS entry for your private endpoint

You can alias your private endpoint with a DNS record to use as your hostname in the Astra DB secure connect bundle. Here are the steps:

  1. Download your secure connect bundle for the region of your choice. Get your latest secure connect bundle.

  2. Unzip the secure connect bundle.

  3. In config.json, copy the host key’s value.

  4. In Google Cloud Console, create a private zone to route traffic to your endpoint IP. Update the domains to use REST and CQL. Examples:

    • REST

    • CQL

    efe451fe-709e-4700-9185-5cf0fd3474a7-2-us-east-1.apps.astra.datastax.com
    efe451fe-709e-4700-9185-5cf0fd3474a7-2-us-east-1.db.astra.datastax.com

    See Create a private zone.

Once those steps are completed, you can connect to your private endpoint using your updated secure connect bundle. For more, see Drivers for Astra DB.

Remove a private endpoint

In Google Cloud Console:

  1. Go to Private Service Connect.

  2. Choose the endpoint you want to remove.

  3. Choose Delete.

In Astra Portal:

  1. Go to the Settings tab for your database.

  2. Choose the endpoint you want to remove.

  3. Click Delete.

What’s next?

  • Refer to related topics for other cloud providers that are linked from Connect via a private endpoint.

  • Learn how to Manage access lists for public access.

  • For more, see Private Service Connect and the DevOps API reference.

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage