<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Infrastructure on The Coders Blog</title><link>https://thecodersblog.com/tag/cloud-infrastructure/</link><description>Recent content in Cloud Infrastructure on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 17:06:06 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/cloud-infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS MCP Server is Now Generally Available: What You Need to Know</title><link>https://thecodersblog.com/aws-mcp-server-general-availability-2026/</link><pubDate>Wed, 06 May 2026 17:06:06 +0000</pubDate><guid>https://thecodersblog.com/aws-mcp-server-general-availability-2026/</guid><description>&lt;p&gt;Imagine your AI agent, trained on vast datasets, suddenly needing to provision a new S3 bucket or troubleshoot a flaky EC2 instance. How does it securely, and reliably, interact with your cloud infrastructure? This is the gap the AWS MCP Server, now generally available, aims to bridge. It promises to unlock powerful AI-driven automation, but demands a critical eye on its implementation.&lt;/p&gt;
&lt;h2 id="the-core-problem-ai-agents-without-cloud-access-are-limited"&gt;The Core Problem: AI Agents Without Cloud Access Are Limited&lt;/h2&gt;
&lt;p&gt;AI agents are increasingly sophisticated, capable of understanding complex requests and generating code. However, without a secure and authenticated channel to interact with real-world systems, their utility remains largely theoretical. Asking an AI to &amp;ldquo;create a VPC with public and private subnets&amp;rdquo; is one thing; enabling it to &lt;em&gt;actually&lt;/em&gt; execute the necessary AWS API calls is another. This is where the Model Context Protocol (MCP) server, and specifically the AWS MCP Server, enters the picture, offering AI agents authenticated access to over 15,000 AWS API operations.&lt;/p&gt;</description></item><item><title>AI's Thirsty Truth: Why Its Water Footprint Isn't What You Think [2026]</title><link>https://thecodersblog.com/ai-s-environmental-footprint-debunking-water-use-myths-2026/</link><pubDate>Fri, 01 May 2026 21:27:09 +0000</pubDate><guid>https://thecodersblog.com/ai-s-environmental-footprint-debunking-water-use-myths-2026/</guid><description>&lt;p&gt;Forget the &amp;lsquo;gallons per ChatGPT query&amp;rsquo; headlines; that&amp;rsquo;s not where AI&amp;rsquo;s real water challenge lies. As senior engineers, we need to talk about the system, the infrastructure, and the optimizations that truly define AI&amp;rsquo;s water footprint by &lt;strong&gt;2026&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="the-core-misconception-why-gallons-per-query-is-a-distraction"&gt;The Core Misconception: Why &amp;lsquo;Gallons Per Query&amp;rsquo; is a Distraction&lt;/h2&gt;
&lt;p&gt;The media loves a catchy, easily digestible metric. &amp;ldquo;X gallons per ChatGPT query&amp;rdquo; is precisely that – and it&amp;rsquo;s fundamentally misleading. This pervasive, oversimplified narrative fails to capture the true water demands of modern AI. It’s akin to measuring the fuel efficiency of a car by the amount of gasoline used for a single brake press.&lt;/p&gt;</description></item></channel></rss>