Hey, pretty good write up. I have only couple of suggestions:
better tags. I'm glad to see at-least one tag, adding some extra tags (for ex, I add a "used_for" tag for every stack I built) helps me analyze and possible revise stacks for cost savings/analysis
Terraform variable blocks can accept description, default and type constraints modifiers. Description is useful for documentation (alternatively, it prompts the description when used as an input variable), defaults can help set some sane default values and type constraints ensure you enter the right type.
For new folks, I really don't recommend touching the NACLs - the defaults are good and security groups provide a good enough firewall and updating NACLs without understanding the "stateless" mechanism can lead to lot of head-scratching on why something is broken.
Given DockerHub's new rate limiting policies, I think storing images in ECR is definitely worth it
Great post overall!
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
I tend to add a "Billing" tag to the resources so then they can be grouped in Cost Explorer. I will add that in!
I always seem to forget about variable descriptions and types!
I did mention the cost aspect of NAT gateways but I will make sure it's clearer.
I was so hesitant about putting in NACLs! I think everyone has been burned by NACLs at some point 😁 I will take them out to avoid confusion.
Again thanks for the feedback! I'm new to blogging and trying to make the call on what can be too confusing for people when reading. It's great to have someone else's opinion.
I missed reading up about the NAT gateways and its quite clear, hence I edited out my post. Your first post is quite impressive and look forward to reading more. Cheers
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
Hi! Sorry for the late reply. There isn't a way to prevent that but there is a tick box option in the cloud watch alarms panel to hide auto scaling alarms. I hope this helps.
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
Passionate Cloud and DevOps Architect, Automation Engineer, and DevSecOps enthusiast with a knack for optimizing workflows and ensuring seamless integration between development, operations & security.
Its too nice.. I have seen many blogs this is too neat .. we are trying to migrate from EC2 based ECS to Fargate....it took me 2 hours to migrate my entire code to to go with Fargate
My current role is as a Cloud Engineer. I have previously had roles as a full stack developer and a test engineer. I love all things AWS and serverless!
I'm a confused as to what you mean by too neat. This is the process I used at the time to create an auto-scaling ECS Fargate service, nothing more, nothing less. If this is too difficult to do in your codebase I would consider refactoring it down to make it easier to manage, then work from there
Hey, pretty good write up. I have only couple of suggestions:
Thanks for the feedback!
I tend to add a "Billing" tag to the resources so then they can be grouped in Cost Explorer. I will add that in!
I always seem to forget about variable descriptions and types!
I did mention the cost aspect of NAT gateways but I will make sure it's clearer.
I was so hesitant about putting in NACLs! I think everyone has been burned by NACLs at some point 😁 I will take them out to avoid confusion.
Again thanks for the feedback! I'm new to blogging and trying to make the call on what can be too confusing for people when reading. It's great to have someone else's opinion.
Maybe put a note at the top of the NACLs section just to warn people "You can do this if you want, but the defaults are ok if you're a beginner"?
Yep, totally
Kieran,
I missed reading up about the NAT gateways and its quite clear, hence I edited out my post. Your first post is quite impressive and look forward to reading more. Cheers
Thank you!
Hi, thank you for great post!
I've found a lot of posts related to Terraform, ECS and Fargate, but this one is the best!
Thank you. That means a lot!
There always low alarm for CPU and Memory in the cloudwatch. Is there anyway to prevent low alarm when instance number is 1 ? Thanks.
Hi! Sorry for the late reply. There isn't a way to prevent that but there is a tick box option in the cloud watch alarms panel to hide auto scaling alarms. I hope this helps.
So after a couple of days searching how to exactly do this process, I finally found the gold mine. Thanks a lot, Kieran!! You nailed it.
Thank you for reading! I'm glad it was useful
Its too nice.. I have seen many blogs this is too neat .. we are trying to migrate from EC2 based ECS to Fargate....it took me 2 hours to migrate my entire code to to go with Fargate
I'm a confused as to what you mean by too neat. This is the process I used at the time to create an auto-scaling ECS Fargate service, nothing more, nothing less. If this is too difficult to do in your codebase I would consider refactoring it down to make it easier to manage, then work from there
Seems to have an error on first line starting Load balance explanation:
shouldn't be elb/variables.tf?