---
title: "Jan Tymiński (@tymik) | Hashnode"
description: "♾️ DevOps ☁️ AWS 🐳 Docker, Terraform, Automation. Read the latest articles by Jan Tymiński on Hashnode."
url: "https://hashnode.com/@tymik"
---

@tymik

# Jan Tymiński

@tymik · Poland · Joined March 2023

♾️ DevOps ☁️ AWS 🐳 Docker, Terraform, Automation

[Website](https://tymik.me/)

## Comments

[Great article!](https://hashnode.com/posts/taking-a-look-at-aws-sqs-short-and-long-polling/63e669ba5fdcc23c37d1af52/comment/65e8d5573da0335c11f13bfb)

Comment · Article · Mar 6, 2024 · [Taking a look at AWS SQS Short and Long Polling](https://hashnode.com/posts/taking-a-look-at-aws-sqs-short-and-long-polling/63e669ba5fdcc23c37d1af52)

[Thank you for the clarification Tomek! I was not really aware of the networking specifics that cause the behaviour of using all protocols, I'm not that fluent with networks - and I believe more people might also not understand the underlying reason so your comment brings a great value here! I had successfully set -1 as protocol with Terraform but perhaps I used older provider when I did so - unfortunately I'm not able to verify that anymore as I don't continue that project.](https://hashnode.com/posts/aws-security-groups-are-tricky/659401cb71deca9b06d6128d/comment/65d0803ad51c276bbe61d2b8#reply-65d0a16d28d5736666e771cb)

Reply · Article · Feb 17, 2024 · [AWS Security Groups are tricky!](https://hashnode.com/posts/aws-security-groups-are-tricky/659401cb71deca9b06d6128d)

[I hope it's more clear now and I'm glad you asked!](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010#reply-64ba37d42e3477ebf6133bd2)

Reply · Article · Jul 21, 2023 · [Migrate from CloudFormation to Terraform](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528)

[Thank you for the question! The Tale of the CloudFormation is there to explain it a little - the CF code was built through years by many people that were more or less experienced with the CloudFormation and eventually it became really hard to maintain - unmaintained, not up to date, tons of drifts, etc... Then there was an internal team built for taking care of all the infrastructure, with expertise in Terraform and inability to dive into existing CloudFormation stacks in any reasonable time. Terraform has just some little inconveniences that the team is aware of and we decided it's easier for us to get rid of CloudFormation as it was easier to achieve than fixing all the stacks - especially when not being experts in them. To make things more complicated, there were parts of the infrastructure in Terraform too - but in a similar state as CF stacks and we decided to not reanimate them but build new code from scratch on what we actually see in the infrastructure.](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010#reply-64a297f08db091c401037181)

Reply · Article · Jul 3, 2023 · [Migrate from CloudFormation to Terraform](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528)
