Which AWS limit is actually current? An agent that proves it, 32 vs 5 vs 16
This is a submission for the Sanity Challenge, Path One: Ship an Agent That Queries Real Content What I Built Which AWS quota is actually current? You copied a default vCPU limit off the AWS docs, shipped it, and it broke in production. I have done this. The number was stale, and nothing warned me. Here is what makes it nasty. For one AWS fact, three official pages can each give you a different…
This submission for the Sanity Challenge demonstrates an agent that queries real AWS content, specifically focusing on the current AWS quota values. The agent reveals that for AWS quotas, there can be three different numbers, each coming from a different source: the official AWS documentation, the Service Quotas console, and a pricing page. These sources can give conflicting information, making it difficult to determine which number is the most up-to-date.
To tackle this problem, the agent was built to read typed facts from a Sanity Context Knowledge Base, and it then selects the correct value using a deterministic rule that the model is not allowed to override. The agent also shows both the current value and the one that replaced it, along with their respective sources. To ensure accuracy, the agent performs a live AWS API check (read-only) to verify whether the reconciled record is still true.
The agent's Stack includes Amazon Nova Pro on Bedrock, Strands Agents (Python), a Sanity Context Knowledge Base, and a read-only live AWS cross-check. The keyword search, which is often used for finding AWS values, was tested and found to be unreliable, as it appears to provide the wrong answer based on an outdated record. In contrast, the agent successfully demonstrated that the current maximum IOPS per volume for an EC2 gp3 EBS volume is 80,000, while the outdated value from the user guide is 16,000.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
