thomasabishop/eolas
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Autosave: 2024-06-23 17:30:04

Browse source
This commit is contained in:
thomasabishop 2024-06-23 17:30:04 +01:00
parent 97735f1070
commit c958975b6a
3 changed files with 29 additions and 54 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
.zk/notebook.db
View file

Binary file not shown.

46
zk/DynamoDB CLI commands.md
View file

@ -1,46 +0,0 @@
---
id: l045
title: DynamoDB CLI commands
tags: [AWS, databases, dynamodb]
created: Saturday, June 22, 2024
---
# DynamoDB CLI commands
## Connecting to a local (Docker)/prod (AWS) DynamoDB instance
In order to distinguish between local and production accounts you should keep
seperate profiles for each (via `.aws/config` and `.aws/credentials`).
When connecting to a local DB use the local profile and the local URL. Without
the `--profile` flag, AWS will default to the `default` profile which will
typically be your credentials for accessing AWS on the remote.
For example:
```sh
aws dynamodb list-tables \
--profile timetracking_dev \
--endpoint-url http://localhost:800
```
## Delete a table
```sh
aws dynamodb delete-table \
--profile timetracking_dev \
--endpoint-url http://localhost:8000 \
--table-name TableName
```
## Create table from JSON schema
```sh
aws dynamodb create-table \
--cli-input-json file://create-timeentries-table.json \
--profile timetracking_dev \
--endpoint-url http://localhost:8000
```
## Related notes

37
zk/DynamoDB_CLI_commands.md
View file

@ -7,19 +7,40 @@ created: Saturday, June 22, 2024
# DynamoDB CLI commands
## Connecting to a local (Docker) DynamoDB instance
## Connecting to a local (Docker)/prod (AWS) DynamoDB instance
In order to distinguish between local and production accounts you should keep
seperate configs in `.aws/config` and `.aws/credentials`. Then specify the
profile if you are working locally and the local URL. Without the `--profile`
flag, AWS will default to the `default` profile which will typically be your
credentials for accessing AWS on the remote.
seperate profiles for each (via `.aws/config` and `.aws/credentials`).
When connecting to a local DB use the local profile and the local URL. Without
the `--profile` flag, AWS will default to the `default` profile which will
typically be your credentials for accessing AWS on the remote.
For example:
```sh
aws dynamodb list-tables --profile timetracking_dev --endpoint-url
http://localhost:800
aws dynamodb list-tables \
--profile timetracking_dev \
--endpoint-url http://localhost:800
```
http://localhost:8000
## Delete a table
```sh
aws dynamodb delete-table \
--profile timetracking_dev \
--endpoint-url http://localhost:8000 \
--table-name TableName
```
## Create table from JSON schema
```sh
aws dynamodb create-table \
--cli-input-json file://create-timeentries-table.json \
--profile timetracking_dev \
--endpoint-url http://localhost:8000
```
## Related notes