UpCloud<p>New shitpost from our Developer Experience team: "Tell me terraform no longer segfaults without telling me it no longer segfaults"</p><p>Happy Friday (deploy) everyone!</p><p><a href="https://mastodon.social/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> <a href="https://mastodon.social/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> <a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a></p>
Recent searches
No recent searches
Search options
Only available when logged in.
social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.
Administered by:
Server stats:
3.9Kactive users
social.tchncs.de: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.6
#opentofu
3 posts · 3 participants · 0 posts today
Johannes Kastl<p>OK, today I took some time and finally reworked the <a href="https://digitalcourage.social/tags/semaphoreui" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>semaphoreui</span></a> package for <span class="h-card" translate="no"><a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>opensuse</span></a></span>. I had it on my todo list for ages and never got around to it. It was already 90% finished but lacking some fine details.</p><p>Now I have properly cleaned it up and removed the "ansible-" from the name, as it is no longer just for executing <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ansible</span></a> code. Apparently Semaphore can now execute <a href="https://digitalcourage.social/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> <a href="https://digitalcourage.social/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> and <a href="https://digitalcourage.social/tags/pulumi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pulumi</span></a> code as well.</p><p>I'll do more testing before I send it to <a href="https://digitalcourage.social/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tumbleweed</span></a>. <br>In other words: new vagrant-libvirt setup incoming! :-)</p><p>Stay tuned.</p><p><a href="https://digitalcourage.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a> <a href="https://digitalcourage.social/tags/IaC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IaC</span></a> <a href="https://digitalcourage.social/tags/InfrastructureAsCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InfrastructureAsCode</span></a> <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ansible</span></a> <a href="https://digitalcourage.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a> <a href="https://digitalcourage.social/tags/Pulumi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pulumi</span></a> <a href="https://digitalcourage.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> <a href="https://digitalcourage.social/tags/packagerslife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>packagerslife</span></a> <a href="https://digitalcourage.social/tags/opensuse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensuse</span></a></p>
Noah<p>Whew...the muscle memory to type "tofu" instead of "terraform" is *really* strong. I made the switch fully a couple of months back, finally updating all my IAC repos to use <a href="https://10base2.dev/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> instead of <a href="https://10base2.dev/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a>. I took the opportunity to centralize on a single reusable release pipeline instead of each having their own, which I honestly should have done in the first place but that's showbiz baby. </p><p>It's just like how when I switched to using "main" as my primary repository name, it took time to rework that muscle memory but eventually that became natural for me and typing in anything else when branching and merging felt strange. </p><p>So while maybe DevOps and SRE shouldn't be seen as a reflection of real life, in this case I think there's a lesson to be gleaned. Sometimes breaking a habit is hard. Sometimes it's more than just a habit and you're trying to change something fundamental about yourself or your work environment and that's even harder and maybe even impossible for some. But striving towards that goal is still important. Maybe it'll take you a year to make a change feel natural. Maybe it'll taken ten. Maybe it'll never feel 100% authentic and natural. That time is going to elapse either way. You can choose to stay right where you are right now or you can refactor and work towards something else and see how far you get. </p><p>Might as well right? Tech debt, emotional debt, it all comes due at some point and if you don't start now then it'll keep accruing and you'll still be sitting here 1 or 5 or 20 years from now thinking maybe you should fix something. </p><p>This is a post about <a href="https://10base2.dev/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a> but I only got a few sentences into this before I realized I really wanted to write about life and about change and about doing something different. </p><p>So maybe what I do to pay the bills is more rooted in real life than I thought.</p>
hobbsc<p>all the <a href="https://social.sdf.org/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ansible</span></a> and <a href="https://social.sdf.org/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> stuff i've been doing at work makes me want to get off my duff and finally get all of my home infrastructure into "code".</p><p>the problem is i do it all day, i don't want to also do it when i get home. just devoops things.</p>
Nic Roland :mastodon:<p>Anyone using terraform/opentofu for their homelab setups? Either on infra level or for CM?</p><p>I've made it a project for this year to get everything managed via gitops. I'm taking it step by step and as such I haven't locked down manual write access so that I can tinker with stuff and troubleshoot as needed.</p><p>I'm finding that I need a good way to spot state drift so that I get notified if I forget to correct things afterwards. I think this is going to be less frustrating than fighting against enforced state while I get my bearings.</p><p>I guess I could use a cron or a timer unit. Unless someone has any recommendations? I would like to manage all the TF using fluxcd eventually but I think it's too early to start enforcing desired state right now. I'm open to suggestions...?</p><p><a href="https://techhub.social/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> <a href="https://techhub.social/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> <a href="https://techhub.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> <a href="https://techhub.social/tags/selfhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhost</span></a> <a href="https://techhub.social/tags/gitops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>gitops</span></a> <a href="https://techhub.social/tags/fluxcd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fluxcd</span></a> <a href="https://techhub.social/tags/IaC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IaC</span></a> <a href="https://techhub.social/tags/infrastructureascode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infrastructureascode</span></a></p>
Esk 🐌⚡💜<p>howdy, folks - it's been a bit since our last <a href="https://hachyderm.io/tags/hachyderm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hachyderm</span></a> infra check in.</p><p>stuff in motion:</p><p>- ditching <a href="https://hachyderm.io/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> cloud & tf for <a href="https://hachyderm.io/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> and <a href="https://hachyderm.io/tags/atlantis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>atlantis</span></a>. we are just about to import our dev environment and put it through its paces.<br>- bringing <a href="https://hachyderm.io/tags/postgresql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>postgresql</span></a> under ansible management. the team has been doing awesome work, and we've started to spin up dev nodes using the new playbooks. soon: production!<br>- moving <a href="https://hachyderm.io/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> zones away from AWS route 53. we chose bunny DNS as our provider and have been doing basic tests in dev. we'll likely prep our records for production this week with a plan for a cutover in one of the coming weekends.</p><p>and if you filled out our volunteer form and haven't heard from me in a bit - you're still on the list. we'll onboard a new batch of folks in the next couple of weeks.</p><p>:hachyderm: :blobfoxheartcute: </p><p><span class="h-card" translate="no"><a href="https://hachyderm.io/@hachyderm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>hachyderm</span></a></span> </p><p><a href="https://hachyderm.io/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a> <a href="https://hachyderm.io/tags/sre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sre</span></a> <a href="https://hachyderm.io/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastoadmin</span></a></p>
Grzegorz Cichocki<p>I must admit, writing in OpenTofu / Terraform is the first time in a while that I’m actually having fun with code. It is just genuinely enjoyable. It’s been a long time since I’ve had this much fun tinkering with code. <br><a href="https://mastodon.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> <a href="https://mastodon.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a> <a href="https://mastodon.social/tags/IaC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IaC</span></a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a></p>
1lowlyadmin<p>Finished up “testing/evaluating” bare metal <a href="https://infosec.exchange/tags/OpenShift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenShift</span></a> on my 3 Minisforum <a href="https://infosec.exchange/tags/ms01" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ms01</span></a> nodes (didn’t get very far before abandoning), and back to <a href="https://infosec.exchange/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a>. Now to learn some <a href="https://infosec.exchange/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> and/or <a href="https://infosec.exchange/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a>, and <a href="https://infosec.exchange/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ansible</span></a> to repopulate the cluster instead of doing everything manually. <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a></p>
dotemacs<p><a href="https://mastodon.xyz/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> supports S3 state locking.</p><p>No need to use DynamoDB for it any more.<br>The lock will be stored next to the state, in S3.</p><p>tl;dr:</p><p>If you have the config for state locking in DynamoDB, keep it, but add S3 option too.<br>Once you're happy that both are state locking, remove the DynamoDB option. Which will leave only the S3 option on.</p><p>See the official docs for info:</p><p><a href="https://github.com/opentofu/opentofu/blob/7fd9c48275c84ef437a8e1bead27942869b70b00/website/docs/language/settings/backends/s3.mdx#s3-state-locking" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/opentofu/opentofu/b</span><span class="invisible">lob/7fd9c48275c84ef437a8e1bead27942869b70b00/website/docs/language/settings/backends/s3.mdx#s3-state-locking</span></a></p><p>This feature will be available in 1.10.0 version. Or right now, if you build from source.</p>
DragonflyDB<p>Introducing the much-requested Dragonfly Cloud Terraform Provider! Automate and manage your Dragonfly in-memory data store with full infrastructure-as-code support. Now available for both <a href="https://mastodon.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a> and <a href="https://mastodon.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a>. Learn more in our announcement post: <a href="https://www.dragonflydb.io/blog/introducing-the-dragonfly-cloud-terraform-provider" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">dragonflydb.io/blog/introducin</span><span class="invisible">g-the-dragonfly-cloud-terraform-provider</span></a> <a href="https://mastodon.social/tags/DragonflyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DragonflyDB</span></a><br><a href="https://www.dragonflydb.io/blog/introducing-the-dragonfly-cloud-terraform-provider" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">dragonflydb.io/blog/introducin</span><span class="invisible">g-the-dragonfly-cloud-terraform-provider</span></a></p>
Adriana Villela 🇧🇷🇨🇦<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@anamedina" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>anamedina</span></a></span> and I dig into 3 IaC tools so you don’t have to. Catch us at <a href="https://hachyderm.io/tags/SCaLE22x" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SCaLE22x</span></a> this week as we compare <a href="https://hachyderm.io/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a>, <a href="https://hachyderm.io/tags/pulumi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pulumi</span></a>, and <a href="https://hachyderm.io/tags/crossplane" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>crossplane</span></a>. </p><p><a href="https://www.socallinuxexpo.org/scale/22x/presentations/infrastructure-code-3-ways" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">socallinuxexpo.org/scale/22x/p</span><span class="invisible">resentations/infrastructure-code-3-ways</span></a></p>
dotemacs<p><span class="h-card" translate="no"><a href="https://babka.social/@serge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>serge</span></a></span> There isn't a OpenTofu provider that allows you to call Python directly, but you can use Go provider for OpenTofu, and use embedded Python: </p><p><a href="https://github.com/kluctl/go-embed-python" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kluctl/go-embed-pyt</span><span class="invisible">hon</span></a></p><p>Or you can use a Python wrapper library: </p><p><a href="https://github.com/terraformindepth/tofupy" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/terraformindepth/to</span><span class="invisible">fupy</span></a></p><p>Basically, there are ways to do what you're after. You just have to pick your “flavour”.</p><p><a href="https://mastodon.xyz/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> <a href="https://mastodon.xyz/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a></p>
Adam<p>The end goal for the new infrastructure is to provision the machine with OpenTofu and then configure it using Ansible. Hoping to start looking at OpenTofu next week.</p><p><a href="https://fosstodon.org/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ansible</span></a> <a href="https://fosstodon.org/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> <a href="https://fosstodon.org/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devops</span></a></p><p>4/4</p>
Noah<p>For folks looking to move away from giving <a href="https://10base2.dev/tags/amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amazon</span></a> more of your money and need options other than <a href="https://10base2.dev/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AWS</span></a> for a home cloud setup, I can suggest a couple of solid options. There are *tons* more out there like Digital Ocean, Vultr, Kamatera, etc. but with the ones below I have personal experience.</p><p>First, Dreamhost has done extremely well by me and their OpenStack infra supports provisioning with <a href="https://10base2.dev/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> (or Terraform if that's what you fancy). I have a good chunk of my sites hosted through them and they've never let me down. If you don't want to roll your own server there is shared hosting that is exceptionally cheap for what you get. </p><p>The Mastodon instance I manage, <a href="https://10base2.dev" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">10base2.dev</span><span class="invisible"></span></a>, is running on Linode shared hosts. Likewise I provisioned with OpenTofu and it's been running without issues for a few months now. I feel I should point out that I work for Akamai so no one comes pointing fingers at me like I'm trying to shill for the company I work for. I won't kvell too much and instead will say it's been speedy and easy to manage. </p><p>Anyway, there you go, those are a couple of options to break away from AWS which, last I checked, is how you really make Amazon hurt. Even if no one bought a single thing from them going forwards, it's all of 17% of their net income. Hit them in the cloud compute pockets, that's how you make them hurt. </p><p>If you're taking part in the protest on Friday, see if you can destroy any infra you have deployed in AWS or if you're using more permanent EC2 instances that you keep around forever, just shut it off so you don't accrue any additional spend on the compute. I will lecture you later on treating EC2 as ephemeral and not as drop-ins for servers in a data center. </p><p>Please feel free to reply with other options you know of, especially if you can speak to what your experience has been in building infrastructure there as that would be quite helpful.</p>
Maquinari.cat<p>Ara que IBM ja controla Hashicorp, enrecordeu-vos que Terraform ara es diu OpenTofu 😉 </p><p><a href="https://www.techpowerup.com/333240/ibm-completes-acquisition-of-hashicorp-creates-comprehensive-end-to-end-hybrid-cloud-platform" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">techpowerup.com/333240/ibm-com</span><span class="invisible">pletes-acquisition-of-hashicorp-creates-comprehensive-end-to-end-hybrid-cloud-platform</span></a></p><p><a href="https://mastodon.social/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IBM</span></a> <a href="https://mastodon.social/tags/Hashicorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hashicorp</span></a> <a href="https://mastodon.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> <a href="https://mastodon.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a></p>
Disco3000<p><span class="h-card" translate="no"><a href="https://geeknews.chat/@theregister" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>theregister</span></a></span> I hear good things about <a href="https://climatejustice.social/tags/Lidlcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Lidlcloud</span></a> in the industry. With <a href="https://climatejustice.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a> or <a href="https://climatejustice.social/tags/openTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openTofu</span></a> it would be easy to move. Disaster recovery exercises should anyways be done regularly so teams should have trust in their scripting. The pain points are the components where a vendor lock-in exists, which would need to be recreated with FOSS. That said I know of at least 3 bigger projects where they move back from public cloud to on-premise again.</p>
hobbsc<p>wrasslin' with <a href="https://social.sdf.org/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a> today. it seems to be just as good as <a href="https://social.sdf.org/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a>, though once in a while i'll hit a snag.</p>
Alejandro Baez<p>Starting to look at using <a href="https://fosstodon.org/tags/opentofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opentofu</span></a>. Compatibility seems ripe, and features are starting to grow. Before <a href="https://fosstodon.org/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> and it diverge too much, this may be the time. 😎</p><p>Of course, I could always go the <a href="https://fosstodon.org/tags/pulumi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pulumi</span></a> route again. But it do feel like rebuilding the wheel. 😅</p>
A Sysadmin, but not *your* Sysadmin<p>My employer is continuing to pursue increased sales to the US government, so for ethical reasons I'm fully on the job market now.</p><p>I am an experienced <a href="https://infosec.exchange/tags/devOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>devOps</span></a> engineer, having worked exclusively with <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AWS</span></a>. I have extensive experience in <a href="https://infosec.exchange/tags/terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terraform</span></a> and <a href="https://infosec.exchange/tags/openTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openTofu</span></a> with significant <a href="https://infosec.exchange/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ansible</span></a> work as well. I've used the full alphabet soup of AWS services: VPC, EC2, S3, ACM, KMS, IAM, RDS, Route53, SNS, SES, SQS, WAF, and many more. I also am familiar with the various monitoring, alerting, and on-call platforms, most notably CloudWatch, DataDog, and Pager Duty. I also have management and project management experience, leading teams and projects at the application and architectural levels.</p><p>I do not, unfortunately, have experience with K8s or EKS, so any potential position would need to accept a ramp-up time if those are part of the infrastructure ecosystem. I am a fast learner, and I have a solid engineering expertise to build off of.</p><p>My primary need is a fully <a href="https://infosec.exchange/tags/remote" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>remote</span></a> position for family reasons. As my profile states, I am based in the Twin Cities area in US Central time. I am fully authorized to work in the US without employer support.</p><p>I'm happy to answer any other questions folks may have, and I can provide my resume upon request. Thanks in advance for boosts and such!</p><p><a href="https://infosec.exchange/tags/FediHire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FediHire</span></a> <a href="https://infosec.exchange/tags/fedihired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fedihired</span></a> <a href="https://infosec.exchange/tags/getfedihired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>getfedihired</span></a></p>
Wolfensteijn<p>Using trial and error to teach myself terraform.</p><p>Equal parts fun and frustrating. Every fix a new error pops up. But I am slowly getting where I want to be. Having something working, and a bigger understanding of what I am actually doing.</p><p><a href="https://urface.social/tags/HomeLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HomeLab</span></a> <a href="https://urface.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terraform</span></a> <a href="https://urface.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenTofu</span></a> <a href="https://urface.social/tags/Talos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Talos</span></a> <a href="https://urface.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kubernetes</span></a> <a href="https://urface.social/tags/PVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PVE</span></a> <a href="https://urface.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a> <a href="https://urface.social/tags/LearningByDoing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LearningByDoing</span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload