This is a placeholder post for the Parsivex blog pipeline. Real launch articles will target specific AWS waste problems and link into the help centre for reference.
Why blog posts look like help articles
Blog MDX reuses the same component map as the help centre — no separate typography system. That means callouts, code blocks, and tables render with identical styling.
Posts inherit helpMdxComponents from the help centre. There is no @tailwindcss/typography plugin in this repo — all article styling lives in the MDX component map.
Example diagnostic steps
When you investigate NAT Gateway spend, a typical workflow looks like this:
Check data transfer
Open the VPC flow logs or Cost Explorer and confirm how much traffic routes through the NAT Gateway versus VPC endpoints.
Look for cross-AZ traffic
NAT Gateways charge per GB processed. Cross-AZ routing is a common driver of unexpected NAT bills.
Run a Parsivex scan
Parsivex flags NAT Gateway overuse when data transfer exceeds configured thresholds. Run a free scan to see your total estimated waste.
Quick reference
| Surface | Purpose |
|---|---|
| Blog post | Question / how-to — diagnose and fix a specific problem |
| Help article | Reference — what a finding type means in Parsivex |
| Free scan | Connect AWS read-only and see total estimated monthly waste |
Example CLI command
Use the AWS CLI to list NAT Gateways in a region:
aws ec2 describe-nat-gateways \
--region us-east-1 \
--query 'NatGateways[*].[NatGatewayId,State,VpcId]' \
--output table
Always review CLI commands in your own account context. Parsivex remediation scripts are separate from diagnostic commands like this one.
What comes next
Launch articles will map one-to-one to shipped waste detectors. Each post links down into the corresponding finding-type help article — never the other way around.