Dark Mode

To better protect your database connection, you can connect to a private endpoint using the Astra DB private endpoint.Private endpoints are available for only intra-region use.The region for your private endpoint in the AWS console and your Astra DB database must match.

This information applies to only serverless databases.

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 about AWS PrivateLink, see AWS PrivateLink.

    Only VPC owners can create resources such as VPC endpoints, subnets, route tables, and NACLs. Participants cannot view, modify, or delete resources that belong to other participants or the VPC owner. Thus a user cannot create resources, including a private endpoint, in a shared VPC that is owned by a different AWS account. To see which account owns your VPC, look at the Owner ID in the AWS Console. Example:

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

    If you are using Postman for your API calls, ensure you use the raw option to enter the body of your API call.

    • Get the allowed principal from your AWS account.
    • Enter the allowed principal for your private endpoints to Astra DB:
    • Use the serviceName to create an endpoint in your AWS Console.
    • Accept your AWS private endpoint connection with your serviceName :
    • Create a DNS entry for your private endpoint.

    You can now connect to your private endpoint using your updated secure connect bundle. For more, see Drivers for Astra.

    Remove a private endpoint

    • Delete a private endpoint from your Astra DB:
    • Remove your connection from AWS PrivateLink:

    What’s next?