<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Affinity on Wirez</title><link>https://wirez.top/tags/affinity/</link><description>Recent content in Affinity on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/affinity/index.xml" rel="self" type="application/rss+xml"/><item><title>Data transfer costs: Stop AWS NLB zone fees now</title><link>https://wirez.top/posts/data-transfer-costs-stop-aws-nlb-zone-fees-now/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/data-transfer-costs-stop-aws-nlb-zone-fees-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Crossing Availability Zone boundaries with an AWS Network Load Balancer instantly incurs a &lt;strong>$0.02 per GB&lt;/strong> surcharge that most architects ignore until billing arrives. Amazon Web Services explicitly details how bidirectional data flows between distinct zones trigger charges at both the sender and receiver endpoints, effectively doubling the cost of every gigabyte transferred.&lt;/p></description></item></channel></rss>