ArcGIS Portal Content Directory AWS S3 Bucket

Anonymous User

We set up Portal 10.8.1 on an Ubuntu EC2 instance and set up the content directory to a local directory. We thought we needed to set it up here and then move it to an S3 bucket based on these instructions

https://enterprise.arcgis.com/en/portal/latest/administer/linux/changing-the-portal-content-directory.htm

We copied the contents of the content directory to an S3 bucket, but when we use Portal Administrator to change the content directory to the S3 bucket, we get the following errors in our log files.

"The content directory has no groupinfo directory under the items directory.
The Portal site has been initialized and configured but is currently not accessible, because the content directory is not available. This may be due to incorrect permissions, a file server hosting the directory being unavailable, or network issues. As a last resort, if the content directory can not be recovered, then uninstall the software, re-install, and restore from a backup.
Health Check failed, the portal is not ready."

Here is our content directory path:

{
"type": "cloudStore",
"provider": "Amazon",
"connectionString": {"region": "<our-selected-region>","credentialType": "IAMRole"},
"objectStore": "<portal-bucket-name>"
} 

Whenever we change this back to the local directory, everything works fine. There was a portal-config.properties that was written to the S3 bucket, so we know portal is connecting to the bucket.

We have also tried to reindex everything. Any thoughts would be greatly appreciated.

Anonymous User

We decided to spin up another EC2 instance and install Portal. Then configure this to put all the site contents into the S3 bucket rather than set it up locally and move it to the S3 bucket. After doing this, we realized that we copied the contents of the "<install location>/usr/arcgisportal/content" folder up to the S3 bucket. We should have copied the contents of the "<install location>/usr/arcgisportal/content/items" folder to the S3 bucket. Then I assume our first instance of moving the local contents to the S3 bucket would have worked properly.