Skip To Content

Strategies for loading data into a geodatabase on Amazon Web Services

You can publish services from data stored on-premises and have the data copied to the cloud. You can also copy data into a geodatabase on Amazon Web Services (AWS). To achieve this, use the methods described in the following sections.


When your client, data source, and ArcGIS Enterprise are not deployed in the same location, you will likely experience degraded performance when data is sent between an on-premises component and the cloud.


You can connect to an ArcGIS Server site on AWS from an installation of ArcGIS Pro on your on-premises machine and register both your local enterprise geodatabase and an enterprise geodatabase on AWS, publish a geodata service of the geodatabase on AWS, and use the geodata service to replicate data from the local geodatabase to the geodatabase on AWS.


When you create a stand-alone ArcGIS Server site using an Esri 10.7 or a 10.6 or older Amazon Web Services CloudFormation template provided by Esri, a geodatabase is created (egdb) and registered as the ArcGIS Server site's managed database. When you publish a feature or WFS-T service, a copy of the data will be moved to the managed database. When you delete the feature or WFS-T service, the corresponding data is deleted from the managed database.

ArcGIS Enterprise deployments include ArcGIS Data Store. The relational data store configured through ArcGIS Data Store acts as the hosting server site's managed database. When you publish hosted feature layers to the deployment, data is copied to the relational data store.

When you use a CloudFormation template provided by Esri to deploy ArcGIS Enterprise, a tile cache data store is also created. This allows you to publish hosted scene layers to the portal, and the scene caches will be copied to the tile cache data store.

Load data you move to the cloud

If necessary, you can also physically move data to AWS and load it into the geodatabases in your deployment.

First, move the data to Amazon Web Services.

Once your source data has been moved to AWS, you need to sign in to an Amazon Elastic Compute Cloud (EC2) instance where ArcGIS Pro is installed to connect to the source data and the geodatabase on AWS, and load the data into the geodatabase.

From ArcGIS Pro, you can do the following:

  • Copy data from a source file you transferred to AWS, such as a file geodatabase, and paste the data into an enterprise geodatabase on AWS. See Copy feature datasets, feature classes, and tables to a geodatabase in the ArcGIS Pro help for more information.
  • Create an empty feature class or table and use a source XML record set document that you uploaded to AWS to load data to the feature class or table.
  • Use geoprocessing tools to import source shapefiles, feature classes, tables, rasters, or XML workspace documents that you moved to AWS.

For more information about getting files and other source data onto an Amazon Web Services instance, see Strategies for data transfer to Amazon Web Services.