Connect a Soda Agent to Soda Cloud via AWS PrivateLink

Last modified on 29-Mar-23

If you use AWS services for your infrastructure and you have deployed or will deploy a Soda Agent in an EKS cluster, you can use an AWS PrivateLink to provide private connectivity with Soda Cloud.

Create an Endpoint for a PrivateLink

Log in to your AWS console and navigate to your VPC dashboard.
Follow the AWS documentation to Connect to an endpoint service as the service customer.
For security reasons, Soda does not publish its Service name. Email support@soda.io with your AWS account ID to request the PrivateLink service name. Refer to AWS documentation for instructions on how to obtain your account ID.
After creating the endpoint, return to the VPC dashboard. When the status of the endpoint becomes Available, the PrivateLink is ready to use. Be aware that this make take more than 10 minutes.
Deploy a Soda Agent to your AWS EKS cluster, or, if you have already deployed one, restart your Soda Agent to begin sending data to Soda Cloud via the PrivateLink.
```
kubectl -n soda-agent rollout restart deploy
```
After you have started the agent and validated that it is running, log into your Soda Cloud account, then navigate to your avatar > Scans & Data > Agents tab. Refresh the page to verify that you see the agent you just created in the list of Agents.

Go further

Need help? Join the Soda community on Slack.
Learn how to deploy a Soda Agent in AWS.

Was this documentation helpful?

What could we do to improve this page?

Suggest a docs change in GitHub.
Share feedback in the Soda community on Slack.

Last modified on 29-Mar-23