@ 9:00 mark you mention main Route Table, curious, whats the purpose. I've always left it alone, thinking if I delete it I will break things badly... ;) Also for Private1 you assign a NatGW and for Private2 you assign a NatGW... if the NatGW1 fails... then I assume everything in Private1 would loose internet connectivity, as we did not associate NatGW2 with Private1 ?
thanks. Is it recommended to create .tf files for different sections such as routes, subnets, nat , etc or can it all be in one main.tf file ? Is it personal preference or rather it's a standard to do it this way?
No, it's up to you how to structure tf, there is only some best practices how to structure terraform modules, for example to have output.tf, variables.tf etc files
Inappropriate value for attribute "route": element 0: attributes "carrier_gateway_id", "destination_prefix_list_id", "egress_only_gateway_id", "gateway_id", "instance_id", "ipv6_cidr_block", "local_gateway_id", "network_interface_id", "transit_gateway_id", "vpc_endpoint_id", and "vpc_peering_connection_id" are required. + no source code here so no where to see diff
I have a source, let me try to find it, it's in of those lessons - github.com/devops-by-example/tutorials/tree/master/lessons or here github.com/antonputra/tutorials/tree/main/lessons :)
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
Thanks. A really great video. I was initially a little confused by Terraform AWS route table configurations, but you explained them well.
Thanks!
Playlist: ua-cam.com/play/PLiMWaCMwGJXkeBzos8QuUxiYT6j8JYGE5.html
⏱️TIMESTAMPS⏱️
0:00 Intro
0:04 AWS Main Route Table
1:03 AWS Public Route Table
1:41 AWS Private Route Table
2:06 AWS Peering Route Table
2:41 Terraform AWS Route Table Creation
6:24 Terraform AWS Route Table Association
i like the way you explained, very useful and easy to understand 🙏
Thank you!
👉 How to Manage Secrets in Terraform - ua-cam.com/video/3N0tGKwvBdA/v-deo.html
👉 Terraform Tips & Tricks - ua-cam.com/video/7S94oUTy2z4/v-deo.html
👉 ArgoCD Tutorial - ua-cam.com/video/zGndgdGa1Tc/v-deo.html
quite helpful
Glad to hear that
@ 9:00 mark you mention main Route Table, curious, whats the purpose. I've always left it alone, thinking if I delete it I will break things badly... ;)
Also for Private1 you assign a NatGW and for Private2 you assign a NatGW... if the NatGW1 fails... then I assume everything in Private1 would loose internet connectivity, as we did not associate NatGW2 with Private1 ?
don't delete main route table, all other tables inherit those rules. You can create HA nat gateway. 1 NAT per AZ.
Thank you!
You bet!
Thanks!
Welcome!
thanks. Is it recommended to create .tf files for different sections such as routes, subnets, nat , etc or can it all be in one main.tf file ? Is it personal preference or rather it's a standard to do it this way?
No, it's up to you how to structure tf, there is only some best practices how to structure terraform modules, for example to have output.tf, variables.tf etc files
Great videos.... It will be grate if we get this source code in github
Thank you. Vivek, GitHub link is in description:)
github.com/antonputra/tutorials/tree/main/lessons/038/terraform
Inappropriate value for attribute "route": element 0: attributes
"carrier_gateway_id", "destination_prefix_list_id", "egress_only_gateway_id",
"gateway_id", "instance_id", "ipv6_cidr_block", "local_gateway_id",
"network_interface_id", "transit_gateway_id", "vpc_endpoint_id", and
"vpc_peering_connection_id" are required.
+ no source code here so no where to see diff
I have a source, let me try to find it, it's in of those lessons - github.com/devops-by-example/tutorials/tree/master/lessons or here github.com/antonputra/tutorials/tree/main/lessons
:)
I think that's the one - github.com/antonputra/tutorials/blob/main/lessons/038/terraform/routing-tables.tf#L22-L56