terraform-aws-ssh-bastion-service VS terraform

I'm not sure from this exactly what you're trying to do. If you're working with cloudinit/userdata then I can point you to an example.

I actually mashed together cloudposse/terraform-aws-dynamic-subnets (which has an option to use NAT instances instead of gateways) and joshuamkite/terraform-aws-ssh-bastion-service. That allowed for even cheaper setups where your bastion jump-host (the host you proxy through to get to the private subnets) is also the NAT gateway. I quite liked this setup because the bastion sessions were sufficiently sandboxed in a ephemeral container, and we didn't need twice the number of hosts to have both NAT instances and bastions.

I have a public terraform module which i migrated away from the template provider last year. You can see how I handled the changes and used the new provider if that helps

You should try to avoid using remote exec with terraform wherever possible. It's not a great fit with the declarative approach that Terraform aims for. Here you would be better off using 'user data' to provision your instance. I have a public project that deploys and builds a Golang app on EC2. It's a bit more complicated than your example here, but it does demonstrate a method for doing what you're trying to do with the approach that I have suggested.

The thing that really moved me on from junior to senior in this area was finding something that was a common pain point for many people that I could focus on to address as a 'simple' solution that could be used as a 'black box' or 'tick box'. Once it picked up steam I had to deal with other people's use cases and suggestions that I had never considered before, both in person (when i spoke at meetups) and online (open source project).

It looks like you might be misunderstanding the purpose of the yamlencode function here. Terraform doesn't need to know anything about the syntax of the file you're using with templatefile, as long as it's text, you're good. Just start with a yaml file and use the templatefile syntax for your substitutions. Examples

I have a public Terraform module with releases incrementing from tf 11 thru 1.2.0 where you can see changes dealing with this sorry of thing

I'm well aware. My repo that I linked is in multi part mime. An older version used different mime types but I couldn't get it to handle all the conditional logic reliably

I haven't seen your code but it sounds like you're using it wrong. I can well imagine that if you apply multiple cloudinit_config files to a single host that they get placed in alphabetical order but I don't really get why you would want to do that. In many environments, e.g. AWS, you can only supply a single user data file to your host anyway. cloudinit_config supports mullti-part MIME encoding so that you can combine sections from multiple sources in a predictable way.

You can see terraform rendering IAM policies with interpoalted assume role policies in my module.

I am not only a big fan of hashicorp terraform. I'm also one of the early adopters of it. So this is my main go-to Infrastructure as a Code tool. However all the resources I use are supported by other IaaC solutions such as AWS CloudFormation and AWS CDK. You definitely got to use one to avoid loosing the track of resources you create.

State Encryption was one of those long requested features[0] (I had it on my ideas list for years[1]) that Hashicorp didn't have much incentive to build. I don't think it has to with distancing opentofu as such, but the opentofu team prioritizing the right things that customers actually need.

[0]: https://github.com/hashicorp/terraform/issues/9556

[1]: https://github.com/captn3m0/ideas#-mars-terraform-remote-htt...

https://github.com/hashicorp/terraform/issues/34402

I’m not a lawyer and have no idea who is right or wrong but I understand why Hashicorp is scrutinizing this.

Just to give an example of the power of Go for CLI builds, you may have already used or at least heard of Docker, Kubernetes, Prometheus, Terraform, but what do they all have in common? They all have a large part of their usability via CLI and are developed in Go 🐿.

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

For example, integrating Terraform for infrastructure as code (IaC) into the IDP can streamline updates and rollbacks.

In this project, you will understand and get hands on experience around the entire concept around CI/CD from applications perspective. To fully gain real expertise around this idea, it is best to see it in action across different programming languages and from the platform perspective too. From the application perspective, we will be focusing on PHP here; there are more projects ahead that are based on Java, Node.js, .Net and Python. By the time you start working on Terraform, Docker and Kubernetes projects, you will get to see the platform perspective of CI/CD in action.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.