Terragrunt is a terraform wrapper that supports keeping your tf configurations DRY https://terragrunt.gruntwork.io/

Hey 👋 Hey, I got this error while deploying

aws-load-balancer-controller

:

Error: cannot patch "aws-load-balancer-controller" with kind ServiceAccount: ServiceAccount "aws-load-balancer-controller" is invalid: [metadata.annotations: Invalid value: "'<http://eks.amazonaws.com/role-arn|eks.amazonaws.com/role-arn>'": prefix part a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. '<http://example.com|example.com>', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), metadata.annotations: Invalid value: "'<http://eks.amazonaws.com/role-arn|eks.amazonaws.com/role-arn>'": name part must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]')]

It’s happening because of this:

"serviceAccount.annotations.'eks\\.amazonaws\\.com/role-arn'"

I’m trying to do the same as in helm (when I’m running it just with helm it’s work. This is what I run with helm:

helm install aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=staging --set serviceAccount.annotations.'eks\.amazonaws\.com/role-arn'="arn:aws:iam::12345678:role/alb-staging"

and this is my TF code:

resource "helm_release" "alb" {
  name       = "aws-load-balancer-controller"
  repository = "<https://aws.github.io/eks-charts>"
  chart      = "aws-load-balancer-controller"
  namespace  = "kube-system"

  set {
    name  = "clusterName"
    value = module.eks.cluster_name
  }
  set {
    name  = "serviceAccount.annotations.'eks\\.amazonaws\\.com/role-arn'"
    value = aws_iam_role.alb_role.arn
  }
}

I’m trying to understand how can I do the same as I do in helm (’\.“) on TF. someone have an idea?

A great piece of reading about the basics of Terraform for everyone who’s debating To Terraform Or Not To Terraform. An article about configuration management in AWS. What benefits or drawbacks of Terraform would you add to what’s listed there?

Hi! 👋 How can we make this channel better? Please share what you would be interested in reading about / seeing more here. 📹 More video tutorials ✍️ More long form content 🙃 Give me the memes

Why invest in Terraform Enterprise instead of using a semi simplified version of Terraform? Anyone has any experience with it?

Found this comprehensive article on *Terraform* and *Ansible*, really liked the description, comparison and discussion. Do you agree that Terraform would be a better option for organizations working with cloud providers?

Was it difficult for your teams to implement Terraform using AWS services?

A useful expert talk:

Hungry? 🍔 Then I have a suggestion for you: a great read about automating 🍕with Terraform. Because why not? 😄

Hey all - i am trying to firm up a standard IaC pipeline for our enterprise and am struggling. There seem many ways to do this - and we have many ways internally which we're trying to standardise but each has it's own drawbacks: 1. multiple TFVARS files for envs (DEV, QA, STAGING, PROD) with multiple workspaces and a generic main.tf. This makes it difficult to test out different flavours of config safely given you're working on the main main.tf and it would be easy to push the change further. Also makes it harder when experimenting with Dev to make an urgent change elsewhere. 2. multiple config folders/repos. So a folder containing DEV config. A folder containing QA etc. Much better separation and you can make changes independently - but then you are repeating yourself and when you upgrade a module in DEV, you need to ensure you upgrade the same code in the QA, STAGING and PROD folders otherwise you have inconsistencies Especially interested to hear how people have configured this kind of workflow in Terraform Cloud. Thanks

I checked the Platform Engineering YouTube channel and found this great video discussing the and really liked how @Andrew Fong listed the requirements their team was looking for prior to choosing the IaC tool. I am personally interested in Terraform and Pulumi and wanted to hear your opinion on their pros and cons. My +/- board looks something like this: Terraform • Highly expandable • Infrastructure deployment quick & reliable • Dry runs • Ability to generate dependency graphs • Storage and import function for existing architectures • Support of various cloud solutions • Collaboration and security features available only in expensive enterprise plans • Demanding entry • No rollback capability built-in Pulumi (some of them from Andrew’s slides): • Multiple languages • Testable • Oriented towards “coders” • Typed • Can be self-hosted • Great CLI • IDE support • The risk of duplication • The documentation isn't as abundant • Pricy Please share yours. Thanks in advance!

Hey guys, Anyone that is dabbling with Terraform at the moment, take a look at www.opslycloud.com. You can create configurations pretty much in a few minutes, and we're going to be launching an import soon where you can sync your Cloud accounts directly, generate the configurations and create templates from there. As well BYOC of terraform modules and use those. Here's a quick demo https://www.loom.com/share/bd67811e6d1140f4a5acd6ccfd0b305c

Our team is considering Terraform vs Pulumi to build out our IaC setup. Can folks here please share real life use cases and examples where Terraform and Pulumi made a big difference for your team? Thanks in advance.

Hi folks, I’m searching for Terraform Cloud alternatives and I am faced with this article about it. Does someone use some tools listed in this article? If yes, what is your impression?

HI, Did anyone created a aurora cluster with terraform?

Terraform and K8s `tools overlap somewhat in scope and one is not a replacement for the other`_._ There are a few paradigms given in this article that I found interesting about the intersection of K8s and Terraform. Might be interesting to you too.

ICYMI https://platformengin-b0m7058.slack.com/archives/C037UGSKMBP/p1660413848744179

Hello everyone.

#terraform Has anyone successfully setup composer 2 using terraform on GCP?

Very interesting article for everyone who thinks there’s room for improvement in Terraform (I bet everyone is on the same page as I am). The author writes about production grade IaC coding. https://medium.com/@anshuman2121/terraform-production-grade-iac-coding-9e22a43b2f96

Join the webinar with Mineiros’ @Soren Martius about common pitfalls teams fall into when handling Terraform at scale. Sören will explain: • How to properly structure your Terraform code so that it scales among thousands of managed resources • How to get automation right that enables a highly collaborative working environment • Best practices when it comes to supporting tooling for orchestration and code generation, policies, cost prediction, vulnerability and threat detection Join the webinar 👉https://www.meetup.com/platform-engineers-atx-online/events/287418292/

I found that Terraform in Action is a clearly written, enjoyable read. I especially liked the deeper explanation of functional programming. Does anyone else have Terraform book or blog post recommendations?

Have you ever thought about who should write the Terraform? As the author indicates in this article, the answer is “it depends”. However, he points out some aspects that would help teams to make the right decision for them, such as: • Non-Negotiable Standards • Engineer Capability • Management Capability • Platform Team Capability • Time to Market Recommend to read

I just got to watch this webinar about . Thumbs up and thanks to @Soren Martius for sharing useful practices for automation, code generation and threat detection. Recommend it to everyone working with Terraform.

Successfully working self-service system for DevOps is probably the highest accomplishment point for platform engineers 💥 Join the webinar with Joern Stenkamp TODAY where he will show you how to enable self-service DevOps with Terraform Cloud and how it can scale for the enterprise, while striking the right balance between both sides.

I’m preparing a presentation for my team about the benefits of IaC. I thought this community is a perfect place to ask for additional input. So far I came up with the following: • Timely and seamless • Speed and scalability • Reusability • Budget-friendly • Saves from discrepancies and failure • Improved consistency • Eliminates configuration drift • Improved security strategies Anything you’d add?

Hello everyone. Has anyone run into this error before?

I’ve change the instance name several time. It will show the new instance name with the same error message. https://GitHub.com/ccarrylab/aws-tf-amazon-connect