AUDIT - LMR

# Workshop audit: LMR (Build and Deploy a Global Serverless Application with Amazon DynamoDB). Findings:

## Workshop Overview - broken module links

The top-level module links return 404 and must point to the `/global-serverless-application/` paths:
- [ ] [[Module 1](https://catalog.workshops.aws/dynamodb-labs/en-US/module_1/)](https://catalog.workshops.aws/dynamodb-labs/en-US/module_1/) → `https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/module_1`
- [ ] [[Module 2](https://catalog.workshops.aws/dynamodb-labs/en-US/module_2/)](https://catalog.workshops.aws/dynamodb-labs/en-US/module_2/) → `https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/module_2`
- [ ] [[Module 3](https://catalog.workshops.aws/dynamodb-labs/en-US/module_3/)](https://catalog.workshops.aws/dynamodb-labs/en-US/module_3/) → `https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/module_3`
- [ ] [[Global Tables Discussion Topics](https://catalog.workshops.aws/dynamodb-labs/en-US/gt_discussion/)](https://catalog.workshops.aws/dynamodb-labs/en-US/gt_discussion/) → `https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/gt-discussion`

---

## Getting Started

- [ ] Replace the Cloud9 deletion message in the **Summary** section with CloudFormation/VS Code equivalent. Current text:
> *If you are running this workshop in your own AWS account, you may delete the `DynamoDBID` CloudFormation Stack and the Chalice created components to avoid incurring any charges afterwards. The DynamoDB table was created in On Demand mode so there are no charges for provisioned capacity levels, only for actual usage. However there will be small charges for storage if the table is not cleaned up.*

- [ ] Rename link text [`[…running the workshop on your own (in your own AWS account)](https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/getting_started/on-your-own)`](https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/getting_started/on-your-own) → **Start: On your own** (match the menu)

- [ ] Replace text *"which guides you to launch a Cloud9 environment using CloudFormation"* with the VS Code equivalent

- [ ] Rename link text [`[…attending an AWS-hosted event (using AWS-provided access-code)](https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/getting_started/aws-ws-event)`](https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/getting_started/aws-ws-event) → **Start: At an AWS Hosted Event** (match the menu)

---

## Start: On your own

- [ ] [`[At an AWS hosted Event](https://catalog.workshops.aws/dynamodb-labs/en-US/hands-on-labs/setup/aws-ws-event)`](https://catalog.workshops.aws/dynamodb-labs/en-US/hands-on-labs/setup/aws-ws-event) link → should point to `https://catalog.workshops.aws/dynamodb-labs/en-US/global-serverless-application/getting-started/aws-ws-event`

---

## Start: At an AWS Hosted Event

- [ ] Steps 8 and 9: update output key naming:
- `VSCodeServerPassword` → `VSCodePassword`
- `VSCodeServerURL` → `VSCodeUrl`

---

## Module 1: Deploy the backend resources

- [ ] Update key naming in screenshot to match the renames below

- [ ] Update all mentions of `VSCodeServerURL` → `VSCodeUrl`, and `VSCodeServerPassword` → `VSCodePassword`

- [ ] Update screenshot — ARN shown still has a `c9` reference, but the actual ARN does not

- [ ] `pip install chalice` fails with a `boto3` not-found error, despite the page noting *"Your VS Code environment is already configured with boto3…"*. Running `pip install boto3` resolves it. Either add this step explicitly or ensure `boto3` is pre-installed in the VS Code environment.

---

## Global Tables Discussion Topics

- [ ] Link for *"How would I upgrade from Global Tables v1 to v2"* → should be `https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_versions.html#upgrading-to-current-version`

Start by opening the workshop pages linked in the checklist and verify each navigation link, wording change, output key, screenshot, and boto3 installation instruction against the stated findings. Done means all broken links and names are corrected, screenshots match, setup guidance reflects VS Code, and the Global Tables reference uses the specified AWS documentation URL.

Written by the indexing model from the issue text.