Skip to content

Commit 844ae1d

Browse files
authored
Merge pull request #139 from tebanieo/master
Removing old references to C9 templates on game-player-data
2 parents a354340 + fc43748 commit 844ae1d

File tree

7 files changed

+37
-44
lines changed

7 files changed

+37
-44
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,4 @@ __pycache__/
66
build
77
.hugo_build.lock
88
preview_build
9+
.vscode/

content/game-player-data/setup/Step1.en.md

Lines changed: 10 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -7,37 +7,27 @@ chapter: false
77
description: "To get started, you configure your environment and download code that you use during the lab."
88
---
99

10+
During the first 60 seconds, the environment will automatically update extensions and plugins. Any startup notification can be safely dismissed.
11+
12+
![VS Code Setup](/static/images/common/common-vs-code-01.png)
1013

11-
[AWS Cloud9](https://aws.amazon.com/cloud9/) is a cloud-based integrated development environment (IDE) that lets you write, run, and debug code with just a browser. AWS Cloud9 includes a code editor, debugger, and terminal. It also comes prepackaged with essential tools for popular programming languages and the AWS Command Line Interface (CLI) preinstalled so that you don’t have to install files or configure your laptop for this lab. Your AWS Cloud9 environment will have access to the same AWS resources as the user with which you signed in to the AWS Management Console.
14+
If a terminal is not available at the bottom left side of your screen, please open a new one like the following picture indicates.
1215

13-
### To set up your AWS Cloud9 development environment:
16+
![VS Code Setup](/static/images/common/common-vs-code-02.png)
1417

15-
1. Choose **Services** at the top of the page, and then choose **Cloud9** under **Developer Tools**.
16-
17-
2. There would be an environment ready to use under **Your environments**.
18+
Then run the command `aws sts get-caller-identity` just to verify that your AWS credentials have been properly configured.
1819

19-
3. Click on **Open IDE**, your IDE should open with a welcome note.
20+
![VS Code Setup](/static/images/common/common-vs-code-03.png)
2021

21-
You should now see your AWS Cloud9 environment. You need to be familiar with the three areas of the AWS Cloud9 console shown in the following screenshot:
2222

23-
![Cloud9 Environment](/static/images/game-player-data/setup/cloud9-environment.png)
24-
25-
- **File explorer**: On the left side of the IDE, the file explorer shows a list of the files in your directory.
26-
27-
- **File editor**: On the upper right area of the IDE, the file editor is where you view and edit files that you’ve selected in the file explorer.
28-
29-
- **Terminal**: On the lower right area of the IDE, this is where you run commands to execute code samples.
30-
31-
32-
33-
In this lab, you use Python scripts to interact with the DynamoDB API. Run the following commands in your AWS Cloud9 terminal to download and unpack this lab’s code.
23+
In this lab, you use Python scripts to interact with the DynamoDB API. Run the following commands in your VS Code terminal to download and unpack this lab’s code.
3424

3525
```bash
36-
cd ~/environment
26+
cd ~/workshop/LGME
3727
curl -sL https://amazon-dynamodb-labs.com/assets/battle-royale.zip -o battle-royal.zip && unzip -oq battle-royal.zip && rm battle-royal.zip
3828
```
3929

40-
You should see two directories in the AWS Cloud9 file explorer:
30+
You should see two directories in the file explorer:
4131

4232
- **application**: The _application_ directory contains example code for reading and writing data in your table. This code is similar to code you would have in your real gaming application.
4333

content/game-player-data/setup/aws-ws-event.en.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,30 +7,29 @@ chapter: true
77

88
### Login to AWS Workshop Studio Portal
99

10-
1. If you are provided a one-click join link, skip to step 3.
10+
1. If you are provided a one-click join link, use it and skip to step 3.
1111

1212
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-
1413
![Workshop Studio Landing Page](/static/images/aws-ws-event1.png)
1514

1615
3. On the next, **Sign in** page, choose **Email One-Time Passcode (OTP)** to sign in to your workshop page.
17-
1816
![Sign in page](/static/images/aws-ws-event2.png)
1917

2018
4. Provide an email address to receive a one-time passcode.
21-
2219
![Email address input](/static/images/aws-ws-event3.png)
2320

2421
5. Enter the passcode that you received in the provided email address, and click **Sign in**.
2522

2623
6. Next, in the textbox, enter the event access code (eg: abcd-012345-ef) that you received from the event facilitators. If you are provided a one-click join link, you will be redirected to the next step automatically.
27-
2824
![Event access code](/static/images/aws-ws-event4.png)
2925

3026
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.
3127

3228
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.
29+
![Event dashboard](/static/images/common/workshop-studio-01.png)
30+
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`.
3332

34-
![Event dashboard](/static/images/aws-ws-event5.png)
33+
![Event dashboard](/static/images/common/workshop-studio-02.png)
3534

3635
9. Now that you are connected continue on to: :link[Step 1]{href="/game-player-data/setup/Step1"}.

content/game-player-data/setup/index.en.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,12 @@ In this module, you'll configure your environment and download code that you wil
2121

2222
To set up this workshop, choose one of the following paths, depending on whether you are:
2323

24-
::alert[If following the lab in your own AWS Account, you will create DynamoDB tables that will incur a cost that could approach tens of dollars per day. **Ensure you delete the DynamoDB tables using the DynamoDB console, and make sure you [delete the Cloud9 environment](https://docs.aws.amazon.com/cloud9/latest/user-guide/delete-environment.html) as soon as the lab is complete**.]{type="warning"}
24+
::alert[If following the lab in your own AWS Account, you will create DynamoDB tables that will incur a cost that could approach tens of dollars per day. **Ensure you delete the DynamoDB tables using the DynamoDB console, and make sure you [delete the Visual Studio Code instance](https://docs.aws.amazon.com/cloud9/latest/user-guide/delete-environment.html) as soon as the lab is complete**.]{type="warning"}
2525

26-
- :link[…running the workshop on your own (in your own AWS account)]{href="/game-player-data/setup/on-your-own"}, which guides you to launch a Cloud9 environment using CloudFormation
26+
- :link[…running the workshop on your own (in your own AWS account)]{href="/game-player-data/setup/on-your-own"}, which guides you to launch a Visual Studio Code instance using Cloud Formation.
2727

2828
- :link[…attending an AWS-hosted event (using AWS-provided access-code)]{href="/game-player-data/setup/aws-ws-event"}
2929

3030

3131
Once you have completed with either setup, continue on to:
32-
- :link[Step 1: Setup AWS Cloud9 IDE]{href="/game-player-data/setup/step1"}
32+
- :link[Step 1: Obtain and review code]{href="/game-player-data/setup/step1"}

content/game-player-data/setup/on-your-own.en.md

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,26 +5,29 @@ weight: 5
55
chapter: true
66
---
77

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"}
99

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="/game-player-data/setup/aws-ws-event"}]
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"}]
1111

1212
## Launch the CloudFormation stack
1313
::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.]
1414

15-
1. Launch the CloudFormation template in US West 2 to deploy the resources in your account: [![CloudFormation](/static/images/cloudformation-launch-stack.png)](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=DynamoDBID&templateURL=:param{key="design_patterns_s3_lab_yaml"})
16-
*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: [![CloudFormation](/static/images/cloudformation-launch-stack.png)](https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/new?stackName=DynamoDBID&templateURL=:param{key="design_patterns_s3_lab_yaml"})
1716

18-
2. Click *Next* on the first dialog.
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*
1918

20-
3. 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*
19+
1. Click *Next* on the first dialog.
2220

23-
![CloudFormation parameters](/static/images/awsconsole1.png)
21+
1. Provide a CloudFormation stack name.
2422

25-
4. 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*.
26-
27-
![Acknowledge IAM role capabilities](/static/images/awsconsole2.png)
28-
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.
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*.
2924

30-
5. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto connecting to Cloud9]{href="/game-player-data/setup/Step1"}.
25+
![CloudFormation parameters](/static/images/common/on-your-own-cf-01.png)
26+
27+
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*.
28+
29+
![CloudFormation parameters](/static/images/common/on-your-own-cf-02.png)
30+
31+
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.
32+
33+
5. After the CloudFormation stack is `CREATE_COMPLETE`, :link[continue onto connecting to VS Code]{href="/game-player-data/setup/Step1"}.

content/game-player-data/summary.en.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,4 +37,4 @@ Please take a few moments to share your feedback with us using the link that you
3737

3838
If you were running this lab in your own AWS Account (not an AWS run event), don't forget to cleanup the resources, by deleting the CloudFormation stack or the resources themselves (incase of no CloudFormation stack) you used during setup.
3939

40-
::alert[If following the lab in your own AWS Account, you will create 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 Cloud9 environment](https://docs.aws.amazon.com/cloud9/latest/user-guide/delete-environment.html) as soon as the lab is complete**.]{type="warning"}
40+
::alert[If following the lab in your own AWS Account, you will create 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 resources created via the [Cloud formation template](https://github.com/aws-samples/aws-dynamodb-examples/blob/master/workshops/modernizer/SELF_HOSTED_README.md#-cleanup-instructions) ]

content/hands-on-labs/index.en.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This workshop is designed for developers, engineers, and database administrators
1616

1717
### Requirements
1818
#### Basic knowledge of AWS services
19-
- Among other services this lab will guide you through the use of [AWS Cloud9](https://aws.amazon.com/cloud9/) and [AWS Lambda](https://aws.amazon.com/lambda/).
19+
- Among other services this lab will guide you through the use of Visual Studio Code and [AWS Lambda](https://aws.amazon.com/lambda/).
2020

2121
#### Basic understanding of DynamoDB
2222
- If you're not familiar with DynamoDB or are not participating in this lab as part of an AWS event, consider reviewing the documentation on "[What is Amazon DynamoDB?](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html)"

0 commit comments

Comments
 (0)