Not Maintained

Feel free to submit feature requests for the new version.

On the roadmap:

• Support for more resource types
• Support for more cloud providers

CloudTables

Cloud Resource Manager

Provides an easily searchable database of AWS resources across multiple accounts.

Installation

---

NOTE

If you skip any of these steps, your install will explode like a hot pocket in the microwave.

---

Prerequisites

The docker compose config needs the nc utility, as this is the method used to determine when the database is ready to proceed.

Set up AWS Credentials

Start by setting up your AWS credentials file.

mkdir $HOME/.aws
cat <<EOF > $HOME/.aws/credentials
[aws_acct_1]
aws_access_key_id=50M353C237!D
aws_secret_access_key=50M353C237P@55W02D

[aws_acct_2]
aws_access_key_id=50M353C237!D
aws_secret_access_key=50M353C237P@55W02D
EOF

You can add as many accounts as you want. I've tested it with like 12(?). If you manage more than 12 AWS accounts, I'm impressed and horrified all at the same time.

In the square brackets of the credentials file is the name of the AWS account. And by "name" I mean whatever name you want to call it. You can call it "prod" or "banana_phone"... it doesn't matter, and it doesn't correspond to anything in your AWS account. It's completely arbitrary. But it will show up in the "Account" column in CloudTables for every resource in that account, so try to pick a good identifier.

You can also change it later and re-sync to update the account name on those objects.

Docker Compose

Provided is a simple docker compse file that will install the front end, back end, and DB containers on a standalone docker host.

I have scripts to install docker and docker-compose here:

• CentOS 7
• Ubuntu 16.04

First, clone the repository

git clone https://github.com/corysm1th/cloudtables-python.git
cd cloudtables-python

If you're just doing a PoC, you can make self_signed to generate the certs. Otherwise, place your certificate and key somewhere on the server, and create symlinks for cloudtables/ssl/nginx.crt and cloudtables/ssl/nginx.key inside the repo.

cd cloudtables-python/ssl
ln -s /path/to/yourcert.crt nginx.crt
ln -s /path/to/yourcert.key nginx.key

Finally, cd back to the parent cloudtables-python repo folder and install the software:

make install

The front end will be exposed on port 443 of the host, and the inital sync should kick off automatically.

Configuration Changes

By default CloudTables will iterate over all AWS regions. If you want to reduce sync time, you can prune the list in .env.

To put your changes into effect, just have docker compse rebuild the stack:

make update

Troubleshooting

If you run into issues, and have double checked the installation instructions, you can use these additional tools to resolve issues.

The Makefile has some helpful scripts:

• make clean: deletes all containers, deletes all data and static files from the host
• make reset_secrets: resets the Django secret key and Postgres password, so that make install can generate new ones.
• make clean_certs: Deletes self signed certs and all symlinks from the ./ssl folder.

Sometimes it may be required to clean some stale container resources from docker.

• make clean followed by docker system prune does a good job of fixing most issues.
• make clean followed by ddocker system prune -a should wipe out pretty much everything.

You can also enable debuging in ./cloudtables/cloudtables/setting.py. At line 28, set DEBUG = True and run make update. Afterward, you can navigate to cloudtables in your web browser, and it will output any python stack traces, and dump the contents of all variables. Useful for troubleshooting issues with both the UI and the sync function (located at https://hostname/sync).