Deploying Paybill on Amazon AMI
You should setup a PostgreSQL database manually to be used by the Paybill server.
You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a CloudFormation template. This template will deploy all the services required to run Paybill on AWS AMI instances.
To deploy all the services at once, simply employ the following template:
curl -LO https://raw.githubusercontent.com/paybilldev/paybill/refs/heads/master/deploy/cloudformation/EC2-cloudfomration.yml
Follow the steps below to deploy Paybill on AWS AMI instances.
-
Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
-
Login to your AWS management console and go to the EC2 management page.
✅ EC2 Dashboard (default region)
🌍 EC2 Dashboard by Region:
You can manually change the region in the URL (replace
us-east-1
with your region):-
US East (N. Virginia): https://console.aws.amazon.com/ec2/v2/home?region=us-east-1
-
US West (Oregon): https://console.aws.amazon.com/ec2/v2/home?region=us-west-2
-
Europe (Ireland): https://console.aws.amazon.com/ec2/v2/home?region=eu-west-1
-
Africa (Cape Town): https://console.aws.amazon.com/ec2/v2/home?region=af-south-1
-
-
Under the Images section, click on the AMIs button.
-
Find the Paybill version you want to deploy. Now, from the AMI search page, select the search type as "Public Images" and input the version you'd want
AMI Name : paybill_vX.X.X.ubuntu_bionic
in the search bar.

-
Select Paybill's AMI and bootup an EC2 instance.
Creating a new security group is recommended. For example, if the installation should receive traffic from the internet, the inbound rules of the security group should look like this:protocol port allowed_cidr tcp 22 your IP tcp 80 0.0.0.0/0 tcp 443 0.0.0.0/0 -
Once the instance boots up, SSH into the instance by running
ssh -i <path_to_pem_file> ubuntu@<public_ip_of_the_instance>
. -
Switch to the app directory by running
cd ~/app
.
Modify the contents of the.env
file. ( Eg:vim .env
)The default
.env
file looks like this:APP_KEY=
PG_DB=
PG_USER=
PG_HOST=
PG_PASS=
PB_DB=
PB_DB_HOST=
PB_DB_USER=
PB_DB_PASS=Read environment variables reference
infoIf there are self signed HTTPS endpoints that Paybill needs to connect to, please make sure that
NODE_EXTRA_CA_CERTS
environment variable is set to the absolute path containing the certificates. -
PB_DB_HOST
environment variable determines where you can access the Paybill client. It can either be the public ipv4 address of your instance or a custom domain that you want to use.Examples:
PB_DB_HOST=http://12.34.56.78
orPB_DB_HOST=https://yourdomain.com
orPB_DB_HOST=https://paybill.yourdomain.com
infoWe use a lets encrypt plugin on top of nginx to create TLS certificates on the fly.
infoPlease make sure that
PB_DB_HOST
starts with eitherhttp://
orhttps://
-
Once you've configured the
.env
file, run./setup_app
. This script will install all the dependencies of Paybill and then will start the required services. -
If you've set a custom domain for
PB_HOST
, add aA record
entry in your DNS settings to point to the IP address of the EC2 instance. -
You're all done, Paybill client would now be served at the value you've set in
PB_HOST
.
Deploying Paybill Database
Paybill AMI comes inbuilt with Postgres. If you intend to use this feature, you'd only have to setup the environment variables in ~/app/.env
file and run ./setup_app
script.
You can learn more about this feature here.
Upgrading to the Latest LTS Version
New LTS versions are released every 3-5 months with an end-of-life of atleast 18 months. To check the latest LTS version, visit the Paybill Docker Hub page. The LTS tags follow a naming convention with the prefix LTS-
followed by the version number, for example paybilldev/paybill:ee-lts-latest
.
Note: If this is a new installation of the application, you may start directly with the latest version. This guide is not required for new installations.
Prerequisites for Upgrading to the Latest LTS Version:
- It is crucial to perform a comprehensive backup of your database before starting the upgrade process to prevent data loss.
If you have any questions feel free to join our Discord Community or send us an email at info@paybill.dev.