Added a blurb about adding the port the LB is listening on in simple Fargate post.

thomasstep · thomasstep · commit 423ec6ad2451 · 2024-06-06T07:22:47.000-05:00
diff --git a/_posts/2021-02-22-cloudformation-example-for-simple-fargate-app.md b/_posts/2021-02-22-cloudformation-example-for-simple-fargate-app.md
@@ -14,4 +14,4 @@ I created the shared resources template with reusability across an application i
 
 The Fargate service template defines a service, task definition, load balancer listener, load balancer target group, and a CloudWatch log group. The service and task definition are necessary resources that tell the ECS cluster that we want to launch a service, how many instances of the service we want to launch, networking configuration, and some other configuration for the service. The task definition defines what the service will be running. Configuration for container definitions in the task definition includes where to find the Docker image, logging configuration, environment configuration, and other container level configuration that could be found in a `docker-compose` file. The task definition also includes some compute level configuration and defines IAM roles to be used. The load balancer listener tells the load balancer what port to listen on and to forward that traffic on to the target group, which finally forwards traffic to our container. It's worth mentioning that there is much more logic that can be built into load balancer listeners, and my configuration is simple by design.
 
-After spinning up the VPC, ECS cluster, and Fargate service, it is possible to make requests to the URL that is given to the load balancer and receive responses from the container. I was super excited to get this working in part two of my video series because I wasn't satisfied with the way I left things in the first video. I hope this has helped someone out there looking for a baseline Fargate service to get them off the ground. I plan to continue updating my [`aws-cloudformation-reference` GitHub repo](https://github.com/thomasstep/aws-cloudformation-reference) with other templates in the future to serve as a jumping-off point for various AWS architectures and service. Thanks for reading!
+After spinning up the VPC, ECS cluster, and Fargate service, it is possible to make requests to the URL (don't forget to add in the correct port that the load balancer is listening on) that is given to the load balancer and receive responses from the container. I was super excited to get this working in part two of my video series because I wasn't satisfied with the way I left things in the first video. I hope this has helped someone out there looking for a baseline Fargate service to get them off the ground. I plan to continue updating my [`aws-cloudformation-reference` GitHub repo](https://github.com/thomasstep/aws-cloudformation-reference) with other templates in the future to serve as a jumping-off point for various AWS architectures and service. Thanks for reading!

Original file line number	Diff line number	Diff line change
`@@ -14,4 +14,4 @@ I created the shared resources template with reusability across an application i`
`14`	`14`
`15`	`15`	The Fargate service template defines a service, task definition, load balancer listener, load balancer target group, and a CloudWatch log group. The service and task definition are necessary resources that tell the ECS cluster that we want to launch a service, how many instances of the service we want to launch, networking configuration, and some other configuration for the service. The task definition defines what the service will be running. Configuration for container definitions in the task definition includes where to find the Docker image, logging configuration, environment configuration, and other container level configuration that could be found in a `docker-compose` file. The task definition also includes some compute level configuration and defines IAM roles to be used. The load balancer listener tells the load balancer what port to listen on and to forward that traffic on to the target group, which finally forwards traffic to our container. It's worth mentioning that there is much more logic that can be built into load balancer listeners, and my configuration is simple by design.
`16`	`16`
`17`		-After spinning up the VPC, ECS cluster, and Fargate service, it is possible to make requests to the URL that is given to the load balancer and receive responses from the container. I was super excited to get this working in part two of my video series because I wasn't satisfied with the way I left things in the first video. I hope this has helped someone out there looking for a baseline Fargate service to get them off the ground. I plan to continue updating my [`aws-cloudformation-reference` GitHub repo](https://github.com/thomasstep/aws-cloudformation-reference) with other templates in the future to serve as a jumping-off point for various AWS architectures and service. Thanks for reading!
	`17`	+After spinning up the VPC, ECS cluster, and Fargate service, it is possible to make requests to the URL (don't forget to add in the correct port that the load balancer is listening on) that is given to the load balancer and receive responses from the container. I was super excited to get this working in part two of my video series because I wasn't satisfied with the way I left things in the first video. I hope this has helped someone out there looking for a baseline Fargate service to get them off the ground. I plan to continue updating my [`aws-cloudformation-reference` GitHub repo](https://github.com/thomasstep/aws-cloudformation-reference) with other templates in the future to serve as a jumping-off point for various AWS architectures and service. Thanks for reading!