Password manager using Passbolt through AWS
-
Leveraging AWS and Passbolt to successfully create a self-hosted password manager to store sensitive information (passwords) and manage them enforcing data protection.
-
Implementing HTTPS encryption to safeguard sensitive data trasnsmitted to and from the password manager
-
Configure and maintain the domain hosting for the password manager, ensuring accessibility and security.
- AWS
- VirtualBox (Ubuntu)
- PassBolt
- Namecheap -(Domain)
- Get started with the Community version of Passbolt Pro.
- Select AWS and then press Deploy to AWS
- After subscribing, I proceeded with the default setup.
- Setup a new security group to allow traffic for Passbolt
- Created a new key pair and dragged file into my Ubuntu under PASSBOLT.pem on virtual machine desktop.
- Successful launch of EC2 instance from Passbolt and in AWS. (Instance has to initialize and be checked)

- After EC2 has been initialized, I copied the public IPv4 address and opened in new tab of web browser. Caveat: entered http:// in front of the IPv4 address. Https is not configured yet.
In the terminal of the Ubuntu machine, ensure to change the permissions so the key isn't publically viewable and then ssh into the ec2 isntance.
cd Desktop
chmod 400 "PASSBOLT.pem"
ssh -i PASSBOLT.pem admin@[ec2ipv4 address] sudo nano /etc/nginx/sites-enabled/nginx-passbolt.confUpdated server name to my domain I purchased from namecheap.

sudo dpkg-reconfigure passbolt-ce-server- The next steps I entered in my domain site and admin for the domain site.
- When successful should display similar to below. If failed, ensure the correct domain site is entered in the nginx config.
After all the configuration has been completed in Passbolt, I downloaded the extensions and downloaded the passkit provided. It also presented me with a security token.
Password manager has been successfully setup
Credits to Pavel Hrabec














