Geodatabases store spatial and nonspatial data. Geodatabases on Amazon Elastic Compute Cloud (EC2) instances are intended to store data you are serving from your ArcGIS Server sites on Amazon Web Services (AWS). You can use file, workgroup, or enterprise geodatabases.
Geodatabases in AWS instances are not intended to be accessed directly from on-premises ArcGIS clients as performance will be far slower than when the geodatabases are accessed from ArcGIS clients on AWS.
ArcGIS Enterprise on AWS deployment tools provide options to include an enterprise geodatabase in an Amazon database service with your stand-alone ArcGIS GIS Server site. The enterprise geodatabase created with these tools is registered with the GIS Server site as a managed database. If you create your site through the AWS Management Console using the Esri Amazon Machine Images (AMI), you can create your own file, workgroup, or enterprise geodatabases and register them with the ArcGIS Server site.
See the ArcGIS Server topic Data sources for ArcGIS Server for more information on registering geodatabases with your site.
When you launch a stand-alone GIS Server site using ArcGIS Enterprise on AWS deployment tools and provide an ArcGIS GIS Server enterprise edition license, an enterprise geodatabase is created in an AWS instance.
The enterprise geodatabase is named egdb, and it is added as a managed database to the GIS Server site.
You can publish data from your on-premises data sources and desktop applications to your GIS Server site on AWS, and ArcGIS will copy the data to the managed database.
Amazon performs some database maintenance tasks so you don't have to. For example, RDS instances automatically apply database patches and create backups of your database. They are also designed to be highly available, as they can be run in multiple availability zones (referred to as multi-AZ deployments).
Multi-AZ deployments are the default deployment type for Amazon database service instances; therefore, Amazon database service instances you launch using ArcGIS Enterprise on AWS deployment tools use this deployment type.
Because they provide enhanced availability, Amazon recommends you use multi-AZ deployments for production systems. Be aware, though, that these deployments cost more to use per hour and for storage than other deployments. Consult the Amazon RDS pricing guide for more information.
The following diagram shows a GIS Server site on AWS with ArcGIS Server and an Amazon RDS instance, with two additional GIS Server installations on AWS instances available when CPU usage exceeds a specified threshold.
See Geodatabases in PostgreSQL used with ArcGIS on AWS and Enterprise geodatabases in SQL Server used with ArcGIS on AWS for more information.
If you use the Esri AMIs and AWS Management Console to create your stand-alone GIS Server site, you can create your own enterprise geodatabases in one of the supported AWS databases.
Supported AWS database offerings
ArcGIS Enterprise on AWS deployment tools can create enterprise geodatabases in the following AWS databases:
- Amazon Aurora PostgreSQL
- Amazon Relational Database Service (RDS) for PostgreSQL
- Amazon Relational Database Service (RDS) for SQL Server
Deployment tools provided by Esri do not create geodatabases in Microsoft SQL Server or PostgreSQL, but you can create your own instance with SQL Server on it and run the Enable Enterprise Geodatabase tool to create the geodatabase.
At this time, ArcGIS supports only database-authenticated connections to these database services.
If you have an ArcGIS Enterprise workgroup edition license, you can use the Esri Windows AMI and AWS Management Console to create a stand-alone GIS Server site on an EC2 instance. Once the ArcGIS Server workgroup edition instance exists, you can install an ArcGIS database server (workgroup) on it.
See Workgroup geodatabases used with ArcGIS on AWS for more information on creating and using these geodatabases on AWS.