> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-aws/aws-privatelink-setup.md).

# AWS PrivateLink Setup

groundcover's BYOC comes with VPC service endpoint (PrivateLink) built in.\
The PrivateLink endpoint let you ingest data through private network and reduce data transfer costs.

## Prerequisites

* Get the VPC service endpoint name value provided by groundcover during BYOC installation.
* **Cross-region Ingestion:** To keep cloud cost low as possible, PrivateLink connection is enabled only on the backend region by default. To allow cross-region endpoint send the required region to the groundcover team.

## Setup PrivateLink connection

1. Make sure DNS resolution is enabled on the VPC.
2. Create Security group for the VPC endpoint that allow port 443 from your workloads ( K8s nodes / EC2s).
3. Create VPC endpoint.
   1. Choose the service endpoint name provided by groundcover.
   2. (Optional) If the endpoint created on different region than the BYOC backend, click on cross region and choose the backend's region
   3. Enable DNS
4. Choose the required subnets for the VPC endpoint.
5. Choose the security group created in step 2 for the VPC endpoint
6. Create the VPC endpoint

## Troubleshooting

Open shell on the monitored workload on the same VPC

Use nslookup to determine if DNS configured correctly, if the endpoint returns IPs that are not from your VPC CIDRs, double check the DNS configuration

* `nslookup <groundcover backend endpoint>`

Use netcat to test the security groups configured correctly, if you get timeout to the VPC endpoint double check the inboud rules on the VPC endpoint and the outbound rule on the workload security groups

* `nc -vz <groundcover backend endpoint> 443`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/collect-data/byoc/setup-byoc-with-aws/aws-privatelink-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.