Good question. Authenticate with AWS: Terraform uses AWS credentials (usually stored in ~/.aws/credentials, environment variables, or IAM roles) to authenticate API requests. These credentials allow Terraform to interact with the AWS API to resources
Thanks for the video! What would be the procedure if I wish to use an existing VPC and not create a new one? I have an existing cluster that I want to replace with a new one, but I want to maintain the networking.
To use an existing VPC in your EC2 instance configuration with Terraform, follow these steps: 1. Fetch Existing VPC Information: • Use the data source to retrieve information about your existing VPC. • Similarly, fetch the details of the existing subnets, security groups, etc. 2. Define EC2 Instance: • Reference the VPC ID, subnet ID, and other relevant details in the EC2 instance resource.
@@CloudcoreHub Thanks for your reply. Would you mind making a practical video about this to show a step-by-step procedure? I've tried to look around online but there seems not to be much resource about how to work this out. I want to be able to create a new EKS cluster with Terraform, but using the networking resources of the the existing cluster (the plan is to take down the existing cluster after the new one is up and running).
@CloudcoreHub: instead of create vpc then provision EKS on that vpc, how we can provision EKS in the custom vpc which created manually how we can take reference of provisioned vpc under EKS?
Thank you ma’am for your videos
Thanks for the feedback
thanks, very useful
Thank you
How AWS Console is communicate with Terraform scripts? I mean In your local VS Code to AWS Console?
Good question.
Authenticate with AWS:
Terraform uses AWS credentials (usually stored in ~/.aws/credentials, environment variables, or IAM roles) to authenticate API requests. These credentials allow Terraform to interact with the AWS API to resources
Thanks for the video! What would be the procedure if I wish to use an existing VPC and not create a new one? I have an existing cluster that I want to replace with a new one, but I want to maintain the networking.
To use an existing VPC in your EC2 instance configuration with Terraform, follow these steps:
1. Fetch Existing VPC Information:
• Use the data source to retrieve information about your existing VPC.
• Similarly, fetch the details of the existing subnets, security groups, etc.
2. Define EC2 Instance:
• Reference the VPC ID, subnet ID, and other relevant details in the EC2 instance resource.
@@CloudcoreHub Thanks for your reply. Would you mind making a practical video about this to show a step-by-step procedure? I've tried to look around online but there seems not to be much resource about how to work this out. I want to be able to create a new EKS cluster with Terraform, but using the networking resources of the the existing cluster (the plan is to take down the existing cluster after the new one is up and running).
Thanks for video and effort.
How the IAM identity provider getting mapped with eks cluster?
Thanks for the question, it is mapped to the resources that eks depends on
How to integrate argocd with it
Hi, I'm currently working on e2e project, that will also include argoCD. thanks for the comment
@@CloudcoreHub great ...looking forward to that!
The requested project is now available on the channel ua-cam.com/video/EVG51U3VcYs/v-deo.html
@CloudcoreHub: instead of create vpc then provision EKS on that vpc, how we can provision EKS in the custom vpc which created manually how we can take reference of provisioned vpc under EKS?
yes, you can specify the custom VPC ID in your AWS EKS module
@@CloudcoreHub can you give an example, it will be helpful if any video to take reference or make a short video.
Can you use this as a project on your resume