LHOL New AWS console theme, fixed guide, mentioned c9 instance (#88)

Author: switch180

content/hands-on-labs/backups/on-demand-backup.md

@@ -18,9 +18,7 @@ table performance or availability.
 
 ![OD Backup 1](/images/hands-on-labs/backup/od_backup_1.png)
 
-2.  Make sure that ProductCatalog is the source table name. Enter
-    ProductCatalogBackup for the backup name. Choose **Create backup** to
-    create the backup.
+2.  Make sure that ProductCatalog is the source table name. Choose **Customize settings** and then select **Backup with DynamoDB**. Enter the name `ProductCatalogBackup`. Click **Create backup** to create the backup.
 
 ![OD Backup 2](/images/hands-on-labs/backup/od_backup_2.png)
 
@@ -36,19 +34,19 @@ While the backup is being created, the backup status is set to
 
 ![OD Backup 3](/images/hands-on-labs/backup/od_backup_3.png)
 
-2.  Enter ProductCatalogODRestore as the new table name. Confirm the
+2.  Enter `ProductCatalogODRestore` as the new table name. Confirm the
     backup name and other backup details. Choose **Restore**
     to start the restore process. The table that is being restored is
     shown with the status **Creating**. After the restore process is
-    finished, the status of the ProductCatalogODRestore table changes to
+    finished, the status of the `ProductCatalogODRestore` table changes to
     **Active**.
 
 ![OD Backup 4](/images/hands-on-labs/backup/od_backup_4.png)
 
 ### To delete a backup
 
 The following procedure shows how to use the console to delete the
-ProductCatalogBackup
+ProductCatalogBackup. You can only delete the backup after the table `ProductCatalogODRestore` is done restoring.
 
 1.  Go to the [DynamoDB Console](https://console.aws.amazon.com/dynamodbv2/) and click on *Tables* from the side menu
 1. Choose ProductCatalog table.

content/hands-on-labs/backups/schedule-backup.md

@@ -66,13 +66,11 @@ Now assign the resource to backup plan. When you assign a resource to a
 backup plan, that resource is backed up automatically according to the
 backup plan.
 
-7.  Click on **Assign resources** under **Backup plans**.
+7. Give Resource a assignment name. Choose the default role. Select **Include specific resource types** under "1. Define resource selection"
 
 ![Scheduled Backup 8](/images/hands-on-labs/backup/sched_backup_8.png)
 
-8.  Give Resource assignment name. Choose default IAM role. Choose our
-    DynamoDB table in the assign resources section. Click on **Assign
-    resources**.
+8.   Under "2. Select specific resource types" select the resource type **DynamoDB** in the drop down. Click choose resources, uncheck All, and select the **ProductCatalog** table. Click **Assign resources**
 
 ![Scheduled Backup 9](/images/hands-on-labs/backup/sched_backup_9.png)
 
@@ -93,11 +91,11 @@ protected and is available to be restored using AWS Backup.
 
 ![Scheduled Backup 11](/images/hands-on-labs/backup/sched_backup_11.png)
 
-2.  Choose the recovery point ID of the resource. Click on **Restore**.
+2.  Choose the recovery point ID of the resource. Click on **Restore**. _Note: If you do not see a recovery point, you can click "Create an on-demand backup" and complete the backup. For the purposes of this lab, you need a completed backup to continue, and you may not want to wait for your backup plan's scheduled backup._
 
 ![Scheduled Backup 12](/images/hands-on-labs/backup/sched_backup_12.png)
 
-3.  Provide new DynamoDB table name. Choose default role and click on
+3.  Provide new DynamoDB table name. Leave all the settings on the defaults and click
     **Restore backup**
 
 ![Scheduled Backup 13](/images/hands-on-labs/backup/sched_backup_13.png)

content/hands-on-labs/explore-cli/cli-gsi.en.md

@@ -55,10 +55,13 @@ aws dynamodb update-table \
 It can take a little time while DynamoDB creates the GSI and backfills data from the table into the index.  We can watch this from the command line and wait until the IndexStatus goes `ACTIVE`:
 
 ```bash
-aws dynamodb describe-table --table-name Reply | grep IndexStatus
+#Get initial status
+aws dynamodb describe-table --table-name Reply --query "Table.GlobalSecondaryIndexes[0].IndexStatus"
+#Watch the status with the wait command (use Ctrl+C to exit):
+watch -n 5 "aws dynamodb describe-table --table-name Reply --query "Table.GlobalSecondaryIndexes[0].IndexStatus""
 ```
 
-Once the GSI has become `ACTIVE`, continue on to the exercise below.
+Once the GSI has become `ACTIVE`, continue on to the exercise below. Use `Ctrl+C` to exit the watch command.
 
 ## Exercise
 

content/hands-on-labs/explore-cli/cli-scan.en.md

@@ -22,7 +22,7 @@ aws dynamodb scan \
 
 Note than in the response we see these lines:
 
-```json
+```
 "Count": 3,
 "ScannedCount": 4,
 ```
@@ -129,7 +129,7 @@ aws dynamodb scan \
 
 When you run this command you receive the following error:
 
-```
+```text
 An error occurred (ValidationException) when calling the Scan operation: Invalid FilterExpression: Attribute name is a reserved keyword; reserved keyword: Views
 ```
 

content/hands-on-labs/explore-console/console-read-data.en.md

@@ -8,7 +8,7 @@ First, go to the [DynamoDB Console](https://console.aws.amazon.com/dynamodbv2/)
 
 ![Console Pick Tables](/images/hands-on-labs/explore-console/dynamodb_pick_tables.png)
 
-Next, choose the ProductCatalog table and scroll down to see the Items preview pane.
+Next, choose the `ProductCatalog` table and scroll down to see the Items preview pane.
 
 ![Console ProductCatalog Items Preview](/images/hands-on-labs/explore-console/console_productcatalog_preview.png)
 

content/hands-on-labs/explore-console/console-read-item-collection.en.md

@@ -33,7 +33,7 @@ We can see that there are two Reply items in the `DynamoDB Thread 1` thread.
 
 ![Item Explorer Query Reply 1](/images/hands-on-labs/explore-console/console_item_explorer_query_reply_1.png)
 
-Since the Sort Key in this table is a timestamp, we could specify a Key Condition Expression to return only the replies in a thread that were posted after a certain time by adding a sort key condition where ReplyDateTime is More than `2015-09-21` and clicking **Run**.
+Since the Sort Key in this table is a timestamp, we could specify a Key Condition Expression to return only the replies in a thread that were posted after a certain time by adding a sort key condition where `ReplyDateTime` is More than `2015-09-21` and clicking **Run**.
 
 ![Item Explorer Query Reply 2](/images/hands-on-labs/explore-console/console_item_explorer_query_reply_2.png)
 

content/hands-on-labs/explore-console/console-writing-data.en.md

@@ -12,7 +12,7 @@ Let's say we wanted to insert a new item into the *Reply* table from the console
 
 ![Console Create Item 1](/images/hands-on-labs/explore-console/console_create_item_1.png)
 
-You will need to click **Add new attribute** a couple of times to make some new String attributes, and then fill in the following data, then click **Create Item**.
+Click ` JSON view`, ensure `View DynamoDB JSON` is deselected, and paste the following attributes, and then click **Create Item** to insert the new item.
 
 ```text
         "Id" : "Amazon DynamoDB#DynamoDB Thread 2",

content/hands-on-labs/rdbms-migration/migration-chapter05.en.md

@@ -35,7 +35,7 @@ _Make sure the DMS instance is Available before you continue. If it is not Avail
     | Password            |                                            Value of DbMasterPassword added as parameter during Configure MySQL Environment                                            |
 
     ![Final Deployment Architecture](/images/migration22.jpg)
-    Open Test endpoint connection (optional) section, then in the VPC drop-down select DMS-VPC and click the Run test button to verify that your endpoint configuration is valid. The test will run for a minute and you should see a successful message in the Status column. Click on the Create endpoint button to create the endpoint.
+    Open Test endpoint connection (optional) section, then in the VPC drop-down select DMS-VPC and click the Run test button to verify that your endpoint configuration is valid. The test will run for a minute and you should see a successful message in the Status column. Click on the Create endpoint button to create the endpoint. If you see a connection error, re-type the username and password to ensure no mistakes were made. Further, ensure you provided the IPv4 DNS name ending in amazonaws.com in the field **Server name**.
     ![Final Deployment Architecture](/images/migration23.jpg)
 
 3.  Create the target endpoint. Repeat all steps to create the target endpoint with the following parameter values:
@@ -45,7 +45,7 @@ _Make sure the DMS instance is Available before you continue. If it is not Avail
     | Endpoint type           |                                                                                       Target endpoint                                                                                       |
     | Endpoint identifier     |                                                                                      dynamodb-endpoint                                                                                      |
     | Target engine           |                                                                                       Amazon DynamoDB                                                                                       |
-    | Service access role ARN | CloudFormation template has created new role with full access to Amazon DynamoDB. Copy Role ARN from [dynamodb-access](https://console.aws.amazon.com/iam/home#/roles/dynamodb-access) role |
+    | Service access role ARN | CloudFormation template has created new role with full access to Amazon DynamoDB. Copy Role ARN from [dynamodb-access](https://us-east-1.console.aws.amazon.com/iamv2/home#/roles/details/dynamodb-access?section=permissions) role |
 
     ![Final Deployment Architecture](/images/migration24.jpg)
     Open Test endpoint connection (optional) section, then in the VPC drop-down select DMS-VPC and click the Run test button to verify that your endpoint configuration is valid. The test will run for a minute and you should see a successful message in the Status column. Click on the Create endpoint button to create the endpoint.
@@ -65,7 +65,7 @@ Still in the AWS DMS console, go to Database migration tasks and click the Creat
    | Migration type                               |                             Migrate existing data                             |
    | Task settings: Editing mode                  |                                    Wizard                                     |
    | Task settings: Target table preparation mode |                                  Do nothing                                   |
-   | Task settings: Enable CloudWatch logs        |                                    Checked                                    |
+   | Task settings: Turn on CloudWatch logs       |                                    Checked                                    |
    | Table mappings: Editing mode                 | Select JSON editor option and follow the instructions after below screenshots |
 
 ![Final Deployment Architecture](/images/migration25.jpg)
@@ -369,14 +369,20 @@ Replace the string "REPLACE THIS STRING BY MOVIES LIST" with list of movies copi
 -   [Third Task - historical-migration03](/files/hands-on-labs/Task_3.json)
 {{% /expand%}}
 
-### Monitor the tasks
+### Monitor and the restart/resume the tasks
 The replication task for historical migration will start moving data from MySQL imdb.movies view, title_akas and title_ratings to DynamoDB table will start in a few minutes.
-If you are loading selective records based on the list above, it may take 5-10 minutes to complete all three tasks. For full loading below are the statistics.
+If you are loading selective records based on the list above, it may take 5-10 minutes to complete all three tasks.
 
+If you were to run this exercise again but do a full load, the load times would be as follows:
 - historical-migration01 task will migrate 800K+ records and normally takes 2-3 Hrs.
 - historical-migration02 task will migrate 747K+ records and normally takes 2-3 Hrs.
-- historical-migration03 task will migrate 79K+ records and normally takes 10-15 Minutes.
-  You can track the status of data loading under the Table statistics of the migration task. Once loading is in progress, feel free to move to the next section of the exercise.
+- historical-migration03 task will migrate 79K+ records and normally takes 10-15 Minutes.  
+
+
+You can track the status of data loading under the Table statistics of the migration task. Once loading is in progress, feel free to move to the next section of the exercise.
   ![Final Deployment Architecture](/images/migration27.jpg)
 
+{{% notice warning %}}
+_Make sure all tasks are running or complete before you continue. If a task says **Ready**, check its box and choose "Restart/Resume" under the Actions button to start the task._
+{{% /notice %}}
 

content/hands-on-labs/setup/prerequisites.en.md

@@ -15,7 +15,7 @@ You can use your own account, or an account provided through Event Engine as par
 
 #### Using an account provided through Event Engine
 
-If you are running this workshop as part of an Event Engine lab, please log into the console using [this link](https://dashboard.eventengine.run/) and enter the hash provided to you as part of the workshop.
+If you are running this workshop as part of an Event Engine lab, please log into the console using [this link](https://dashboard.eventengine.run/) and enter the hash provided to you as part of the workshop. In event engine, the Cloud9 instance should be made in your account. Please open the "AWS Cloud9" section of the AWS Management Console in the correct region and look for a lab instance called "DynamoDBC9". 
 
 #### Using your own AWS account
 

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

@@ -5,6 +5,9 @@ date = 2021-04-21T07:39:31-05:00
 weight = 12
 +++
 
+{{% notice note %}}
+_These instructions are for users running the lab in their own AWS account. If you are part of a workshop, check the AWS Cloud9 console in the correct region for a running environment named "DynamoDBC9" before you follow these instructions. You may not need to launch the template._
+{{% /notice %}}
 
 Download this [Cloud Formation Template](/files/hands-on-labs/dynamodb-labs-vpc.yaml) to your local machine.