Skip to content

Fix typos #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Jasha10 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix typos #103

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3329690
Fix typos
Jasha10 Dec 22, 2024
1efa9b1
Update overview.mdx
Jasha10 Dec 28, 2024
a7559e9
Merge branch 'main' into patch-1
mwylde Dec 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions deployment/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,12 @@ See the [database configuration options](/configuration#database).

### Storage

You will need a place to store pipeline artifacts (binaries) and checkpoint
data. This needs to be accessible to all nodes in your cluster, including
Arroyo the control plane and pipeline workers. Arroyo supports several storage
backends, including S3 and S3-compatible object stores, R2, GCS, ABS, and local
filesystem. For local testing, a filesystem that's3 mounted on all nodes is
sufficient, but for production you will likely want to use an object store like
S3 or GCS. We also support S3-compatible object stores like MinIO and
Localstack; endpoints can be set via the `s3::` prefix or the
`AWS_ENDPOINT_URL` environment variable.
You will need a place to store pipeline artifacts (binaries) and checkpoint data. This needs to be accessible to
all nodes in your cluster, including Arroyo the control plane and pipeline workers. Arroyo
supports several storage backends, including S3, GCS, ABS (Azure Block Storage), and local filesystem. For local testing, a filesystem that's
mounted on all nodes is sufficient, but for production you will likely want to use an object store like S3 or GCS.
We also support S3-compatible object stores like MinIO and Localstack; endpoints can be set via the `s3::` prefix
or the `AWS_ENDPOINT_URL` environment variable.

The storage backend is configured by the following [config properties](/configuration):

Expand Down