Skip to main content

​
Overview

G360 requires a PostgreSQL database to store and manage application data. Your organization can use one of the supported database deployment options:
  1. A managed PostgreSQL database
  2. A PostgreSQL container deployed with G360

​
Option 1: Managed PostgreSQL Database

A managed PostgreSQL service is the recommended option for production environments. For example, organizations using AWS can use Amazon RDS. The database must use:
  • PostgreSQL 16 or later
  • The pg_trgm extension
A managed database service can simplify:
  • Backups
  • Database recovery
  • Storage management
  • Database maintenance
For an initial production deployment, the recommended configuration includes:
  • At least a db.t4g.large instance
  • 100 GB of gp3 storage
  • Storage autoscaling
  • At least 7 days of backups
  • Point-in-Time Recovery (PITR)
The database should only be accessible from authorized infrastructure, including the G360 environment.

​
Option 2: PostgreSQL Container

PostgreSQL can also run as a Docker container on the same server as G360. This option may be suitable for:
  • Pilot environments
  • Smaller deployments
  • Organizations that do not use a managed database service
However, your organization is responsible for managing:
  • Database backups
  • Restore testing
  • Database upgrades
  • Disk capacity
Do not remove Docker volumes used by the G360 PostgreSQL database. Removing these volumes can permanently delete database data.

​
Database Access

Before G360 is installed, the required database information must be available to the installation team. Depending on your database configuration, this may include:
  • Database hostname
  • Port
  • Database name
  • Database username
  • Database password
A dedicated database and database user should be used for G360.

​
Choosing a Database Option

​
Next Steps

After the database has been prepared, configure the required network and firewall access. Continue to Network Requirements.