|Daniel 7f22d4c6cc Merge pull request #1 from SDFE/master||4 years ago|
|images||4 years ago|
|.env||5 years ago|
|.gitignore||5 years ago|
|LICENSE||5 years ago|
|README.md||5 years ago|
|explorer.py||5 years ago|
|mapall.py||4 years ago|
|requirements.txt||4 years ago|
Generate basic graphviz/dot maps of your AWS deployments.
$ pip install -r requirements.txt $ sudo apt-get install graphviz
$ ./mapall.py | dot -Tpng > aws-map.png $ eog aws-map.png
Options include specifying just one VPC to draw with: ./mapall.py --vpc vpc_123456
Or specifying a subnet to draw with: ./mapall.py --subnet subnet_123456
You can generate a map of each vpc or subnet individually. This is very useful if you have a large and complex setup where putting it all on a single page becomes spaghetti.
$ ./mapall.py --iterate vpc $ ./mapall.py --iterave subnet
Normally security groups get in the way and obscure what you want to see so they aren't included. You can add them back with --security. Note that if you only want to map a single subnet you shouldn't turn security groups on as there is no easy way to determine which subnet a security group operates on - so it draws them all - leading to potentially huge, unusable maps.
The program will write the results of the aws query to a .cache directory and use that unless you specify --nocache. Cacheing is much faster than querying AWS everytime but obviously won't react to changes that are made.