How to fix: X-Amz-Request-Id reveals AWS infrastructure
The X-Amz-Request-Id header is present, revealing that the response is served from AWS infrastructure.
Why it matters
While low severity on its own, revealing AWS infrastructure enables attackers to tailor attacks to AWS-specific vulnerabilities, targeting S3 public bucket access, EC2 metadata endpoints, or IAM misconfigurations.
Strip AWS-specific headers at your edge proxy before they reach clients.
How to fix it
- 1Configure your CDN or reverse proxy to strip X-Amz-* headers
- 2Ensure S3 bucket responses are proxied and not directly accessed
Code examples
Nginx: strip AWS headers
proxy_hide_header X-Amz-Request-Id;
proxy_hide_header X-Amz-Id-2;
proxy_hide_header X-Amz-Version-Id;References
Detected automatically by VulnRadar. The check id is x-amz-request-id, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-Amz-Request-Id reveals AWS infrastructure?
- VulnRadar rates this info severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id x-amz-request-id, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.