<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Oguzhan Coskun on Medium]]></title>
        <description><![CDATA[Stories by Oguzhan Coskun on Medium]]></description>
        <link>https://medium.com/@blakk?source=rss-24f9d85e8135------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PLoLuEpHFUgN2Bt1LirgiQ@2x.jpeg</url>
            <title>Stories by Oguzhan Coskun on Medium</title>
            <link>https://medium.com/@blakk?source=rss-24f9d85e8135------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:44:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@blakk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Cockpit on My Desk: A DIY X-Plane 12 Switch Panel with a Raspberry Pi Pico]]></title>
            <link>https://blakk.medium.com/a-cockpit-on-my-desk-a-diy-x-plane-12-switch-panel-with-a-raspberry-pi-pico-3e3d3b9a4991?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e3d3b9a4991</guid>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[flight-simulator]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[electronics]]></category>
            <category><![CDATA[3d-printing]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 12:06:43 GMT</pubDate>
            <atom:updated>2026-10-08T12:07:22.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dA15yvXlAKFKgSAvR16wVQ.png" /></figure><h3>Why I didn’t just buy the modules</h3><p>Over one weekend, with a cheap Raspberry Pi Pico clone and a handful of toggle switches, I built an 8-switch panel that powers up my aircraft in X-Plane 12 the way a real cockpit does. After getting the Logitech/Saitek G Pro Flight Yoke, the next step looked obvious: the switch panel, the radio panel, the multi panel. Instead of buying all of them, I wanted to build one myself.</p><p>My question was simple: is this ecosystem closed, or can a Pico from my drawer become a module of my own? It turns out to be completely open. This post walks through every step from idea to working panel, including the mistakes and how I fixed them. I worked through the whole process with an AI assistant (Claude): parts, code, 3D model and X-Plane settings included.</p><h3>The idea: turn the Pico into a joystick</h3><p>Logitech’s panels don’t plug into the yoke; each one is a separate USB device on the computer. So my module only had to be a USB device the computer recognises. I never needed to touch Logitech’s closed protocol.</p><p>The cleanest route is for the Pico to present itself as a <strong>USB joystick (HID)</strong>. That means:</p><ul><li>X-Plane sees it on the <em>Settings → Joystick</em> screen like any other joystick.</li><li>No driver or plugin is needed, and it works on macOS as well as Windows.</li><li>Every switch position maps to a button, and each button gets one of X-Plane’s own commands.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NmxJGF8X0nKfYyibm9ztJg.png" /></figure><p>The Pico only reads switches and sends button presses; X-Plane decides what each button does. It plugs into the USB hub on the back of the yoke or straight into the Mac. Anything that reads data from the sim (an attitude indicator screen, for example) will come later through a different path, X-Plane’s UDP or web API. This first panel only sends input.</p><h3>Parts list</h3><p>The whole panel is built from the parts below; apart from a soldering iron, no special tools were needed.</p><ul><li><strong>1 × Raspberry Pi Pico clone</strong> (RP2040, USB-C), male headers soldered on</li><li><strong>7 × MTS-102 mini toggle switch</strong> (ON-ON), 6 mm bushing, panel mount</li><li><strong>1 × MTS-103 mini toggle switch</strong> (ON-OFF-ON), for the LAND / OFF / TAXI lights</li><li><strong>8 × 5 mm diffused LED</strong>: green, amber, red</li><li><strong>8 × 330 Ω resistor</strong>, one per LED</li><li><strong>1 × 830-point breadboard</strong>, 160 × 60 × 10 mm</li><li><strong>~35 male-to-male jumper wires</strong>, one end cut off and soldered to the switch</li><li><strong>Heat-shrink tubing</strong> to cover the solder joints</li><li><strong>5 × M3 × 21 mm screws</strong> for the lid</li><li><strong>3D-printed enclosure</strong> (PLA): base + lid, fits a 180 × 180 mm bed</li></ul><p>The “6A 125VAC” printed on the switches is only their maximum rating; it means nothing at the Pico’s 3.3 V. For the LEDs I picked red, amber and classic green over white and blue: colours that need a higher forward voltage glow dimly at 3.3 V.</p><h3>Software: CircuitPython instead of Arduino</h3><p>To avoid installing any toolchain on my Mac I used <strong>CircuitPython</strong> instead of Arduino. Plugging the Pico in while holding BOOTSEL mounts a drive called RPI-RP2; dragging the ~2 MB CircuitPython .uf2 file onto it makes the Pico come back as a CIRCUITPY drive. The code is a plain text file on that drive: save it and it runs immediately, no compiling.</p><p>The code is two files:</p><ol><li><strong>boot.py</strong> runs once at power-up and presents the Pico as a joystick called “DIY Switch Panel”, with 32 buttons and no axes.</li><li><strong>code.py</strong> reads the switches continuously; when a switch changes position it sends a 150 ms pulse on that position’s button and turns the LED on or off.</li></ol><p>Why a short pulse instead of holding the button? X-Plane runs a command at the moment a button is pressed, while a toggle switch stays where you leave it. So I turned every switch into two buttons: one when it goes ON, another when it goes OFF. That lets me assign separate commands such as battery_1_on and battery_1_off.</p><p>The whole panel is configured in one list:</p><pre># (label, input pins, LED pin, buttons per position)<br>SWITCHES = [<br>    (&quot;ENGINE&quot;,    (board.GP0,), board.GP16, ((1,), (2,))),<br>    (&quot;BATT&quot;,      (board.GP1,), board.GP17, ((3,), (4,))),<br>    (&quot;ALT&quot;,       (board.GP2,), board.GP18, ((5,), (6,))),<br>    (&quot;AVIONICS&quot;,  (board.GP3,), board.GP19, ((7,), (8,))),<br>    (&quot;FUEL PUMP&quot;, (board.GP4,), board.GP20, ((9,), (10,))),<br>    (&quot;BEACON&quot;,    (board.GP5,), board.GP21, ((11,), (12,))),<br>    (&quot;NAV&quot;,       (board.GP6,), board.GP22, ((13,), (14,))),<br>    # GP7 = up, GP8 = down<br>    (&quot;LAND/OFF/TAXI&quot;, (board.GP7, board.GP8), board.GP26,<br>        ((15, 18), (16, 18), (17, 16))),<br>]</pre><p>Every position of the three-way switch on the last line presses <strong>two buttons at once</strong>. X-Plane allows only one command per button, so this is the only way to get behaviour like “in the middle, turn off both the landing and the taxi light”. Button 18 has no physical counterpart at all: it is a virtual button pressed purely by the code.</p><h3>Wiring: GP pins and GND only</h3><p>Nothing in this project connects to the 3V3 pin; every connection runs between a GP pin and GND. The trick is the Pico’s internal <strong>pull-up</strong> resistor: enabled in code, it holds the pin at 3.3 V from the inside. When the switch closes, the pin is pulled to GND and the Pico reads that as “ON”.</p><ul><li><strong>ON-ON switch:</strong> middle leg to GND, one outer leg to a GP pin, the other outer leg unused. Which outer leg you pick only decides which lever direction counts as ON; I made it up = ON, as in real aircraft.</li><li><strong>ON-OFF-ON switch:</strong> all three legs are used. Middle leg to GND, the outer legs to two separate GP pins. In the middle both pins stay open, which the Pico reads as OFF.</li><li><strong>LED:</strong> GP pin → 330 Ω resistor → the LED’s long leg; short leg to GND. With 3.3 V and a red LED that is about 4 mA per LED, comfortably within the Pico’s limits even with all 8 lit.</li><li><strong>Common GND:</strong> the breadboard’s blue (−) rails collect every GND wire. One GND pin on each side of the Pico feeds the rail on its side.</li></ul><p>The switches sit on one edge of the Pico (GP0–GP8) and the LEDs on the other (GP16–GP22 and GP26). The wires don’t cross, and 9 pins stay free for encoders later.</p><p>The switch legs are not made for a breadboard; these are panel-mount switches. I cut one end off male-to-male jumpers and soldered it to the switch and LED legs; the other end plugs into the breadboard. There is no soldering on the Pico side at all. The one rule: slide the heat-shrink onto the wire <strong>before</strong> you solder.</p><h3>Problems I hit</h3><p>Not everything worked the first time. The four problems that cost the most time, and their fixes:</p><p><strong>1. Nothing happens when the Pico is plugged into the Mac, not even the LED.</strong><br><em>Cause:</em> some cheap USB-C Pico clones lack the CC resistors USB-C requires; over a C-to-C cable the Mac never powers the board.<br><em>Fix:</em> go through USB-A: Apple’s USB-C Multiport adapter or the yoke’s USB-A hub.</p><p><strong>2. One switch’s LED stays dark while another one lights up.</strong><br><em>Cause:</em> on the LED side of the Pico there is a GND pin between GP17 and GP18; plugging in “in order” swapped two LEDs.<br><em>Fix:</em> swap the two LED pins in the code instead of rewiring.</p><p><strong>3. The ALT switch sends no signal at all.</strong><br><em>Cause:</em> a connection fault on the switch side; the Pico, code and LED all checked out.<br><em>Fix:</em> short GP2 to GND with a jumper to prove the Pico side, then check the switch’s wires and solder joints.</p><p><strong>4. The taxi light stays on in the middle position.</strong><br><em>Cause:</em> X-Plane allows only one command per button.<br><em>Fix:</em> make every position press two buttons at once.</p><p>The most useful debugging tool was the Pico’s serial output. Every switch movement prints a line like ALT -&gt; 0 buttons (5,), so you can see at a glance which switch sends a signal and which doesn&#39;t. For LED problems, stopping the code and driving a single pin high by hand was enough to tell a code problem from a wiring problem.</p><h3>The 3D-printed enclosure</h3><p>The box is 170.4 × 120.4 × 40 mm and fits a 180 × 180 mm print bed with about 5 mm to spare on each side. It is generated by a parametric Python script; when a measurement changes, I rerun the script and get new STLs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ExclN4fgpRv6_kzRV4y85g.png" /></figure><p>The box has two zones. The Pico and the jumper ends on the breadboard rise about 20 mm, and the switch bodies hang about 22 mm below the lid. Stacking them would make the box far too tall, so they sit side by side:</p><ul><li><strong>Front zone:</strong> 8 switches at 20 mm spacing, an LED behind each, engraved labels in front. “ENGINE &amp; ELECTRICAL” and “LIGHTS” group headers above them.</li><li><strong>Rear zone:</strong> a low 3 mm frame that keeps the breadboard in place, and an opening in the left wall for the Pico’s USB.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_L0FcIDpnm_iZUm-l1YGLw.png" /></figure><p>The first print needed two fixes:</p><ol><li><strong>The USB opening was too high.</strong> The top of the Pico’s USB port turned out to sit 12 mm above the floor. I lowered the opening to 6–15 mm and sized it at 12 × 9 mm for the 10.5 × 7.5 mm plug head.</li><li><strong>The screw holes were too shallow.</strong> My M3 × 21 mm screws pass the lid and go 18 mm into the base; 14 mm holes were not enough. I deepened them to 22 mm and widened them to 2.6 mm.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TsVR32kooFt7vce7huj5fg.png" /></figure><p>A flat box this size likes to lift at the corners. In Bambu Studio, setting <em>Others → Brim type</em> to <strong>Mouse ear</strong> adds small pads only at the corners. Washing the build plate with dish soap to get rid of fingerprints helps at least as much.</p><h3>X-Plane 12 integration</h3><p>The panel shows up in X-Plane as “DIY Switch Panel”, and its 18 buttons map to X-Plane’s own commands:</p><ul><li><strong>ENGINE:</strong> sim/operation/auto_start / sim/magnetos/magnetos_off</li><li><strong>BATT:</strong> sim/electrical/battery_1_on / sim/electrical/battery_1_off</li><li><strong>ALT:</strong> sim/electrical/generator_1_on / sim/electrical/generator_1_off</li><li><strong>AVIONICS:</strong> sim/systems/avionics_on / sim/systems/avionics_off</li><li><strong>FUEL PUMP:</strong> sim/fuel/fuel_pump_1_on / sim/fuel/fuel_pump_1_off</li><li><strong>BEACON:</strong> sim/lights/beacon_lights_on / sim/lights/beacon_lights_off</li><li><strong>NAV:</strong> sim/lights/nav_lights_on / sim/lights/nav_lights_off</li><li><strong>LAND / OFF / TAXI:</strong> up = landing on + taxi off; middle = landing off + taxi off; down = taxi on + landing off</li></ul><p>In X-Plane the alternator is called “generator”. I checked every command name against X-Plane’s own Resources/plugins/Commands.txt.</p><h3>The settings are just a text file</h3><p>X-Plane keeps every joystick assignment in one plain text file: Output/preferences/X-Plane Joystick Settings.prf. Each device&#39;s buttons live in a numbered block; the yoke has 0–159, the panel 160–319. That has three practical consequences:</p><ul><li><strong>Backup:</strong> copying this file (and X-Plane Keys.prf, which holds the keyboard shortcuts) backs up every assignment.</li><li><strong>Direct editing:</strong> assignments can be changed in the file instead of clicking through X-Plane.</li><li><strong>One catch:</strong> X-Plane writes its settings to disk only when it quits. Edit the file while X-Plane is closed, or it gets overwritten on exit.</li></ul><h3>Cleaning up the yoke</h3><p>The Saitek Pro Flight Yoke profile in X-Plane’s Resources/joystick configsfolder says which button number is which physical control. With it I reviewed the existing assignments and changed six lines:</p><ul><li><strong>E trigger → wheel brakes</strong> (brakes_regular, held). With no rudder pedals there were no brakes besides the parking brake.</li><li><strong>Detent at the bottom of the throttle levers → reverser</strong>(thrust_reverse_hold). On while the lever sits in the detent, off when it leaves.</li><li><strong>T5 / T6 → autopilot toggle and disconnect.</strong> The landing light moved to the panel, which freed these two.</li><li><strong>Reset on the clock panel → unassigned.</strong> The red lever is already the speedbrake axis, so the speedbrake toggle there was redundant.</li></ul><h3>Files and code</h3><p>Everything you need to build your own is in one GitHub repository:</p><p><a href="https://github.com/oguzhancoskun/xplane-pico-switch-panel">github.com/oguzhancoskun/xplane-pico-switch-panel</a></p><ul><li>pico/boot.py and pico/code.py: the CircuitPython firmware, copied straight onto the CIRCUITPY drive.</li><li>enclosure/base.stl and enclosure/lid.stl: print-ready, no supports needed. GitHub shows them as rotatable 3D previews in the browser.</li><li>enclosure/build.py: the parametric script that generates the STLs. Change the breadboard size, switch spacing or labels and rerun it.</li></ul><h3>What’s next</h3><p>I now bring the Cessna 172 to life step by step, the way you would in the cockpit: BATT, FUEL PUMP, BEACON, then ENGINE. Every switch lights its LED, and the switches in X-Plane move with it. Next on the list:</p><ul><li><strong>LEDs in sync with the sim.</strong> Today the LEDs show the switch position. A small script on the Mac could read the aircraft state from X-Plane’s web API and send it to the Pico, so the LEDs show the real state. The switch positions could also be written straight into the sim, so the two never drift apart.</li><li><strong>A more realistic ENGINE switch.</strong> Magnetos and starter instead of auto_start, to start the engine with the real procedure.</li><li><strong>An encoder panel.</strong> Two rotary knobs for heading and altimeter on the 9 free pins.</li><li><strong>An attitude indicator screen.</strong> A separate module with an ESP32 and a 1.28&quot; round display, fed by X-Plane over WiFi.</li></ul><p>If you have a yoke at home and a Pico in a drawer, the first step is one switch and one evening. A Pico that shows up as a joystick opens X-Plane’s door completely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1A_9Q6j8DxDIt0fD5W_ezA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_PHgjfZlO2HtrUrWFQOzQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e3d3b9a4991" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiro.dev: Free 1-Year Enterprise for Startups via AWS]]></title>
            <link>https://blakk.medium.com/kiro-dev-free-1-year-enterprise-for-startups-via-aws-f1408953f62a?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1408953f62a</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[iam-identity-center]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[kiro]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 23:22:34 GMT</pubDate>
            <atom:updated>2025-12-22T23:22:34.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k8C1oX7H7wwdaSJ7qfDgag.jpeg" /></figure><p>In recent years, AWS ecosystem has started offering serious advantages especially for startups. Besides its strong position in cloud computing, it stands out with comprehensive support programs and incentives that help startups grow in early stages. AWS is not just an infrastructure provider; through platforms like Startups, Partner Central, Community Hub, and Skill Builders, it supports innovative projects with a wide community.</p><p>I’ve been working closely with AWS ecosystem for over 10 years. Both my own projects, my clients, and the companies I worked for were mostly shaped on AWS. During this time, I closely observed how AWS’s scalable infrastructure and AI services evolved.</p><p>AI and machine learning growth exploded especially in the last 4–5 years. I first saw AWS’s investment in this area 4 years ago at AWS re:Invent in Las Vegas. There I realized Amazon is not just developing AI products, but also building a strong ecosystem for developers.</p><p>In this context, <strong>Kiro.dev</strong> became one of the innovations that excites me most. Positioned as an agentic IDE, Kiro is a project developed within AWS team and continues to grow rapidly. Despite serious competition in agentic coding world, Kiro meets many current needs with a simple and smart approach. I’ve been using it actively for a while and find it more than sufficient for my workflow.</p><p>Honestly, I always see agentic IDEs as a “helper layer.” Instead of making everything autonomous from scratch, I use them to optimize existing projects, organize repetitive tasks, or speed up development. Kiro fits me perfectly in this aspect.</p><h3>What is AWS Startups?</h3><p>AWS Startups is a platform that supports startups from early stage to growth phase with both cloud credits and partner ecosystem. The main goal of this program is to help you test your product faster even when it’s just an idea, prototype, or MVP, automate repetitive tasks, and shorten time-to-market.</p><p>You can access AWS Startups homepage at <strong>startups.aws</strong>. Here you can access both AWS Activate credit programs and “Offers” section with special deals for dozens of third-party tools. Through this page, you record your startup and track suitable credits, mentorships, and partner opportunities from one place based on your stage.</p><h3>Profile Setup and Credit Options</h3><p>First, you need to create a personal and company profile on AWS Startups side. In short: you match your company info, domain, stage (idea, prototype, MVP, early revenue, growth etc.), and your AWS account with this profile.</p><p>Through this profile:</p><ul><li>You can apply for AWS Activate credits for idea, prototype, or MVP stage projects. Early stage founders can get from $1,000 level up to $100,000 with portfolio programs.</li><li>Also in AWS Activate Exclusive Offers, you find many partner benefits like few months free/discounted Pro plans for Notion, $400 cloud credits for ClickHouse services etc.</li><li>When you explain your idea and use case to AWS, you can get instant credits (like $1,000 levels) for use in your account through certain programs.</li></ul><p>Especially in early stage, running both infrastructure and surrounding SaaS tools with credits as much as possible is quite critical to extend runway.</p><h3>Advanced Stages and Investment Side</h3><p>When your project reaches certain maturity — meaning beyond MVP, starting to generate revenue, or entering growth phase — AWS ecosystem opens different doors.</p><ul><li>With higher segment programs of AWS Activate, you have chance to get up to $100,000 cloud credits and additional support credits.</li><li>Through Global Startup Program and similar initiatives, you can more easily access AWS’s own investor and partner network, catch investor meetings and co-sell opportunities.</li></ul><p>In short, it has a support structure that extends from go-to-market, sales, and investment side, not just “let me get credits and run servers cheaply.”</p><h3>Kiro’s AWS Startups Offer</h3><p>Within all this ecosystem, Kiro.dev currently has a very attractive, time-limited offer. If you apply through AWS Startups until December 31, 2025, there’s a credit program where you can use <strong>Kiro Enterprise</strong> free for one year.</p><p>Kiro Startup Credits Program offers three levels:</p><ul><li><strong>Starter Tier</strong>: Up to 2 Kiro users</li><li><strong>Growth Tier</strong>: Up to 50 Kiro users</li><li><strong>Scale Tier</strong>: Up to 100 Kiro users</li></ul><p>These credits are automatically assigned to approved startups’ AWS accounts and cover Kiro Pro+ licenses for one year. If you choose extra users or Pro+ above plan, difference goes to billing.</p><h3>Requirements for Kiro Pro+ Credits</h3><p>There are some basic requirements to apply for this Pro+ credit offered by Kiro through AWS Startups:</p><ul><li>Your startup stage should be from “we have an idea and some funding” level up to maximum <strong>Series B</strong>.</li><li>Your AWS account must match your company domain; meaning use enterprise AWS account instead of personal one.</li><li>You need to apply with your real business email (like <em>@company.com</em>).</li></ul><p>If you meet these conditions, you can start the process with short application form by selecting Kiro offer through your AWS Startups profile. After approval, you get chance to experience Kiro in agentic coding with your whole team for one year without serious cost consideration.</p><h3>Kiro Credit Activation: Critical Points</h3><p>After Kiro Pro+ credit application through AWS Startups is approved, process completes in few days. Usually approval email comes or they may want short call; then credits are directly assigned to your linked AWS account. You’ll receive notification email to AWS account saying “Kiro credits assigned” after credit activation.</p><p>Here are 4 critical points to watch:</p><ol><li><strong>AWS Startups Profile Account Linking</strong><br>Link the AWS account matching your company domain correctly in AWS Startups profile. If you specify wrong account, credits go there and transfer is not possible. Double-check AWS Account ID while creating profile.</li><li><strong>Credit Assignment Notification</strong><br>When credits assigned, clear approval email comes to email linked with AWS account: “Kiro credits assigned to this AWS account.” You can pass to Kiro side after seeing this email. You can also track credit usage from AWS Billing Dashboard.</li><li><strong>Login to Kiro with “Organization Identity”</strong><br>Don’t login to Kiro with personal account, use “Sign in with your organization identity” option. For this, you first need to activate <strong>IAM Identity Center</strong> in your AWS account.<br>• After activating IAM Identity Center, add your company domain (like company.com) here.<br>• On Kiro login screen, auth using IAM Identity Center URL.</li><li><strong>IAM User Creation and Login</strong><br>After IAM Identity Center is active:<br>• Create IAM users for your team members from Users section (each with own username/password).<br>• Download Kiro IDE, open and login with IAM credentials (username + password).<br>• Root user setup recommended; invite emails will come for IAM users.</li></ol><p>When these steps completed, your 1-year Kiro Enterprise credit (2–100 users based on selected tier) becomes active and billing automatically deducts from credits. Process is a bit technical but works smoothly for your team once setup.</p><h3>Conclusion: Apply Now, Don’t Miss</h3><p>AWS Startups and Kiro.dev combination is a rare opportunity for every startup wanting to transition to agentic coding. With 10+ years AWS experience I say: These credits are not just cost saving, but infrastructure investment that will make your team productive fast.</p><p>To meet December 31, 2025 deadline, create your profile at startups.aws today, select Kiro offer and apply. From Starter to Scale Tier, 1-year Enterprise license according to your team size is in your pocket.</p><p><strong>Resources &amp; Links</strong></p><ul><li><a href="https://startups.aws/">AWS Startups Homepage</a></li><li><a href="https://aws.amazon.com/startups/learn/power-your-startup-with-1-year-of-kiro-pro-plus-now-available-through-aws-startups">Kiro AWS Startups Offer</a></li><li><a href="https://kiro.dev/docs/enterprise/iam/">Kiro IAM Docs</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1408953f62a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your AI Model Is About to Expire — Move to Nova Canvas Before It’s Gone]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/your-ai-model-is-about-to-expire-move-to-nova-canvas-before-its-gone-46fcc192ba89?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/1280/1*rY_JtpUiPzKoEGdb9hKZ1A.png" width="1280"></a></p><p class="medium-feed-snippet">AWS announced that some Titan models will stop working soon, including Titan Image Generator G1 V1. The last working date is January 31&#x2026;</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/your-ai-model-is-about-to-expire-move-to-nova-canvas-before-its-gone-46fcc192ba89?source=rss-24f9d85e8135------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/your-ai-model-is-about-to-expire-move-to-nova-canvas-before-its-gone-46fcc192ba89?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/46fcc192ba89</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[image-processing]]></category>
            <category><![CDATA[nova-canvas]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Sun, 19 Oct 2025 22:51:34 GMT</pubDate>
            <atom:updated>2025-10-21T18:12:27.973Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Full Metal DevOps 2.0: Modern Codeware]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/full-metal-devops-2-0-modern-codeware-a97750b6a68a?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/2600/1*eqbX-Yk0Ie9Cw3A8waP7cg.jpeg" width="5376"></a></p><p class="medium-feed-snippet">Before we begin, if you are wondering what FMD1 (Full Metal DevOps 1.0) is, you can check it here:</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/full-metal-devops-2-0-modern-codeware-a97750b6a68a?source=rss-24f9d85e8135------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/full-metal-devops-2-0-modern-codeware-a97750b6a68a?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/a97750b6a68a</guid>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Tue, 14 Oct 2025 21:22:52 GMT</pubDate>
            <atom:updated>2025-10-15T15:26:38.542Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Serverless to Sentiment: Designing a Modern AWS AI Stack]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/from-serverless-to-sentiment-designing-a-modern-aws-ai-stack-1e073eef28a4?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/1920/1*qxhUWmCgOaDssE-Vkc9kaw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">In the AWS ecosystem, using serverless options has both advantages and disadvantages. It gives a good foundation even for production&#x2026;</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/from-serverless-to-sentiment-designing-a-modern-aws-ai-stack-1e073eef28a4?source=rss-24f9d85e8135------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/from-serverless-to-sentiment-designing-a-modern-aws-ai-stack-1e073eef28a4?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e073eef28a4</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[bedrock]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Mon, 06 Oct 2025 23:40:24 GMT</pubDate>
            <atom:updated>2025-10-14T06:06:32.794Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Talent ≠ Keywords: Why Beating the ATS Felt Wrong]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blakk.medium.com/talent-keywords-why-beating-the-ats-felt-wrong-1bd5383c387a?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/1024/1*9mQwL0x6fc5C8rrzBGH_2Q.png" width="1024"></a></p><p class="medium-feed-snippet">Did you see the sparrow in the picture? Maybe not. The peacock looks big and colorful, so it gets all the attention. But the small sparrow&#x2026;</p><p class="medium-feed-link"><a href="https://blakk.medium.com/talent-keywords-why-beating-the-ats-felt-wrong-1bd5383c387a?source=rss-24f9d85e8135------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://blakk.medium.com/talent-keywords-why-beating-the-ats-felt-wrong-1bd5383c387a?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bd5383c387a</guid>
            <category><![CDATA[applicant-tracking-system]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[resume-optimization]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 21:43:58 GMT</pubDate>
            <atom:updated>2025-07-30T21:43:58.682Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Securing Redis in Transit: HAProxy as a TCP Proxy for AWS ElastiCache in Kubernetes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://aws.plainenglish.io/securing-redis-in-transit-haproxy-as-a-tcp-proxy-for-aws-elasticache-in-kubernetes-6615225cdbb6?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/1024/1*bxeKvxnmwzCzP0Djp7OxCQ.png" width="1024"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://aws.plainenglish.io/securing-redis-in-transit-haproxy-as-a-tcp-proxy-for-aws-elasticache-in-kubernetes-6615225cdbb6?source=rss-24f9d85e8135------2">Continue reading on AWS in Plain English »</a></p></div>]]></description>
            <link>https://aws.plainenglish.io/securing-redis-in-transit-haproxy-as-a-tcp-proxy-for-aws-elasticache-in-kubernetes-6615225cdbb6?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/6615225cdbb6</guid>
            <category><![CDATA[proxy]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[elasticache]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 20:15:29 GMT</pubDate>
            <atom:updated>2025-07-22T00:07:26.768Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Optimize Raspberry Pi OS for Mobility: Reduce Boot Time from Over 1 Minute to 30 Seconds]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blakk.medium.com/optimize-raspberry-pi-os-for-mobility-reduce-boot-time-from-over-1-minute-to-30-seconds-8ea65b919d3e?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/2600/1*f_xDho5jZXVELpqGJJEOVg@2x.jpeg" width="3024"></a></p><p class="medium-feed-link"><a href="https://blakk.medium.com/optimize-raspberry-pi-os-for-mobility-reduce-boot-time-from-over-1-minute-to-30-seconds-8ea65b919d3e?source=rss-24f9d85e8135------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://blakk.medium.com/optimize-raspberry-pi-os-for-mobility-reduce-boot-time-from-over-1-minute-to-30-seconds-8ea65b919d3e?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ea65b919d3e</guid>
            <category><![CDATA[3d-printing]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 18:00:25 GMT</pubDate>
            <atom:updated>2025-06-19T18:00:25.211Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Enhancing AWS EKS Cost Efficiency: Leveraging ENI Prefix Delegation for Optimal Resource…]]></title>
            <link>https://blakk.medium.com/enhancing-aws-eks-cost-efficiency-leveraging-eni-prefix-delegation-for-optimal-resource-cc3ae5b28e36?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc3ae5b28e36</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[prefix-delegation]]></category>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[cilium]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Thu, 27 Mar 2025 15:08:47 GMT</pubDate>
            <atom:updated>2025-04-02T15:18:25.048Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhancing AWS EKS Cost Efficiency: Leveraging ENI Prefix Delegation for Optimal Resource Utilization</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OSXcBerT9OSR-1uqTi90UA.jpeg" /></figure><p>In this article, we explain how AWS EKS can improve cost efficiency by using ENI Prefix Delegation. We focus on proper configuration and explain the concept in simple terms for beginners. We also discuss how to delegate from aws-node to Cilium and how to check if prefix delegation is correctly configured using a custom CDC script shared on GitHub.</p><p>If you are interested, here is my CDC script to check if delegation is working properly:<br><a href="https://gist.github.com/oguzhancoskun/aaf0484f2c426c1fd15b4a9fb85bf3ac">https://gist.github.com/oguzhancoskun/aaf0484f2c426c1fd15b4a9fb85bf3ac</a></p><h3>Understanding Prefix Delegation</h3><p>In the Kubernetes ecosystem, every node has a maximum number of pods. For example, if you use a t3a.large instance, it can handle up to 35 pods. However, when prefix delegation is enabled, this number can scale to 110 pods.<br>For more details about instance class pod limits, please check:</p><ul><li><a href="https://learnk8s.io/kubernetes-instance-calculator">Kubernetes instance calculator</a></li><li><a href="https://docs.aws.amazon.com/ec2/latest/instancetypes/gp.html?utm_source=chatgpt.com">Specifications for Amazon EC2 general purpose instances</a></li></ul><p>The pod count per node is calculated with the formula:<br><strong>Max ENIs * (IPs per ENI — 1) + 2</strong></p><p>For an m5.large instance:</p><ul><li>Maximum ENIs: 3</li><li>IP addresses per ENI: 10</li></ul><p>Calculation:<br>3 * (10–1) + 2 = 3 * 9 + 2 = 27 + 2 = 29</p><h3>How AWS Extends IP Blocks with Prefix Delegation</h3><p>In AWS EKS environments, enabling prefix delegation significantly increases the number of pods per node, especially for instance types with higher ENI support, such as m5.large instances. By default, these instances support only a limited number of Elastic Network Interfaces (ENIs) with a set number of IP addresses. When prefix delegation is enabled, each ENI receives a /28 IPv4 block, which provides 16 IP addresses per block. This configuration increases the number of pods per node, potentially up to 110, depending on the instance’s ENI limit, leading to more efficient resource use, reducing the need for extra nodes, and lowering operational costs. It also creates a scalable and flexible infrastructure for high-demand applications.</p><h3>Enable Prefix Delegation</h3><h4>1 . Setup vpc-cni</h4><pre>helm repo add eks https://aws.github.io/eks-charts &amp;&amp; helm repo update &amp;&amp; helm search repo aws-vpc-cni -l | cat</pre><pre>helm install aws-vpc-cni eks/aws-vpc-cni --namespace kube-system --version 1.19.2 --set env.ENABLE_PREFIX_DELEGATION=true -<br>-set-json &#39;nodeSelector={&quot;io.cilium/aws-node-enabled&quot;:&quot;true&quot;}&#39;</pre><p><strong>2. Important Considerations:</strong></p><ul><li>Choose AWS Nitro instance classes.</li><li>Set the amazon-vpc-cni environment variables:</li><li>ENABLE_PREFIX_DELEGATION=true</li><li>WARM_PREFIX_TARGET=1</li><li>The nodeSelector parameter prevents AWS VPC CNI pods from running if no nodes match the label io.cilium/aws-node-enabled=&#39;true&#39;</li></ul><p><a href="https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html">Instances built on the AWS Nitro System</a></p><p>Second point is, you need to set amazon-vpc-cni env var will be set to ENABLE_PREFIX_DELEGATION=true and WARM_PREFIX_TARGET=1 .</p><blockquote>AWS VPC CNI assigns a <strong>/28 IP block (prefix)</strong> to each EC2 node, providing <strong>16 IP addresses</strong>.<br>When WARM_PREFIX_TARGET=1 is set, it ensures that <strong>at least one available prefix per node</strong> is always maintained.</blockquote><blockquote>In the AWS EKS cluster, we wanted to use Cilium as the main networking plugin while disabling AWS VPC CNI without fully removing it. To do this, we used a <strong>Node Selector</strong> during the Helm installation. This setting forced aws-vpc-cni pods to run only on nodes with the label <strong>io.cilium/aws-node-enabled=true</strong>, but since no such nodes existed in our cluster, the pods were never started. As a result, AWS VPC CNI remained installed but inactive, allowing us to keep AWS dependencies intact while keeping the setup easily reversible if needed.</blockquote><h4>CDC Check</h4><p>If you clearly setup aws-vpc-cni you can run my shared cdc script for check which details exists/missing for prefix delegation.</p><p>Here is sample result;</p><pre>AWS EKS Cilium Prefix Delegation Check<br>───────────────────────────────────────────────────────────────────────────<br><br>                                                      Checking Requirements<br>───────────────────────────────────────────────────────────────────────────<br>✓ kubectl is installed<br>✓ ipcalc is installed<br>✓ jq is installed<br><br>                                                 Fetching Cluster Instances<br>───────────────────────────────────────────────────────────────────────────<br>☁ Cluster: example-test-cluster<br>ℹ Profile: example<br><br>                                                  Verifying Cluster Details<br>───────────────────────────────────────────────────────────────────────────<br>☁ Fetching cluster details...<br>✓ Cluster Status: ACTIVE<br>ℹ Kubernetes Version: 1.30<br>ℹ Platform Version: eks.28<br>☁ Checking node groups...<br>✓ Found node groups: nodegroup-01<br>☁ Checking Kubernetes nodes...<br>✓ Found 4 Kubernetes nodes<br><br>ℹ Node Details:<br>✓ ip-xxx.x-xx-1.compute.internal: True<br>✓ ip-xxx.x-xx-1.compute.internal: True<br>✓ ip-xxx.x-xx-1.compute.internal: True<br>✓ ip-xxx.x-xx-1.compute.internal: True<br>☁ Fetching EC2 instances...<br>ℹ Attempting to get instance ID from node name...<br>ℹ Found node private IP: xxx<br>✓ Found instance by private IP: i-xxx<br><br>                                   Checking Cilium Prefix Delegation Status<br>───────────────────────────────────────────────────────────────────────────<br>ℹ Checking Cilium configuration...<br>✓ Cilium CNI is active<br>⚠ Prefix delegation is not enabled in Cilium<br>ℹ To enable prefix delegation in Cilium:<br>🔧 1. Edit the cilium-config ConfigMap<br>🔧 2. Set enable-prefix-delegation: &quot;true&quot;<br>🔧 3. Restart Cilium pods to apply changes</pre><h4>Cilium Setup</h4><pre>&gt; helm repo add cilium https://helm.cilium.io/<br>&gt;  helm install cilium cilium/cilium \<br>  --version 1.14.5 \<br>  --namespace kube-system \<br>  --set eni.enabled=true \<br>  --set eni.subnetTagsFilter=cilium=true \<br>  --set ipam.mode=eni \<br>  --set eni.awsEnablePrefixDelegation=true \<br>   --set egressMasqueradeInterfaces=eth0 \<br>  --set nodeinit.enabled=false \<br>  --set tunnel=disabled</pre><p><em>Note</em>: tunnel parameter deprecated after 1.15, if your version greater thane 1.15 ignore this parameter.</p><p><strong>Parameter Explanations:</strong></p><ul><li><strong>ipam.mode:</strong> Sets the ENI mode for IP address management. Cilium will manage IP addresses using AWS’s ENI mechanism.</li><li><strong>eni.awsEnablePrefixDelegation:</strong> Enables the prefix delegation feature on AWS. This is useful for environments that require many pods.</li><li><strong>egressMasqueradeInterfaces:</strong> Sets the network interface (eth0) for egress traffic, performing IP masquerading for outgoing pod traffic.</li></ul><h4>Create Node Group</h4><p>If you want to use amazon-vpc-cni, the prefix delegation is ready to use. However, if you choose Cilium with prefix delegation, you need to create a new node group to activate this feature.</p><h4>Testing</h4><p>Once everything is set up, you can test the deployment by creating a simple pod. Here is an example using an nginx deployment:</p><ol><li>Create the deployment file nginx.yaml:</li></ol><pre>~via  v20.18.1 via  v3.11.9<br>●  cat nginx.yaml<br>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: nginx-test-deployment<br>spec:<br>  selector:<br>    matchLabels:<br>      app: nginx-test<br>  replicas: 1<br>  template:<br>    metadata:<br>      labels:<br>        app: nginx-test<br>    spec:<br>      containers:<br>      - name: nginx<br>        image: public.ecr.aws/nginx/nginx:1.21<br>        ports:<br>        - containerPort: 80</pre><p>2. Scale the deployment:</p><pre>kubectl scale deployment nginx-test-deployment --replicas=200 -n default</pre><p>3. Check the pod count on your nodes and run the CDC script again to confirm the setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkN6uaV_R68louGz7IniVw.png" /></figure><p>4. Now let’s run again CDCscript,</p><pre>AWS EKS Cilium Prefix Delegation Check<br>─────────────────────────────────────────────────────────────────────────<br>ℹ Starting checks...<br><br>                                                    Checking Requirements<br>─────────────────────────────────────────────────────────────────────────<br>✓ aws is installed<br>✓ kubectl is installed<br>✓ ipcalc is installed<br>✓ jq is installed<br><br>                                               Fetching Cluster Instances<br>─────────────────────────────────────────────────────────────────────────<br>ℹ Profile: example<br><br>                                                Verifying Cluster Details<br>─────────────────────────────────────────────────────────────────────────<br>☁ Fetching cluster details...<br>✓ Cluster Status: ACTIVE<br>ℹ Kubernetes Version: 1.30<br>ℹ Platform Version: eks.28<br>☁ Checking node groups...<br>✓ Found node groups: example-node-group<br>☁ Checking Kubernetes nodes...<br>✓ Found 3 Kubernetes nodes<br><br>ℹ Node Details:<br>✓ ip-xxx.eu-west-1.compute.internal: True<br>✓ ip-xxx.eu-west-1.compute.internal: True<br>✓ ip-xxx.eu-west-1.compute.internal: True<br>☁ Fetching EC2 instances...<br>ℹ Attempting to get instance ID from node name...<br>ℹ Found node private IP: 10.x.x.x<br>✓ Found instance by private IP: i-xxx<br><br>                                 Checking Cilium Prefix Delegation Status<br>─────────────────────────────────────────────────────────────────────────<br>ℹ Checking Cilium configuration...<br>✓ Cilium CNI is active<br>✓ Prefix delegation is enabled (Managed by Cilium)<br>ℹ Cilium Version: 1.14.5<br><br>🌐 Checking ENI configuration...<br>🌐 Checking ENIs for instance: i-xxx<br><br>┌────────────────────────────────────────────────────────────────────────────┐<br>│ ENI ID                │ IP Configuration            │ Delegation Status    │<br>├────────────────────────────────────────────────────────────────────────────┤<br>│ eni-xxx               │ Prefixes:        1          │ ACTIVE (Cilium)      │<br>└────────────────────────────────────────────────────────────────────────────┘<br><br>ℹ Summary:<br>ℹ CNI Type: Cilium<br>ℹ Prefix Delegation: ACTIVE<br>ℹ Total ENIs: 3<br>ℹ Total prefixes assigned: 1<br>ℹ Available IPs from prefixes: 110<br>ℹ Instance type: m5a.large<br><br>🔍 Capacity Analysis:<br>ℹ Using prefix delegation mode (Managed by Cilium)<br>ℹ Each prefix (/28) provides 16 pod IPs #need improvement<br>ℹ Total available pod IPs: 110</pre><p>This setup shows that prefix delegation is enabled and working with Cilium on your AWS EKS cluster. It increases the pod capacity per node and improves resource utilization.</p><h3>Conclusion</h3><p>Using ENI Prefix Delegation on AWS EKS increases pod capacity and improves cost efficiency. With proper configuration using AWS VPC CNI or Cilium, you can optimize resource use and make your infrastructure more scalable and flexible. The CDC script helps you check that prefix delegation is set up correctly, ensuring a more efficient and sustainable AWS EKS environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc3ae5b28e36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Switching Gears: Strategies for Seamless Task Transitions]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blakk.medium.com/switching-gears-strategies-for-seamless-task-transitions-1a08fcac0e30?source=rss-24f9d85e8135------2"><img src="https://cdn-images-1.medium.com/max/1920/1*UIhiXGUryWNyD0hjETl8fA.jpeg" width="1920"></a></p><p class="medium-feed-snippet">In the modern work environment, particularly in the fast-paced world of DevOps, the ability to quickly switch between tasks, teams, and&#x2026;</p><p class="medium-feed-link"><a href="https://blakk.medium.com/switching-gears-strategies-for-seamless-task-transitions-1a08fcac0e30?source=rss-24f9d85e8135------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://blakk.medium.com/switching-gears-strategies-for-seamless-task-transitions-1a08fcac0e30?source=rss-24f9d85e8135------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a08fcac0e30</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[multitasking]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Oguzhan Coskun]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 14:45:12 GMT</pubDate>
            <atom:updated>2024-12-11T14:45:12.565Z</atom:updated>
        </item>
    </channel>
</rss>