It simplifies the process of managing multiple AWS accounts by listing all AWS profiles managed by AWS Vault and switching between them. It helps maintain the working context and improves efficiency.

Installing

You can install aws-vault-switch by downloading the latest release;

• on macOS, download the package and move it to /usr/local/bin.

    $ wget https://github.com/kobeBigs/aws-vault-switch/releases/download/v0.1.0/aws-vault-switch-mac.tar.gz 
    $ tar -xzvf aws-vault-switch-mac.tar.gz 
    $ sudo mv aws-vault-switch-mac /usr/local/bin/aws-vault-switch
  

if you are on macOS arm64 architecture you can download the arm package and use the instructions above

• on linux, you can do same above using the linux package.

Also, you can clone and build from source.

$ git clone https://github.com/kobebigs/aws-vault-switch
$ cd aws-vault-switch
$ go build -o aws-vault-switch

How to use it

# run aws-vault-switch and navigate and select using the arrow keys and enter key respectively
$ aws-vault-switch
Use the arrow keys to navigate: ↓ ↑ → ←
? Select AWS Profile:
  ▸ default
    aws-account-dev
    aws-account-prod
    aws-account-marketing
↓   aws-account-sales

Note: make sure you have AWS Vault installed and setup before using aws-vault-switch.

Contributions: issues, forks, and pull requests are welcome!

Here are some of my learnings in keeping Redash alive and optimised on AWS EC2.

Configuration and Logs

To check running docker processes, ssh into the server and run docker ps. This lists all running Redash docker containers. docker logs -f also provides logs on the container you pass to it ie. docker logs -f <container id>.

Restart

Navigate to /opt/redash on the server and run docker-compose restart to restart all containers.

You can also restart single processes using the container id or name. For instance, docker restart redash_server_1 will restart the Redash server.

Restarting Celery Workers & the Queries Queue

In case you are handling a problem, and you need to stop the currently running queries and reset the queue, follow the steps below;

1. you can flush redis by running docker exec -it redash_redis_1 redis-cli flushall. Restart container with docker restart redash_redis_1.

2. check redis dump size: docker exec -it redash_redis_1 ls -la.

Changing the Number of Workers

By default, Celery will start a worker per CPU core. Because most of Redash’s tasks are IO bound, the real limit for the number of workers you can use depends on the amount of memory your machine has. It’s recommended to increase the number of workers, to support more concurrent queries.

You can change the number of workers by changing WORKERS_COUNT for the scheduler service in docker-compose.yml located at /opt/redash/. Restart the services after, using docker-compose restart or docker-compose up -d.

DB

Accessing Redash’s DB:

Access Redash DB (Postgres) in docker using: docker exec -it redash_postgres_1 psql -U postgres. You can then perform any activity via the Postgres prompt.

SSL Renewal (Certbot)

I use Let's Encrypt and I renew the certificate using the command below.

sudo docker run -t --rm -v /opt/redash/nginx/certs:/etc/letsencrypt -v /opt/redash/nginx/certs-data:/data/letsencrypt deliverous/certbot renew --webroot --webroot-path=/data/letsencrypt

list certificates to check the renewal has taken effect and see the new expiry date;

sudo docker run -t --rm -v /opt/redash/nginx/certs:/etc/letsencrypt -v /opt/redash/nginx/certs-data:/data/letsencrypt deliverous/certbot certificates

Restart nginx after; go to /opt/redash and sudo docker-compose kill -s HUP nginx.

Redash NGINX Error

ERROR: for nginx Cannot start service nginx: b'driver failed programming external connectivity on endpoint redash_nginx_1 (e8c2089c3a09d7728fc79fb8eb7dde390ee9687d11a51d924d7224a28824ed52): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use'

When you encounter the above error, try the below commands to resolve it.

docker stop $(docker ps -a -q); docker rm $(docker ps -a -q); docker volume rm $(docker volume ls -qf dangling=true)

docker network rm $(docker network ls -q)

sudo lsof -nP | grep LISTEN

sudo kill -9 <>

If the above doesn't work, check the nginx service(docker container), stop it and restart with docker-compose up to restart all services/containers.

sudo service nginx status
sudo service nginx stop
sudo docker-compose restart

To get started, provision an Ubuntu 20.04 EC2 instance and connect to it via SSH.

Step 1: Install Erlang

sudo apt update
sudo apt install erlang

Step 2: Add RabbitMQ to Ubuntu

Enable apt HTTPS transport

sudo apt install apt-transport-https

Get RabbitMQ keys

wget -O- https://dl.bintray.com/rabbitmq/Keys/rabbitmq-release-signing-key.asc | sudo apt-key add -
wget -O- https://www.rabbitmq.com/rabbitmq-release-signing-key.asc | sudo apt-key add -

Add RabbitMQ Repository (this assumes you’re on focal - Ubuntu 20.04)

echo "deb https://dl.bintray.com/rabbitmq-erlang/debian focal erlang-22.x" | sudo tee /etc/apt/sources.list.d/rabbitmq.list

Step 3: Install RabbitMQ

sudo apt update
sudo apt install rabbitmq-server

Check status. RabbitMQ service is started and enabled after installation.

sudo systemctl status  rabbitmq-server.service

Check if RabbitMQ service is configured to start on boot.

sudo service rabbitmq-server start

If disabled, enable it with

sudo systemctl enable rabbitmq-server

Enable RabbitMQ Management Web Dashboard

sudo rabbitmq-plugins enable rabbitmq_management

This web service listens on TCP Port 15672. Open http://server ip/hostname:15672 in your browser to access the dashboard.

By default, the service creates a user 'guest' account with password ‘guest’. This can only be used when accessing on a localhost.

To login on a network, create an admin user account. See below.

Creating Users

Create user or admin user using the command below

sudo rabbitmqctl add_user <username> <password>

example: sudo rabbitmqctl add_user admin adminpassword

Add tags: administrator, management, monitoring, policymaker

sudo rabbitmqctl set_user_tags <username> administrator

In the above command, the tag ‘administrator’ gives user full management UI and HTTP API access. Non administrator users should not be assigned a tag.

Now, set/grant permissions to the user. This grants the user access to all virtual hosts(vhosts).

sudo rabbitmqctl set_permissions <username> ".*" ".*" ".*"

Login to management dashboard http://server ip/hostname:15672 as admin.

Port Access

To connect to rabbitmq using AMQP 0-9-1 and 1.0 clients with and without TLS, use port 5672 or 5671.

amqp://username:password.<server ip/hostname>:5672//

For management UI, HTTP API access, use port 15672 in your browser http://server ip/hostname:15672.

References

• https://www.rabbitmq.com/ec2.html

• https://www.rabbitmq.com/install-debian.html

• https://computingforgeeks.com/how-to-install-latest-rabbitmq-server-on-ubuntu-linux/

This is a guide on installing and setting up pgweb on Amazon EC2 (Ubuntu 20.04.4 LTS machine).

Requirement:

1. An Amazon EC2 instance

Installation

SSH into your instance and update your system packages. sudo apt update && sudo apt upgrade -y

Download and install pgweb.

curl -s https://api.github.com/repos/sosedoff/pgweb/releases/latest \
  | grep linux_amd64.zip \
  | grep download \
  | cut -d '"' -f 4 \
  | wget -qi - \
  && unzip pgweb_linux_amd64.zip \
  && rm pgweb_linux_amd64.zip \
  && mv pgweb_linux_amd64 /usr/local/bin/pgweb

Check installation by running;

pgweb -v

  Output
  Pgweb v0.11.11 (git: db2a7a8aa5bc449e4efa78cada9c76c3fe33bc39) (go: go1.17.6) (build time: 2022-03-30T04:36:12Z)

Usage

Start server with pgweb.

By default pgweb runs on 127.0.0.1, localhost on port 8081. For Amazon EC2, bind pgweb to 0.0.0.0 to be able to access pgweb via the instance's public IP/DNS.

pgweb --bind 0.0.0.0

Open your-instance-public-ip:8081 in your browser to access pgweb.

To connect to a database at start of pgweb you can add the connection flags;

pgweb --bind 0.0.0.0 --host db-host-endpoint --user dbuser --db dbname

pgweb also supports url scheme connection;

pgweb --bind 0.0.0.0 --url postgres://dbuser:password@host:port/database

See more CLI options/flags.

Extend into a service(daemon)

This lets systemd manage pgweb and can be monitored via systemctl.

Create a file pgweb.service in /etc/systemd/system folder.

sudo vi /etc/systemd/system/pgweb.service

Copy and paste the code below;

[Unit]
Description=pgweb
Wants=
After=network.target

[Service]
User=ubuntu
Type=simple
ExecStart=/usr/local/bin/pgweb --bind 0.0.0.0 --sessions
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

Note the --sessions flag on ExecStart=/usr/local/bin/pgweb --bind 0.0.0.0 --sessions is to enable multiple database sessions.

You can also get/clone this repo and move pgweb.service file to /etc/systemd/system folder.

sudo mv pgweb.service /etc/systemd/system

Reload services to include the new service.

sudo systemctl daemon-reload

Start the service and check the status.

sudo systemctl start pgweb.service
sudo systemctl status pgweb.service

If all goes through, enable the service to start at boot;

sudo systemctl enable pgweb.service