Considerations for using a cloud relational store
System storage is a foundational requirement of ArcGIS Enterprise to support administrative and other workflows in the organization. Included in this storage requirement is a relational store.
Administrators deploying ArcGIS Enterprise in the Amazon Web Services (AWS) or Microsoft Azure cloud can optionally configure a supported cloud database service to use as the relational store database. ArcGIS Data Store must still be installed and configured as a relational store. With a cloud relational store, however, data is stored in the cloud database service rather than locally on the ArcGIS Data Store machine. This configuration can provide scalability, reliability, and performance advantages, but it is recommended only for organizations with the expertise to administer PostgreSQL databases and effectively manage cloud services and related resources.
As with all service offerings, cloud database service providers can change settings and functionality in their offerings, even in minor releases. It is possible that changes made by the provider could adversely affect access from ArcGIS to the database. To mitigate these adverse effects, it is recommended that you work with your cloud provider to understand any changes in their service and to keep your ArcGIS software updated in order to have access to the latest updates that address changes in cloud services. Take regular backups of your ArcGIS Enterprise organization and test your backup restoration process.
The following sections describe considerations for using a cloud relational store with ArcGIS Enterprise, including software usage, supported types, requirements, and ongoing maintenance needs.
Supported cloud database services
The following cloud database service types are supported for use with ArcGIS Enterprise:
Amazon Relational Database Service (RDS) for PostgreSQL
Amazon Aurora PostgreSQL
Azure Database for PostgreSQL - Flexible Server
Note:
To minimize latency and connectivity issues, it is recommended that any cloud database services use the same cloud provider and region as ArcGIS Enterprise.
Database requirements
A cloud relational store configured with ArcGIS Enterprise must meet the following requirements:
The PostgreSQL instance version and PostGIS version must be supported for that version of ArcGIS Enterprise. See Supported cloud-based database services for supported PostgreSQL and PostGIS versions for each cloud service.
The database must be network accessible from ArcGIS Enterprise. Some security groups and firewalls may block direct access to the database by default.
Database username and password authentication must be used for the administrator account.
Connections and instance sizing
It is important to consider and allocate for sufficient sizing of your database instance, as many services do not allow instance resizing. Additionally, resizing an instance after it's been in use may be disruptive or lead to unforeseen issues.
Each database connection consumes memory and CPU on the database servers and impacts hardware needs.
For example, hosted feature services may use up to 100 database connections when there are 100 simultaneous requests on those services. To account for other service requests, an additional 100 are recommended, for a total of 200. Because this may be lower than the default for the cloud database service, it is recommended that you increase the connection limit to 200 or more.
Note:
It is not supported to use pgBouncer as a proxy to pool database connections to the cloud relational store.
Databases use RAM to improve performance on frequently accessed data. Hosted feature services typically contribute the largest amount of data. Usage can vary considerably since many services may be used infrequently, while others may be accessed constantly. If you know that some hosted feature services will be accessed consistently and you can estimate their size, it may be worthwhile to plan for additional RAM.
Hardware recommendations
For solid performance with a median load, it is recommended that you use database instances with the following:
4 virtual CPUs
16 GB RAM
For larger data volumes that are frequently accessed, it is recommended that you add more RAM.
Storage
Your organization's storage needs will vary depending on the data you're using. A baseline recommendation is 100 GB of storage, which may be suitable for a few hundred hosted feature services with minimal attachments. Feature attachments, especially high-resolution imagery, can consume large amounts of space. If you anticipate having large attachments, it's essential that you work with your GIS department to estimate the storage space, as some organizations exceed 1 TB of storage to support their data needs.
Software usage
When configuring a cloud relational store, consider that its resulting instance is to be used exclusively for ArcGIS Enterprise. Do not put other databases or data in that instance. Additionally, the software creates databases, schemas, and users in the instance.
The administrative database user that you provide to ArcGIS Enterprise is used during initial configuration and the backup and restore processes. ArcGIS Enterprise creates specific least-privilege users for operational use, ensuring greater security.
Ongoing maintenance
When using a cloud relational store, your IT administrator or database administrator must continue the ongoing maintenance and management of the system. The following are examples:
Manage the database system by applying patches and monitoring hardware use, particularly storage.
Manage system-wide settings such as the number of connections.
Upgrade the database version after verifying the new database version is supported for your version of ArcGIS Enterprise.
ArcGIS Enterprise software, on the other hand, continues ongoing software maintenance. The following are examples:
Manage columns, tables, indices, and users.
Back up and restore the database during routine organization backup and restore processes.
Administrators can also use their cloud service provider's tools to create their own database backups and restore data from those backups. If the database is restored using the cloud provider's tools, administrators must also run the ArcGIS Data Store
restoredatastoreutility as a secondary step, using the--cloudconfigFileparameter to specify a file with the newdbURIvalue of the restored database.
Migrating an existing relational store to the cloud
For ArcGIS Enterprise deployments in the AWS or Azure cloud, it is possible to migrate the relational store to the cloud using a supported cloud database service from the same provider. At this release, migrating in the opposite direction is not supported.