<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Emulator on SoloSoft</title><link>https://www.solosoft.dev/tags/aws-emulator/</link><description>Recent content in Aws-Emulator on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/aws-emulator/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Emulator Measured: 56.46% of Its Own Fidelity Tests Pass, 8,261 of 40,130 Operations Answer 501, and 306 Return Success Where AWS Returns an Error</title><link>https://www.solosoft.dev/post/aws-emulator-fidelity-ledger-measured/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/aws-emulator-fidelity-ledger-measured/</guid><description>&lt;p&gt;AWS shipped a local AWS emulator in September 2026. It is a Rust binary you install from a Debian or RPM package, point &lt;code&gt;AWS_ENDPOINT_URL&lt;/code&gt; at, and run your integration tests against without an AWS account. Anyone who has run that category of tool before knows the failure mode: the tests go green locally and the stack falls over on real AWS.&lt;/p&gt;
&lt;p&gt;What makes this one unusual is that AWS publishes the evidence. Every release is supposed to carry a &lt;code&gt;scores.json.gz&lt;/code&gt; — the raw pass/fail ledger of a public conformance suite — and the repository tracks individual gaps as markdown files in two directories, &lt;code&gt;issues/things-that-do-not-work/&lt;/code&gt; and &lt;code&gt;issues/things-that-now-work/&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>