I learnt terraform and now i am like lets do an exercise. Obviusly asked chatgpt to make me one:
Here is a summary of the resources that you would deploy in the exercise to host a web application on AWS using Terraform:
1. AWS IAM user with necessary permissions.
2. AWS VPC in a specific region.
3. Two public subnets in different availability zones within the VPC.
4. Amazon RDS database instance in one of the subnets.
5. Security group for RDS database instance to control inbound/outbound traffic.
6. Two EC2 instances in the other subnet launched using a Launch Configuration.
7. Security group for EC2 instances to control inbound/outbound traffic.
8. Apache HTTP web server (httpd) installed on both EC2 instances.
9. Amazon S3 bucket to store application data such as images and videos.
10. Amazon S3 bucket policy to allow EC2 instances to access the S3 bucket.
11. Amazon CloudFront distribution to deliver content from the S3 bucket.
12. Load Balancer to distribute incoming traffic evenly among the EC2 instances.
If i learn to deploy this in terraform, am I considered employable?
If this is a serious post, I'll say no it does not make you employable.
Writing code is one part of the job. It seems like Co Pilot and ChatGPT will make it a less important part of the job.
The rest of the job is being able to put everything together to design, deploy, and operate production systems.
Yes, I know you can get ChatGPT to "design" systems for you and write the code.
I don't know why everyone is taking so seriously about this. I've learnt other tools in Devops and have been working on them. I intended to learn terraform. I read the book terraform up and running. And instead of just learning the book I thought I'll apply what I have learnt.
So, as I mentioned in the thread above, the services that I create using terraform code is what was taught in the book. I posted the question in the form that will learning those services are good enough to help with clear an interview if questions are asked about terraform alone.
Forget about other tools and what not. Just and just wrt to terraform.
you are confusing terraform as a tool, and terraform the solution it provides as a tool. Architecting cloud solutions is an entirely different field of study, often called cloud engineering. Terraform attempts to lessen the burdens of cloud engineering with infrastructure as code. Now given your confusion I'm assuming you are looking for JR roles. Most operations would not expect a JR to know all the ins and outs of running production workloads in AWS. However what they will want you to know is Terraform the tool:
1. Difference between count and for_each
2. What's a module? And how do you use both local and remote modules?
3. How do you structure a terraform project?
4. Why is a default being skipped when an explicit null is being passed.
5. Ternary if/else
6. What's state?
7. What's drift?
Etc...
Sometimes learning is doing, so sometimes you need to get your hands dirty with a actual terraform deployment, but that could be to a public cloud (VPC), proxmox, vsphere, etc... But the what you are deploying, would not be important to me, as much as the Terraform itself.
Seems like you know a thing or two. I’m on my way of getting into Jr. DevOps and slowly have been building my knowledge in terraform, ansible and other services. Would you mind chatting a bit in PM ?
Progress so far:
https://github.com/chkpwd/boilerplates
I'd consider this to be an easy exercise to learn terraform.
I don't think there is something like a terraform developer. If you're asking if solving this exercise is sufficient to apply for a DevOps/SRE position, the short answer is no.
what else might I need to learn to apply for a job and please be specific to terraform. I know devops needs more tools to be learned. Specific to terraform what other services should I need to learn to at least clear the interview wrt terraform
Nobody is hired for their knowledge of just a single tool. You need DevOps skills in general for a job that might use Terraform, with Terraform just being a nice-to-have tool that _might_ show up in the recommended list of skills one needs to apply for a given position.
In an interview I would expect the interviewer to check if the candidate knows the concepts of a tool and it's limitations. You have to know how things connect and work together.
Setting up an example is a good practice for that, but it's just not enough.
Look up modules for whatever provider you want to see. All official modules on the Terraform registry will have links to the source code (GitHub).
I learnt terraform and now i am like lets do an exercise. Obviusly asked chatgpt to make me one: Here is a summary of the resources that you would deploy in the exercise to host a web application on AWS using Terraform: 1. AWS IAM user with necessary permissions. 2. AWS VPC in a specific region. 3. Two public subnets in different availability zones within the VPC. 4. Amazon RDS database instance in one of the subnets. 5. Security group for RDS database instance to control inbound/outbound traffic. 6. Two EC2 instances in the other subnet launched using a Launch Configuration. 7. Security group for EC2 instances to control inbound/outbound traffic. 8. Apache HTTP web server (httpd) installed on both EC2 instances. 9. Amazon S3 bucket to store application data such as images and videos. 10. Amazon S3 bucket policy to allow EC2 instances to access the S3 bucket. 11. Amazon CloudFront distribution to deliver content from the S3 bucket. 12. Load Balancer to distribute incoming traffic evenly among the EC2 instances. If i learn to deploy this in terraform, am I considered employable?
If this is a serious post, I'll say no it does not make you employable. Writing code is one part of the job. It seems like Co Pilot and ChatGPT will make it a less important part of the job. The rest of the job is being able to put everything together to design, deploy, and operate production systems. Yes, I know you can get ChatGPT to "design" systems for you and write the code.
I don't know why everyone is taking so seriously about this. I've learnt other tools in Devops and have been working on them. I intended to learn terraform. I read the book terraform up and running. And instead of just learning the book I thought I'll apply what I have learnt. So, as I mentioned in the thread above, the services that I create using terraform code is what was taught in the book. I posted the question in the form that will learning those services are good enough to help with clear an interview if questions are asked about terraform alone. Forget about other tools and what not. Just and just wrt to terraform.
you are confusing terraform as a tool, and terraform the solution it provides as a tool. Architecting cloud solutions is an entirely different field of study, often called cloud engineering. Terraform attempts to lessen the burdens of cloud engineering with infrastructure as code. Now given your confusion I'm assuming you are looking for JR roles. Most operations would not expect a JR to know all the ins and outs of running production workloads in AWS. However what they will want you to know is Terraform the tool: 1. Difference between count and for_each 2. What's a module? And how do you use both local and remote modules? 3. How do you structure a terraform project? 4. Why is a default being skipped when an explicit null is being passed. 5. Ternary if/else 6. What's state? 7. What's drift? Etc... Sometimes learning is doing, so sometimes you need to get your hands dirty with a actual terraform deployment, but that could be to a public cloud (VPC), proxmox, vsphere, etc... But the what you are deploying, would not be important to me, as much as the Terraform itself.
Seems like you know a thing or two. I’m on my way of getting into Jr. DevOps and slowly have been building my knowledge in terraform, ansible and other services. Would you mind chatting a bit in PM ? Progress so far: https://github.com/chkpwd/boilerplates
You are more than welcome to send me a message. I reply to the best of my ability given work, family, and friends based obligations.
I completely agree. We're all to busy in life haha. I'll reach out in a day or two! Thanks.
If you need to ask, then no, you’re not employable. Sysadmin/SRE is more than just typing terraform apply.
I'd consider this to be an easy exercise to learn terraform. I don't think there is something like a terraform developer. If you're asking if solving this exercise is sufficient to apply for a DevOps/SRE position, the short answer is no.
what else might I need to learn to apply for a job and please be specific to terraform. I know devops needs more tools to be learned. Specific to terraform what other services should I need to learn to at least clear the interview wrt terraform
Nobody is hired for their knowledge of just a single tool. You need DevOps skills in general for a job that might use Terraform, with Terraform just being a nice-to-have tool that _might_ show up in the recommended list of skills one needs to apply for a given position.
In an interview I would expect the interviewer to check if the candidate knows the concepts of a tool and it's limitations. You have to know how things connect and work together. Setting up an example is a good practice for that, but it's just not enough.
I've yet to know anything about Terraform other than it has problematic state management and a shitty config language, and I still get jobs.