<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://cilginc.github.io/</id><title>cilgin</title><subtitle>My blog site for my DevOps blogs such as Kubernetes, Docker and Linux.</subtitle> <updated>2025-09-20T15:28:31+03:00</updated> <author> <name>cilgin</name> <uri>https://cilginc.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://cilginc.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://cilginc.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2025 cilgin </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>How To Make Terraform S3 Backend using Terraform</title><link href="https://cilginc.github.io/posts/HowToMake-TerraformS3Backend/" rel="alternate" type="text/html" title="How To Make Terraform S3 Backend using Terraform" /><published>2025-09-19T22:23:07+03:00</published> <updated>2025-09-19T22:23:07+03:00</updated> <id>https://cilginc.github.io/posts/HowToMake-TerraformS3Backend/</id> <content type="text/html" src="https://cilginc.github.io/posts/HowToMake-TerraformS3Backend/" /> <author> <name>cilgin</name> </author> <category term="IaC" /> <category term="DevOps" /> <category term="Cloud" /> <summary>Hello there! Ever found yourself in a bit of a pickle with Terraform state management, especially when working with a team or CI/CD? You’re not alone! In this guide, we’re going to walk through how to set up a super robust and reliable Terraform state management backend using AWS S3 for storage and DynamoDB for state locking. Why Even Bother with a Remote Backend? You might be thinking, “Hey...</summary> </entry> <entry><title>TryHackMe: Creative</title><link href="https://cilginc.github.io/posts/TryHackMe-Creative/" rel="alternate" type="text/html" title="TryHackMe: Creative" /><published>2025-07-11T13:01:01+03:00</published> <updated>2025-07-11T15:38:35+03:00</updated> <id>https://cilginc.github.io/posts/TryHackMe-Creative/</id> <content type="text/html" src="https://cilginc.github.io/posts/TryHackMe-Creative/" /> <author> <name>cilgin</name> </author> <category term="CyberSecurity" /> <summary>Hey everyone! Welcome to another adventure in the land of TryHackMe. Today, we’re diving headfirst into the Creative room. Let’s pop open a terminal, get our IP, and see what kind of creative trouble we can get into. First things first, let’s set our target IP as an environment variable so we don’t have to type it out a million times. Efficiency is key! export IP=10.10.86.65 Step 1: Reconna...</summary> </entry> <entry><title>TryHackMe: WhyHackMe</title><link href="https://cilginc.github.io/posts/TryHackMe-WhyHackMe/" rel="alternate" type="text/html" title="TryHackMe: WhyHackMe" /><published>2025-07-10T13:56:25+03:00</published> <updated>2025-07-10T16:36:09+03:00</updated> <id>https://cilginc.github.io/posts/TryHackMe-WhyHackMe/</id> <content type="text/html" src="https://cilginc.github.io/posts/TryHackMe-WhyHackMe/" /> <author> <name>cilgin</name> </author> <category term="CyberSecurity" /> <summary>Hey everyone, and welcome to another CTF adventure! Today, we’re diving into the TryHackMe WhyHackMe room. This was a really fun box with a few twists and turns. So grab your coffee, fire up your terminal, and let’s get hacking! Step 1: Reconnaissance - The Digital Knock on the Door First things first, let’s set our target IP address as a variable. This saves us from a world of copy-pasting p...</summary> </entry> <entry><title>TryHackMe: The London Bridge</title><link href="https://cilginc.github.io/posts/TryHackMe-The_London_Bridge/" rel="alternate" type="text/html" title="TryHackMe: The London Bridge" /><published>2025-07-09T16:34:38+03:00</published> <updated>2025-07-09T16:35:08+03:00</updated> <id>https://cilginc.github.io/posts/TryHackMe-The_London_Bridge/</id> <content type="text/html" src="https://cilginc.github.io/posts/TryHackMe-The_London_Bridge/" /> <author> <name>cilgin</name> </author> <category term="CyberSecurity" /> <summary>Hey everyone! Today, I’m tackling the The London Bridge room on TryHackMe. The goal is to see if we can make this bridge fall down (metaphorically, of course!). So grab a cup of tea, and let’s get hacking! Step 1: Reconnaissance - Knocking on the Door First things first, let’s set our target IP address. This makes life way easier than typing it out every single time. export IP=10.10.22.48 ...</summary> </entry> <entry><title>TryHackMe: Rabbit Store</title><link href="https://cilginc.github.io/posts/TryHackMe-Mayhem/" rel="alternate" type="text/html" title="TryHackMe: Rabbit Store" /><published>2025-07-08T13:57:28+03:00</published> <updated>2025-07-08T17:08:26+03:00</updated> <id>https://cilginc.github.io/posts/TryHackMe-Mayhem/</id> <content type="text/html" src="https://cilginc.github.io/posts/TryHackMe-Mayhem/" /> <author> <name>cilgin</name> </author> <category term="CyberSecurity" /> <summary>Hey everyone, and welcome to another cybersecurity write-up! Today, we’re strapping on our detective hats and diving into the TryHackMe Mayhem room. The name suggests chaos, and our job is to make sense of it. This room is all about network forensics, so let’s get ready to dissect some packets! The First Clue: The Pcap File Our journey begins after unzipping the challenge file. Inside, we f...</summary> </entry> </feed>
