aboutsummaryrefslogtreecommitdiff
path: root/aws-ipblocks-csv
diff options
context:
space:
mode:
authorDavid Timber <dxdt@dev.snart.me>2024-03-20 06:27:01 +0900
committerDavid Timber <dxdt@dev.snart.me>2024-03-20 06:27:01 +0900
commit3b370208fc349d937cf036d6398b30399b6cb510 (patch)
tree4cba3fb6becfba3df3dbe8cb8bbba528557b15a6 /aws-ipblocks-csv
parent1c0cd118eb48ba9f62a4d39530678b2e20d0533a (diff)
Fix static urls
Diffstat (limited to 'aws-ipblocks-csv')
-rw-r--r--aws-ipblocks-csv/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/aws-ipblocks-csv/README.md b/aws-ipblocks-csv/README.md
index 6b8cf8d..f415bb4 100644
--- a/aws-ipblocks-csv/README.md
+++ b/aws-ipblocks-csv/README.md
@@ -9,13 +9,13 @@ The JSON data is probably for anyone who is affected by the Amazon's IP address
changes, namely network admins who have to configure their firewalls for AWS
traffic. Technically speaking, the data is not meant to be consumed by humans,
but I personally had to consume it for [my hobby self-hosting
-project](https://gist.github.com/ashegoulding/72a8732d4a1679c343f84fc985ca8de8).
+project](https://gist.github.com/dxdxdt/72a8732d4a1679c343f84fc985ca8de8).
I was particularly interested in EIP address blocks. I figured they're something
AWS cannot easily mess with because that involves "evicting" all the EIP holders
before releasing or repurposing the block.
This tool is hosted on [my github.io
-site](https://ashegoulding.github.io/aws-ipblocks-csv). Bon appetit!
+site](https://dxdxdt.github.io/aws-ipblocks-csv). Bon appetit!
## Links
https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html