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
Copy file name to clipboardExpand all lines: content/authors.en.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,15 @@ weight: 100
13
13
1. Sean Shriver ([switch180](https://github.com/switch180)) - Ported the whole lab to amazon-dynamodb-labs.com with a custom Hugo theme. Made the "bullet-proof" CloudFormation template for the lab. Updated the hands on lab to Python3
14
14
1. Daniel Yoder ([danielsyoder](https://github.com/danielsyoder)) - The brains behind amazon-dynamodb-labs.com and the co-creator of the design scenarios
15
15
16
+
### 2025 additions
17
+
Removing Cloud9 due to End of Life from all the workshops (October 2025):
18
+
1. Esteban Serna ([@tebanieo](https://github.com/tebanieo)) - Primary author, and merger
19
+
20
+
Database modernizer workshop was released in August 2025:
21
+
1. Esteban Serna ([@tebanieo](https://github.com/tebanieo)) - Primary author, and merger
22
+
2. John Terhune - ([@terhunej](https://github.com/terhunej)) - Editor, tech reviewer.
23
+
3. Sean Shriver - ([@switch180](https://github.com/switch180)) - Tech reviewer
24
+
16
25
### 2024 additions
17
26
The Generative AI workshop LBED was released in early 2024:
18
27
1. John Terhune - ([@terhunej](https://github.com/terhunej)) - Primary author
Copy file name to clipboardExpand all lines: content/hands-on-labs/explore-cli/index.en.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ weight: 20
5
5
chapter: true
6
6
---
7
7
8
-
We will be exploring DynamoDB with the AWS CLI using the [AWS cloud9 management Console](https://console.aws.amazon.com/cloud9/home). If you haven't already, choose *open IDE* to launch AWS Cloud9 environment. You can close the Welcome screen and adjust your terminal to increase screen area, or close all the windows and navigate to *Window* -> *New Terminal* to open a new terminal window.
8
+
We will be exploring the Amazon DynamoDB tables using the AWS CLI with the platform we have set up during the :link[environment setup]{href="/hands-on-labs/setup/create-tables"}.
9
9
10
10
The highest level of abstraction in DynamoDB is a *Table* (there isn't a concept of a "Database" that has a bunch of tables inside of it like in other NOSQL or RDBMS services). Inside of a Table you will insert *Items*, which are analogous to what you might think of as a row in other services. Items are a collection of *Attributes*, which are analogous to columns. Every item must have a *Primary Key* which will uniquely identify that row (two items may not contain the same Primary Key). At a minimum when you create a table you must choose an attribute to be the *Partition Key* (aka the Hash Key) and you can optionally specify another attribute to be the *Sort Key*.
Copy file name to clipboardExpand all lines: content/hands-on-labs/index.en.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,3 +24,4 @@ This workshop is designed for developers, engineers, and database administrators
24
24
### Recommended study before taking the lab
25
25
26
26
If you're not part of an AWS event and you haven't recently reviewed DynamoDB design concepts, we suggest you watch this video on [Advanced Design Patterns for DynamoDB](:param{key="latest_rh_design_pattern_yt"}), which is about an hour in duration.
Copy file name to clipboardExpand all lines: content/hands-on-labs/setup/aws-ws-event.en.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,10 @@ chapter: true
26
26
7. Select on **I agree with the Terms and Conditions** on the bottom of the next page and click **Join event** to continue to the event dashboard.
27
27
28
28
8. On the event dashboard, click on **Open AWS console** to federate into AWS Management Console in a new tab. On the same page, click **Get started** to open the workshop instructions.
9. Now that you are connected continue on to: :link[Step 1]{href="/design-patterns/setup/Step1"}.
31
+
9. In addition to the AWS console you should open your Visual Studio code server, by clicking in the `VSCodeServerURL` parameter, available from the "Event Outputs" section. When prompted for a password use the value from `VSCodeServerPassword`.
To run this lab, you'll need an AWS account, and a user identity with access to the following services:
18
+
19
+
* Amazon DynamoDB
20
+
* Visual Studio Code Web Environment
21
+
22
+
You can use your own account, or an account provided through Workshop Studio Event Delivery as part of an AWS organized workshop. Using an account provided by Workshop Studio is the easier path, as you will have full access to all AWS services, and the account will terminate automatically when the event is over.
23
+
24
+
### Account setup
25
+
26
+
#### Using an account provided to you by your lab instructor
27
+
28
+
If you are running this workshop using a link provided to you by your AWS instructor, please use that link and enter the access-code provided to you as part of the workshop. In the lab AWS account, the Visual Studio Code instance should already be provisioned. This should be available at the "Event Output" section in your Workshop studio URL.
Copy file name to clipboardExpand all lines: content/hands-on-labs/setup/setup.en.md
+15-10Lines changed: 15 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,24 +5,29 @@ weight: 5
5
5
chapter: true
6
6
---
7
7
8
-
::alert[These setup instructions are identitical for LADV, LHOL, LBED, LMR, and LGME - all of which use the same Cloud9 template. Only complete this section once, and only if you're running it on your own account.]{type="warning"}
8
+
::alert[These setup instructions are identitical for LADV, LHOL, LBED, LMR, and LGME - all of which use the same Visual Studio Code template. Only complete this section once, and only if you're running it on your own account.]{type="warning"}
9
9
10
10
::alert[Only complete this section if you are running the workshop on your own. If you are at an AWS hosted event (such as re\:Invent, Immersion Day, etc), go to :link[At an AWS hosted Event]{href="/hands-on-labs/setup/aws-ws-event"}]
11
11
12
12
## Launch the CloudFormation stack
13
13
::alert[During the course of the lab, you will make DynamoDB tables that will incur a cost that could approach tens or hundreds of dollars per day. Ensure you delete the DynamoDB tables using the DynamoDB console, and make sure you delete the CloudFormation stack as soon as the lab is complete.]
14
14
15
-
1. Launch the CloudFormation template in US West 2 to deploy the resources in your account: [](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=DynamoDBID&templateURL=:param{key="design_patterns_s3_lab_yaml"})
16
-
1.*Optionally, download [the YAML template](:param{key="design_patterns_s3_lab_yaml"}) and launch it your own way*
15
+
1.**[Deprecated]** - Launch the CloudFormation template in US West 2 to deploy the resources in your account: [](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=DynamoDBID&templateURL=:param{key="design_patterns_s3_lab_yaml"})
16
+
17
+
1.*Optionally, download [the YAML template](https://github.com/aws-samples/aws-dynamodb-examples/blob/master/workshops/modernizer/modernizer-db.yaml) from our GitHub repository and launch it your own way*
17
18
18
19
1. Click *Next* on the first dialog.
19
20
20
-
1. In the Parameters section, note the *Timeout* is set to zero. This means the Cloud9 instance will not sleep; you may want to change this manually to a value such as 60 to protect against unexpected charges if you forget to delete the stack at the end.
21
-
Leave the *WorkshopZIP* parameter unchanged and click *Next*
1. In the Parameters section, note the *AllowedIP** contains a default IP Address, if you want to access the instance via SSH obtain your own public IP address. Ensure to add the `/32` network mask at the end. Do not modify any other parameter and click *Next*.
6. Scroll to the bottom and click *Next*, and then review the *Template* and *Parameters*. When you are ready to create the stack, scroll to the bottom, check the box acknowledging the creation of IAM resources, and click *Create stack*.
23
28
24
-
1. Scroll to the bottom and click *Next*, and then review the *Template* and *Parameters*. When you are ready to create the stack, scroll to the bottom, check the box acknowledging the creation of IAM resources, and click *Create stack*.
The stack will create a Cloud9 lab instance, a role for the instance, and a role for the AWS Lambda function used later on in the lab. It will use Systems Manager to configure the Cloud9 instance.
The stack will create a Visual Studio Code EC2 instance, a role for the instance, and a role for the AWS Lambda function used later on in the lab. The CloudFormation template will create a set of folders that can be used to execute individually the lab modules presented in this guide.
27
32
28
-
1. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto Prerequisites]{href="/hands-on-labs/setup/prerequisites"}.
33
+
7. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto launching your IDE]{href="/hands-on-labs/setup/vscode"}.
0 commit comments