AWS PrivateLink for MongoDB Atlas #

Use the following steps to securely connect your Starburst Galaxy cluster to MongoDB Atlas using AWS PrivateLink.

You must work with a Starburst technical resource to complete your PrivateLink configuration. Contact your account team for more information.

You must configure a separate AWS PrivateLink connection for each catalog you want to connect to Starburst Galaxy.

In MongoDB Atlas, complete the following steps:

• Create a private endpoint
• Find your private endpoint name
• Find your connection string

Create a private endpoint #

1. In MongoDB Atlas, create a new private endpoint for your project. For assistance, see the MongoDB documentation.
2. Choose AWS as your cloud provider.

Find your endpoint service ID #

1. Once your Atlas endpoint service is ready, find the endpoint service ID.
2. Provide the endpoint service ID to your Starburst technical resource.

Enter your VPC endpoint ID #

1. Ask your Starburst technical resource to provide you with your VPC endpoint ID.
2. In MongoDB Atlas, enter the VPC endpoint ID into the appropriate field.
3. Finish configuring your private endpoint.

Find your private endpoint name #

1. In MongoDB Atlas, once your private endpoint is available, find the endpoint name.
2. Provide the endpoint name to your Starburst technical resource.

Find your connection string #

1. In MongoDB Atlas, find the connection string for connecting an application using a private endpoint. For assistance with locating the connection string, see the MongoDB documentation.
2. Provide the connection string to your Starburst technical resource.

As the final step, contact your Starburst technical resource to complete your PrivateLink configuration.

See also #

• MongoDB catalogs