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/design-patterns/setup/Step1.en.md
+27-29Lines changed: 27 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,32 +4,30 @@ date: 2019-12-02T10:07:45-08:00
4
4
weight: 10
5
5
---
6
6
7
-
1. Once you've gained access to the AWS Management Console for the lab, double check the region is correct and the role name **WSParticipantRole** appears on the top right of the console.
8
-
1. In the services search bar, search for **Systems Manager** and click on it to open the AWS Systems Manager section of the AWS Management Console.
9
-
1. In the AWS Systems Manager console, locate the menu in the left, identify the section **Node Management** and select **Session Manager** from the list.
10
-
1. Choose **Start session** to launch a shell session.
11
-
1. Click the radio button to select the EC2 instance for the lab. If you see no instance, wait a few minutes and then click refresh. Wait until an ec2 instance with name of `DynamoDBC9` is available before continuing. Select the instance.
12
-
1. Click the **Start Session** button (This action will open a new tab in your browser with a new black shell).
13
-
1. In the new black shell, switch to the ubuntu account by running `sudo su - ubuntu`
14
-
```bash
15
-
sudo su - ubuntu
16
-
```
17
-
1. run `shopt login_shell` and be sure it says `login_shell on` and then change into the workshop directory.
18
-
```bash
19
-
#Verify login_shell is 'on'
20
-
shopt login_shell
21
-
#Change into the workshop directory
22
-
cd~/workshop/
23
-
```
24
-
25
-
26
-
The output of your commands in the Session Manager session should look like the following:
27
-
```bash
28
-
$ sudo su - ubuntu
29
-
:~ $ #Verify login_shell is 'on'
30
-
shopt login_shell
31
-
#Change into the workshop directory
32
-
cd~/workshop/
33
-
login_shell on
34
-
:~/workshop $
35
-
```
7
+
During the first 60 seconds, the environment will automatically update extensions and plugins. Any startup notification can be safely dismissed.
::alert[_Make sure you have AWS CLI version 2.x or higher and python 3.10 or higher before proceeding. If you do not have these versions, you may have difficultly successfully completing the lab._]
Copy file name to clipboardExpand all lines: content/design-patterns/setup/aws-ws-event.en.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Start: At an AWS Hosted Event"
3
3
date: 2019-12-02T07:05:12-08:00
4
-
weight: 3
4
+
weight: 4
5
5
chapter: true
6
6
---
7
7
@@ -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`.
Copy file name to clipboardExpand all lines: content/design-patterns/setup/user-account.en.md
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,25 +5,30 @@ weight: 5
5
5
chapter: true
6
6
---
7
7
8
-
::alert[These setup instructions are identitical for LADV, LHOL, LMR, LBED, 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"}
9
8
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="/design-patterns/setup/aws-ws-event"}]
9
+
::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"}
10
+
11
+
::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
12
12
13
## Launch the CloudFormation stack
13
14
::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
15
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*
16
+
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"})
17
+
18
+
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
19
18
20
1. Click *Next* on the first dialog.
19
21
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*.
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.
28
+
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*.
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.
28
33
29
-
1. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto Step 1]{href="/design-patterns/setup/Step1"}.
34
+
7. After the CloudFormation stack is `CREATE_COMPLETE`, :link[Launch Visual Studio Code]{href="/design-patterns/setup/step1"}.
Copy file name to clipboardExpand all lines: content/event-driven-architecture/setup/aws-ws-event.en.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,9 @@ chapter: true
7
7
8
8
### Login to AWS Workshop Studio Portal
9
9
10
-
1. If you are provided a one-click join link, skip to step 3.
10
+
### Login to AWS Workshop Studio Portal
11
+
12
+
1. If you are provided a one-click join link, use it and skip to step 3.
11
13
12
14
2. Visit [https://catalog.us-east-1.prod.workshops.aws](https://catalog.us-east-1.prod.workshops.aws). If you attended any other workshop earlier on this portal, please logout first. Click on **Get Started** on the right hand side of the window.
13
15
@@ -26,6 +28,10 @@ chapter: true
26
28
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
29
28
30
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. 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`.
Copy file name to clipboardExpand all lines: content/event-driven-architecture/setup/user-account.en.md
+18-7Lines changed: 18 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,30 @@ 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 Visual Studio Code template. Only complete this section once, and only if you're running it on your own account.]{type="warning"}
9
+
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"}]
8
11
9
-
::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="/event-driven-architecture/setup/start-here/aws-ws-event"}]
10
12
## Launch the CloudFormation stack
11
-
::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.]{type="warning"}
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
+
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"})
12
16
13
-
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=amazon-dynamodb-labs&templateURL=:param{key="event_driven_architecture_lab_yaml"})
14
-
1.*Optionally, download [the YAML template](:param{key="event_driven_architecture_lab_yaml"}) and launch it your own way*
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*
15
18
16
19
1. Click *Next* on the first dialog.
17
20
18
-
1. Scroll to the bottom and click *Next*, and then review the *Template*. 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 DynamoDB tables, Lambda functions, Kinesis streams, and IAM roles and policies which will be used later on in the lab.
21
+
1. Provide a CloudFormation stack name.
22
+
23
+
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*.
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.
21
32
22
33
1. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto the overview]{href="/event-driven-architecture/ex1overview"}.
0 commit comments