<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Wirez</title><link>https://wirez.top/tags/architecture/</link><description>Recent content in Architecture 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/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Airgapped VPC for SageMaker: Zero Public Internet</title><link>https://wirez.top/posts/airgapped-vpc-for-sagemaker-zero-public-internet/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/airgapped-vpc-for-sagemaker-zero-public-internet/</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">Three Availability Zones form the mandatory minimum foundation for deploying a network-isolated &lt;strong>Amazon SageMaker Unified Studio&lt;/strong> domain.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">This architecture proves that strict regulatory adherence to &lt;strong>HIPAA&lt;/strong> or &lt;strong>FedRAMP&lt;/strong> standards demands eliminating public internet exposure entirely. You will learn how &lt;strong>AWS PrivateLink&lt;/strong>, now available for this service as of January 2026, secures communication channels exclusively over private networks. The guide details constructing a custom VPC named &lt;strong>airgapped&lt;/strong> with specific interface and gateway endpoints to ensure sensitive data never leaves controlled pathways. Finally, we examine the step-by-step configuration required to maintain full functionality for data cataloging and query execution within these hardened boundaries.&lt;/p></description></item><item><title>RPKI validation gaps: Why 84% skip enforcement</title><link>https://wirez.top/posts/rpki-validation-gaps-why-84-skip-enforcement/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-validation-gaps-why-84-skip-enforcement/</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">With only 12.3% of analyzed ASes actively enforcing Route Origin Validation, global routing security remains critically fragile despite rising signature rates. The stark reality is that signing routes via &lt;strong>Resource Public Key Infrastructure&lt;/strong> means nothing without the mandatory filtering of invalid announcements at the network edge. Readers will examine the core mechanics of &lt;strong>Route Origin Validation&lt;/strong> and why current adoption metrics from APNIC data reveal a dangerous disconnect between signed prefixes and protected traffic. &lt;a href="https://blog.apnic.net/2025/07/22/how-can-rpki-can-be-made-quantum-safe/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s how can rpki can be made quantum safe&lt;/a> We dissect the specific failure modes of legacy BGP verification and how &lt;strong>Autonomous System Provider Authorization&lt;/strong> closes the loop on path hijacking by cryptographically validating upstream relationships. The analysis moves beyond theory to present a concrete operational playbook for deploying these controls, drawing direct lessons from IDNIC&amp;#039;s successful mandate in Indonesia.&lt;/p></description></item></channel></rss>