Skip to content

Update storage-aws.md #2992

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

Merged
merged 3 commits into from
Sep 15, 2020
Merged

Update storage-aws.md #2992

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d3fe5c
Update storage-aws.md
amckinley Aug 6, 2020
46ee9ba
fix
pracucci Sep 15, 2020
2217899
Fixed white noise
pracucci Sep 15, 2020
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
5 changes: 3 additions & 2 deletions docs/production/storage-aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +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 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 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
much more expensive to store over months. S3 charges differently, so
Expand Down