update

Definitely-not-AWS-Workshops · Sep 23, 2024 · ed9a60a · ed9a60a
1 parent dc595f5
commit ed9a60a
Show file tree

Hide file tree

Showing 5 changed files with 17 additions and 9 deletions.
diff --git a/...ur-First-Release-Workflow-Executions/1-Configure-Database-Credentials/_index.md b/...ur-First-Release-Workflow-Executions/1-Configure-Database-Credentials/_index.md
@@ -35,4 +35,12 @@ sed -i 's/<YOUR-AWS-SECRECTS-MANAGER-NAME>/<AWS-SECRECTS-MANAGER-NAME>/g' src/ma
 
 ```git
 git add . && git commit -m "configure database credentials" && git push --set-upstream origin config-db
-```
+```
+
+**5.** On your remote repository, click **Compare & pull request**.
+
+![0001](/images/16/1/0001.svg?featherlight=false&width=100pc)
+
+**6.** Click **Create pull request**.
+
+![0002](/images/16/1/0002.svg?featherlight=false&width=100pc)
diff --git a/content/7-Create-AWS-ECS-Resources/1-Create-ECS-Task-Definition/_index.md b/content/7-Create-AWS-ECS-Resources/1-Create-ECS-Task-Definition/_index.md
@@ -7,7 +7,7 @@ pre : " <b> 7.1 </b> "
 ---
 
 
-Let's create an AWS ECS Task Definition - a JSON file that defines the configuration of a task in Amazon Elastic Container Service (ECS). It acts like a blueprint that tells ECS how to run a Docker container, including information about the container image, resources, environment variables, networking, logging, and IAM roles.
+Let's create an AWS ECS Task Definition - a JSON file that defines the configuration of a task in Amazon Elastic Container Service (ECS). It acts like a blueprint that tells AWS ECS how to run a Docker container, including information about the container image, resources, environment variables, networking, logging, and IAM roles.
 
 **1.** Go to [AWS ECS console](https://console.aws.amazon.com/ecs/).
 
@@ -33,7 +33,7 @@ Let's create an AWS ECS Task Definition - a JSON file that defines the configura
 **5.** In the **Container - 1** section, 
 
 - For **Name**, enter `awsome-books`.
-- For **Image URI**, choose one that you have noted down in step **7** in [4. Create AWS ECR](4-create-aws-ecr).
+- For **Image URI**, choose one that you have noted down in step **7** in [5. Create AWS ECR](5-create-aws-ecr).
 - For **Container port**, enter `8080`.
 
 ![0004](/images/7/1/0004.svg?featherlight=false&width=100pc)

diff --git a/content/7-Create-AWS-ECS-Resources/2-Create-ECS-Cluster/_index.md b/content/7-Create-AWS-ECS-Resources/2-Create-ECS-Cluster/_index.md
@@ -37,7 +37,7 @@ You next create an ECS service that run the AWSome Books application at scale.
 
 **7.** In the **Deployment configuration** section,
 
-- For **Family**, choose **awsome-books**.
+- For **Family**, choose **awsome-books** (LATEST should be your default **Revision**).
 - For **Service name**, enter `awsome-books`.
 
 ![0006](/images/7/2/0006.svg?featherlight=false&width=100pc)
@@ -53,7 +53,7 @@ You next create an ECS service that run the AWSome Books application at scale.
 - For **VPC**, choose the VPC named **fcj**.
 - For **Subnets**, select subnets **fcj-private-02** and **fcj-private-05**.
 - For **Security group**, select **fcj-ecs-fargate**.
-- For **Public IP**, disable **Turned off**.
+- For **Public IP**, leave it as **Turned off**.
 
 ![0008](/images/7/2/0008.svg?featherlight=false&width=100pc)
 

diff --git a/content/9-Create-AWS-API-Gateway-Resources/1-Create-VPC-Link/_index.md b/content/9-Create-AWS-API-Gateway-Resources/1-Create-VPC-Link/_index.md
@@ -22,7 +22,7 @@ pre : " <b> 9.1 </b> "
 **4.** In the **VPC link details** section,
 
 - For **Name**, enter `vpc-link-nlb`.
-- For **Target NLB**, enter the arn of Network Load Balancer named `fcj-nlb` you have created.
+- For **Target NLB**, enter the arn of Network Load Balancer named **fcj-nlb** you have created.
 
 ![0003](/images/9/1/0003.svg?featherlight=false&width=100pc)
 

diff --git a/content/9-Create-AWS-API-Gateway-Resources/2-Create-AWS-API-Gateway/_index.md b/content/9-Create-AWS-API-Gateway-Resources/2-Create-AWS-API-Gateway/_index.md
@@ -38,7 +38,7 @@ pre : " <b> 9.2 </b> "
 
 - For **HTTP method**, select **ANY**.
 - For **VPC link**, select **[Use stage variable]** and enter `${stageVariables.vpcLinkId}`. You define the vpcLinkId stage variable after deploying the API to a stage and set its value to the ID of the VpcLink.
-- For **Endpoint URL**, enter the Network Load Balancer's DNS name you have noted down in step **12** in [7. Create Network Load Balancer](7-create-network-load-balancer).
+- For **Endpoint URL**, enter the Network Load Balancer's DNS name you have noted down in step **12** in [8. Create Network Load Balancer](8-create-network-load-balancer).
 
 ![0005](/images/9/2/0005.svg?featherlight=false&width=100pc)
 
@@ -71,12 +71,12 @@ pre : " <b> 9.2 </b> "
 ![00011](/images/9/2/00011.svg?featherlight=false&width=100pc)
 
 - For **Name**, enter `vpcLinkId`.
-- For **Value**, enter the VPC Link ID you have noted down in step **6** in [8.1 Create VPC Link](8-create-aws-api-gateway-resources/1-create-vpc-link).
+- For **Value**, enter the VPC Link ID you have noted down in step **6** in [9.1 Create VPC Link](9-create-aws-api-gateway-resources/1-create-vpc-link).
 - Click **Save**.
 
 ![00012](/images/9/2/00012.svg?featherlight=false&width=100pc)
 
-**12.** To view the results, use the URL you obtained in step **9**. If you try to invoke more than once, you should see 2 internal IP addresses in 2 seperate subnets (Yours should be different from mine).
+**12.** To view the results, use the URL you obtained in step **9**. If you try to invoke more than once, you should see 2 internal IP addresses in 2 seperate subnets (Yours could be different from mine).
 
 ![00013](/images/9/2/00013.svg?featherlight=false&width=100pc)