You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating table with streams enabled
9
+
10
+
The script handles this step automatically. See `dynamodb-streams.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Writing items to trigger stream events
13
+
14
+
The script handles this step automatically. See `dynamodb-streams.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Reading stream records
17
+
18
+
The script handles this step automatically. See `dynamodb-streams.sh` for the exact CLI commands.
19
+
20
+
## Cleanup
21
+
22
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating table
9
+
10
+
The script handles this step automatically. See `dynamodb-global-tables.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Enabling point-in-time recovery
13
+
14
+
The script handles this step automatically. See `dynamodb-global-tables.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Describing continuous backups
17
+
18
+
The script handles this step automatically. See `dynamodb-global-tables.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Writing and reading items
21
+
22
+
The script handles this step automatically. See `dynamodb-global-tables.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Table details
25
+
26
+
The script handles this step automatically. See `dynamodb-global-tables.sh` for the exact CLI commands.
27
+
28
+
## Cleanup
29
+
30
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating table with GSI
9
+
10
+
The script handles this step automatically. See `dynamodb-queries.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Writing items
13
+
14
+
The script handles this step automatically. See `dynamodb-queries.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Query by partition key
17
+
18
+
The script handles this step automatically. See `dynamodb-queries.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Query GSI (active users)
21
+
22
+
The script handles this step automatically. See `dynamodb-queries.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Scan with filter
25
+
26
+
The script handles this step automatically. See `dynamodb-queries.sh` for the exact CLI commands.
27
+
28
+
## Cleanup
29
+
30
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating table
9
+
10
+
The script handles this step automatically. See `dynamodb-ttl.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Enabling TTL
13
+
14
+
The script handles this step automatically. See `dynamodb-ttl.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Writing items with TTL
17
+
18
+
The script handles this step automatically. See `dynamodb-ttl.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Describing TTL
21
+
22
+
The script handles this step automatically. See `dynamodb-ttl.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Scanning items
25
+
26
+
The script handles this step automatically. See `dynamodb-ttl.sh` for the exact CLI commands.
27
+
28
+
## Cleanup
29
+
30
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
0 commit comments