From 33296903ff3198275d285f5b142056699de9282c Mon Sep 17 00:00:00 2001 From: Jasha Sommer-Simpson <8935917+Jasha10@users.noreply.github.com> Date: Sat, 21 Dec 2024 23:03:02 -0500 Subject: [PATCH 1/2] Fix typos --- deployment/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deployment/overview.mdx b/deployment/overview.mdx index 6ddc875..4e256bb 100644 --- a/deployment/overview.mdx +++ b/deployment/overview.mdx @@ -29,7 +29,7 @@ See the [database configuration options](/configuration#database). 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, and local filesystem. For local testing, a filesystem that's3 +supports several storage backends, including S3, GCS, EBS, 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. From 1efa9b1b06fc3b4cce3b6d2c131fc92b203fc80c Mon Sep 17 00:00:00 2001 From: Jasha Sommer-Simpson <8935917+Jasha10@users.noreply.github.com> Date: Sat, 28 Dec 2024 00:29:14 -0600 Subject: [PATCH 2/2] Update overview.mdx --- deployment/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deployment/overview.mdx b/deployment/overview.mdx index 4e256bb..7a4d34f 100644 --- a/deployment/overview.mdx +++ b/deployment/overview.mdx @@ -29,7 +29,7 @@ See the [database configuration options](/configuration#database). 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, EBS, and local filesystem. For local testing, a filesystem that's +supports several storage backends, including S3, GCS, ABS, 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.