When deploying ArcGIS Enterprise on Kubernetes on Microsoft Azure, you can configure a cloud relational store to support hosted feature data and administrative aspects, such as customization and configuration settings. See Considerations for using a cloud relational store to learn more.
Considerations for selecting and administering a relational store in Azure are provided below.
Compatible options
ArcGIS Enterprise on Kubernetes is compatible with one relational store option available on Azure:
This option provides high availability, reliability, and the ability to scale read-only replicas to achieve high throughput.
Cluster options
When creating an Azure Database for PostgreSQL flexible server instance, choose the Server option. This option provides node-based clustering with support for read-only replica scale-out. The elastic cluster option is not supported for ArcGIS Enterprise.
Compute options
When creating an Azure Database for PostgreSQL flexible server instance, consider which compute and pricing option suits your organization's needs:
- Burstable—Not recommended for production use because it does not support high availability.
- General purpose—Balances compute and memory resources.
- Memory optimized—Increased memory to CPU ratio.
Storage options
For instance storage, the minimum disk size is 32GiB. When choosing an initial size, consider the space required for your hosted feature layers and other managed relational data.
Various classes of performance tiers can be selected based on instance type, and the tier can be temporarily increased to accommodate unanticipated demand on the database instance. For more information refer to Performance tiers for managed disks .
To avoid running low or out of disk space, it is recommended that you enable storage autogrow.
High availability
Azure Database for PostgreSQL flexible server can support the following highly available configurations:
- Disabled—No standby server is provisioned for the instance. This option is not recommended for production systems.
- Same zone—For organizations that are not making use of multiple availability zones, this option provisions a standby server within the same availability zone.
- Zone redundant—For organizations requiring the highest availability and deployed to a cluster spanning multiple availability zones, this option provisions a standby server within a separate availability zone in the same region. This option is recommended for production systems.
Authentication
ArcGIS Enterprise requires database administrator credentials to manage the users, schemas, and databases created for an organization. This requires one of the following authentication methods for compatibility:
- PostgreSQL authentication only
- PostgreSQL and Microsoft Entra authentication
The Microsoft Entra only option is not supported at this release.
Database connectivity
ArcGIS Enterprise does not require public access to the database instance. It is recommended that you disallow public access. To enable ArcGIS Enterprise to connect to your Azure database without the need to traverse the public internet, chose one of the following options:
- Place the database in the same virtual network as your Microsoft Azure Kubernetes Service (AKS) cluster.
- Place the database in a virtual network that is peered to the virtual network used by your AKS cluster.
If you are unable to provision the database instance in the same or peered virtual network, it is recommended that you implement firewall rules limiting database access to only the public IP addresses of ArcGIS Enterprise and other allowed clients. Administrators should consult with their cloud security experts to define their network architecture and controls according to best practices.
Post-provisioning considerations
After you have provisioned an Azure Database for PostgreSQL flexible server instance, there are additional steps to achieve compatibility with ArcGIS Enterprise.
Allowed extensions
ArcGIS Enterprise requires that you allow the POSTGIS extension. For instructions on allowing extensions, see Allowed extensions.
Backups
ArcGIS Enterprise has an integrated backup and restore implementation that maintains consistency with the other system managed data stores within the organization. For this reason, Azure backups can be disabled to save on storage costs. Administrators can opt to leave these backups enabled, but restoring the database instance outside of ArcGIS Enterprise can lead to data loss and item corruption.