Skip to content

Commit c3ea122

Browse files
committed
fixing weird merge issue
1 parent 918414a commit c3ea122

File tree

6 files changed

+4
-7
lines changed

6 files changed

+4
-7
lines changed

content/relational-migration/application refactoring/index2.en.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,4 +29,4 @@ open a different browser and navigate to the web app:
2929
(You can also open the same browser in Incognito Mode for this step.)
3030

3131
5. Click the Target API button and paste in the new Rest API URL.
32-
6. Notice the title of the page has updated to **DynamoDB App** in a blue color.
32+
6. Notice the title of the page has updated to **DynamoDB App** in a blue color. If it isn't blue, you can refresh the page and see the color change.

content/relational-migration/data migration/index3.en.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@ We can also check the import status within the AWS Console.
4444
4. In the search box, type DynamoDB to visit the DyanmoDB console.
4545
5. From the left nav, click Imports from S3.
4646
6. Notice your import is listed along with the current status.
47+
![Import from S3](/static/images/relational-migration/import-from-s3.png)
4748
7. Once the import has completed, you can click it to see a summary including item count and the size of the import.
4849
8. On the left nav, click to Tables.
4950
9. In the list of tables, click on the Customers table.

content/relational-migration/index.en.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ then apply them to create a new VIEW and use this to perform a custom import.
5858
Developer challenge: Write a new set of data access functions that point to DynamoDB.
5959

6060
### Runtime environment
61-
This workshop is designed to run in an AWS-provided environment that includes a MySQL database on EC2.
61+
This workshop is designed to run in an immersion day on Workshop Studio in an AWS-provided environment that includes a MySQL database on EC2. It cannot be run in your own AWS account, however the code is all open source.
6262

6363
### Technical Depth
6464
This workshop is a L300 level workshop. Having SQL, Python, and Bash skills will help but are not required.

content/relational-migration/setup/index.en.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,6 @@ You likely have a developer desktop or laptop,
1414
the ability to find and clone the public Github code repository,
1515
and a running MySQL database instance.
1616
You can create a new Amazon S3 bucket quickly, which can be used as a staging area for data to be migrated.
17-
All the steps, tools, and scripts presented in the workshop are designed to be taken home with you
18-
so you can perform a real database migration.
1917

2018

2119

content/relational-migration/setup/index2.en.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,6 @@ The Lambda source code project has been setup as follows
2626

2727

2828
1. Next, let's deploy the Chalice application stack.
29-
The deploy may take up to three minutes, be patient.
30-
3129
```bash
3230
chalice deploy --stage relational
3331
```

contentspec.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@ params:
1313
event_driven_architecture_lab_yaml : "https://s3.amazonaws.com/amazon-dynamodb-labs.com/assets/event-driven-cfn.yaml"
1414
github_contributing_guide : "https://github.com/aws-samples/amazon-dynamodb-labs/blob/master/CONTRIBUTING.md"
1515
github_issues_link : "https://github.com/aws-samples/amazon-dynamodb-labs/issues"
16-
lsql_git_commit : "cea34bc520512c70091aba2995de0e99a31d1078"
16+
lsql_git_commit : "47a43bedf75bc0859e9141ad1bdd1f330f0933f1"

0 commit comments

Comments
 (0)