The enterprise geodatabase (or geodatabases at 10.6) included when you create a stand-alone ArcGIS Server site using ArcGIS Server Cloud Builder on Amazon Web Services or Esri CloudFormation templates do not require any configuration before you can access them. However, you can perform some administration tasks, such as creating another geodatabase, creating roles or groups, or moving data between instances, if your workflow requires it. Listed here are some of these optional advanced administration tasks, tools used to perform them, and links to documentation with further instructions.
The ArcGIS Server sites created with Cloud Builder or CloudFormation templates come with default roles to administer geodatabases in PostgreSQL, Microsoft SQL Server, and Amazon Relational Database Service (RDS) and load spatial data to them. (See Geodatabases on Amazon Web Services for a list of these default roles.) You may require additional roles to manage your spatial data. For example, you may want to add a login that has read-only privileges in the database, require a login with a name other than the default name provided with the Esri Amazon Machine Image (AMI), or want additional data owner logins in the database.
If you want additional logins that can own data, you can use the Create Database User geoprocessing tool or a Python script to create a new login.
If you want to create logins that can only view data, use SQL or your database management system (DBMS) tools to create the logins. See PostgreSQL, Microsoft SQL Server, or Amazon RDS documentation for more information.
Create additional geodatabases
If you choose to include enterprise geodatabases with your ArcGIS Server site on AWS you create with Cloud Builder or Esri CloudFormation templates, the instance comes with two geodatabases: egdb and geodata. To create additional geodatabases in PostgreSQL or SQL Server—for example, if you want a geodatabase with a different name or you require additional geodatabases for different services or applications to access—you can use the Create Enterprise Geodatabase geoprocessing tool. To create another geodatabase in Amazon RDS for SQL Server or Amazon RDS for PostgreSQL, use the Enable Enterprise Geodatabase tool.
After you create an additional geodatabase, connect to the database as an administrator and add any schemas or users you require.
To create additional workgroup geodatabases, connect to the database server from ArcMap as a database server administrator and create a geodatabase. See Create additional workgroup geodatabases for more information.
Esri supports the use of the PostGIS geometry type in enterprise geodatabases in PostgreSQL. If you use Amazon RDS for PostgreSQL, PostGIS is already installed and used for spatial data storage. If you are using a traditional PostgreSQL database cluster on Amazon, you can download a supported version of PostGIS and install it on the AWS instance where PostgreSQL resides (either the same instance as ArcGIS Server or a separate instance).
To use PostGIS geometry or geography in a traditional PostgreSQL database cluster, the database that contains your geodatabase must be enabled to use PostGIS. Since PostGIS is not part of the basic AMI, the default geodatabase is not enabled to use PostGIS. Therefore, after you install PostGIS, you must enable your geodatabase to use it. Once it is enabled, new data you add to the geodatabase can use the PostGIS geometry or geography type by specifying the PG_GEOMETRY or PG_GEOGRAPHY configuration keyword when you create or import the data. Existing data continues to use the ST_Geometry storage type.
After you have installed PostGIS and enabled a database to use it, you may want to create your own AMI to preserve the current state of your machine. See Create your own AMI for more information.