topic Re: High available ArcGIS Server config-store on AWS DynamoDB in ArcGIS Enterprise Questions

High available ArcGIS Server config-store on AWS DynamoDB

DriesHerzeel2 — Wed, 24 Oct 2018 08:43:17 GMT

Hi,

We are deploying an ArcGIS 10.5.1 Windows Enterprise setup to AWS and need to configure a highly available ArcGIS Server with a shared configuration store on AWS storage services, following the steps described in the link below.

https://enterprise.arcgis.com/en/server/10.5/cloud/amazon/configure-shared-configuration-store.htm

Following these steps, we got stuck on step 11. No content was created in the S3 bucket.

We did create an AWS S3 bucket but no AWS DynamoDb instance.

Basically we need to know which steps to follow to place the ArcGIS Server config store manually on AWS S3 / DynamoDB.

Do we have to create the dynamodb table ourselves or is it done by the software?
If we have to create it, what is the primary key and all the other attributes that we need to create?

We can't make use of existing ESRI AWS AMI's, because of internal security policies, and want to do the installation manually instead of using Chef cookbooks.

Thx in advance!

Re: High available ArcGIS Server config-store on AWS DynamoDB

BenjaminMillard1 — Tue, 26 Mar 2019 18:34:07 GMT

I know this is several months late, but I ran into the same problem while attempting to do the same exact thing. The problem is with Esri's documentation, specifically the s3/DynamoDB step. In their documentation, the connection string is horribly malformed and is not JSON. The actual connection string should look like:

{
"type":"AMAZON",
"connectionString":"NAMESPACE=<Name of your Bucket>;REGION=<AWS region e.g us-west-2>;"
}

{
"type":"AMAZON",
"connectionString":"NAMESPACE=<Name of your Bucket>;REGION=<AWS region e.g us-west-2>", "connectionSecret":"ACCESS_KEY_ID=<Your AccessKey>;SECRET_KEY=<Your Secret Key>;"
}

Using a colon instead of an equals sign.

Hope this helps.

Ben

Re: High available ArcGIS Server config-store on AWS DynamoDB

JonathanQuinn — Tue, 26 Mar 2019 21:19:55 GMT

Thanks for bringing this to our attention, we'll get it corrected in the documentation.