Skip to content

Commit 2259f20

Browse files
amckinleypracucci
andauthored
Update storage-aws.md (#2992)
* Update storage-aws.md Improve clarity around blocks vs chunks storage options. * fix Signed-off-by: Marco Pracucci <[email protected]> * Fixed white noise Signed-off-by: Marco Pracucci <[email protected]> Co-authored-by: Marco Pracucci <[email protected]>
1 parent d24c388 commit 2259f20

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/production/storage-aws.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,9 @@ if you use MFA), or use a short-term token solution such as
1818

1919
## Should I use S3 or DynamoDB ?
2020

21-
Note that the choices are: "chunks" of timeseries data in S3 and index
22-
in DynamoDB, or everything in DynamoDB. Using just S3 is not an option.
21+
Note that the choices for the chunks storage backend are: "chunks" of
22+
timeseries data in S3 and index in DynamoDB, or everything in DynamoDB.
23+
Using just S3 is not an option, unless you use the [blocks storage](../../blocks-storage/) engine.
2324

2425
Broadly S3 is much more expensive to read and write, while DynamoDB is
2526
much more expensive to store over months. S3 charges differently, so

0 commit comments

Comments
 (0)