From 1d3fe5c560a12417668206c631086a890c285327 Mon Sep 17 00:00:00 2001 From: Austin McKinley <54160+amckinley@users.noreply.github.com> Date: Thu, 6 Aug 2020 16:45:45 -0700 Subject: [PATCH 1/3] Update storage-aws.md Improve clarity around blocks vs chunks storage options. --- docs/production/storage-aws.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/production/storage-aws.md b/docs/production/storage-aws.md index 84f39828419..d7625f5e9e8 100644 --- a/docs/production/storage-aws.md +++ b/docs/production/storage-aws.md @@ -18,8 +18,10 @@ if you use MFA), or use a short-term token solution such as ## Should I use S3 or DynamoDB ? -Note that the choices are: "chunks" of timeseries data in S3 and index -in DynamoDB, or everything in DynamoDB. Using just S3 is not an option. +Note that the choices for the chunks stoage backend are: "chunks" of +timeseries data in S3 and index in DynamoDB, or everything in DynamoDB. +Using just S3 is not an option, unless you use the experimental "blocks" +storage engine. Broadly S3 is much more expensive to read and write, while DynamoDB is much more expensive to store over months. S3 charges differently, so From 46ee9ba6a1c25d45ab89cd1808a0452dc284ae7f Mon Sep 17 00:00:00 2001 From: Marco Pracucci Date: Tue, 15 Sep 2020 16:34:03 +0200 Subject: [PATCH 2/3] fix Signed-off-by: Marco Pracucci --- docs/production/storage-aws.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/production/storage-aws.md b/docs/production/storage-aws.md index d7625f5e9e8..23cb4333e91 100644 --- a/docs/production/storage-aws.md +++ b/docs/production/storage-aws.md @@ -18,10 +18,9 @@ if you use MFA), or use a short-term token solution such as ## Should I use S3 or DynamoDB ? -Note that the choices for the chunks stoage backend are: "chunks" of +Note that the choices for the chunks storage backend are: "chunks" of timeseries data in S3 and index in DynamoDB, or everything in DynamoDB. -Using just S3 is not an option, unless you use the experimental "blocks" -storage engine. +Using just S3 is not an option, unless you use the [blocks storage](../../blocks-storage/) engine. Broadly S3 is much more expensive to read and write, while DynamoDB is much more expensive to store over months. S3 charges differently, so From 2217899f4df110cda7db96b82386c8dca10bcb65 Mon Sep 17 00:00:00 2001 From: Marco Pracucci Date: Tue, 15 Sep 2020 16:35:02 +0200 Subject: [PATCH 3/3] Fixed white noise Signed-off-by: Marco Pracucci --- docs/production/storage-aws.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/production/storage-aws.md b/docs/production/storage-aws.md index 23cb4333e91..cd1707a5f72 100644 --- a/docs/production/storage-aws.md +++ b/docs/production/storage-aws.md @@ -18,8 +18,8 @@ if you use MFA), or use a short-term token solution such as ## Should I use S3 or DynamoDB ? -Note that the choices for the chunks storage backend are: "chunks" of -timeseries data in S3 and index in DynamoDB, or everything in DynamoDB. +Note that the choices for the chunks storage backend are: "chunks" of +timeseries data in S3 and index in DynamoDB, or everything in DynamoDB. Using just S3 is not an option, unless you use the [blocks storage](../../blocks-storage/) engine. Broadly S3 is much more expensive to read and write, while DynamoDB is