41,554 blogs · 5,316,985 posts Claim your blog

Record · corpus.blog/posts/01a08c55-a830-7150-b99c-5a8371684e13

What happens when you leak AWS credentials and how AWS minimizes the damage

tiborhercz.com · published 5 April 2023

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at tiborhercz.com Wayback capture

0blogs citing

First cited: —
Most recent: —
Rank this month: not ranked
External links: 5
Words captured: 2,284

Cited by

No blog we hold has cited this post yet.

Links from this post

Link

Host

https://github.com/tiborhercz/aws-leaked-credentials/commit/33b4d387e94e16b1c8b9277056299bdb02de3a4b

github.com

https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning

docs.github.com

https://docs.github.com/en/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories

docs.github.com

https://github.com/tiborhercz/aws-leaked-credentials/blob/33b4d387e94e16b1c8b9277056299bdb02de3a4b/credentials.txt

github.com

https://console.aws.amazon.com/iam/home

console.aws.amazon.com

Elsewhere on tiborhercz.com (1)

Steps to take after leaking AWS credentials Read at the source ↗