> For the complete documentation index, see [llms.txt](https://docs.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthly.dev/earthly-cloud/satellites/byoc/aws/requirements.md).

# Requirements

This page documents the requirements to install [BYOC Satellites](/earthly-cloud/satellites/byoc.md) in AWS. Additional requirements may apply depending on your chosen installation method.

## Networking

Because every configuration is different, using BYOC within your organization will require you to configure your networking to match your use case. You'll need to ensure that:

* Traffic from Earthly clients, including CI build runners and developer workstations, can reach the satellites directly.
* Traffic to any required resources (e.g. private repositories, the internet, etc) are allowed.
* Internal AWS DNS names (or IP addresses) must resolve to an address reachable on the network.

These can all be accomplished with most VPN technologies. We recommend and have direct experience with [Tailscale](/earthly-cloud/satellites/byoc/vpn/tailscale.md). If you need help configuring other networking scenarios, [please reach out to us](https://earthly.dev/slack)!

## Cloud

Configuring BYOC in your AWS account requires:

* A VPC,
* and a chosen subnet that Earthly will place its satellites into. *Take note of the CIDR block, you may need it later.*

Right now, BYOC is only supported in the `us-west-2` (Oregon) region.

## On Your Machine

You'll need to finish the installation at the command line. To do this, ensure that [Earthly](https://earthly.dev/get-earthly) is installed on your system.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.earthly.dev/earthly-cloud/satellites/byoc/aws/requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.