Hello,
On ArcGIS Enterprise, it is possible to configure a custom S3 region when registering a cloud store:
But I am under the impression that it is not supported for webgisdr ... ? There is no variable for the S3 private URL:
https://enterprise.arcgis.com/en/portal/latest/administer/linux/create-web-gis-backup.htm
Seems strange: did I miss anything ?
Thanks
Solved! Go to Solution.
You should be able to create the regionsforcloudstorage.dat file within the webgisdr tool folder. Somewhat follows this doc:
https://enterprise.arcgis.com/en/server/10.6/administer/linux/configure-regions-for-cloud-stores.htm
but move it into the webgisdr tool folder instead. There is a bug about it not working when it's in framework\etc, which should work:
BUG-000138487 WebGISDR tool does not recognize custom entries in regionsforcloudstorage.dat file in Portal's framework/etc directory
Workaround:
Download regionsforcloudstorage.dat file from http://arcgisstore105.s3.amazonaws.com/regionsforcloudstorage.dat and append necessary region to JSON. Save file and place in <Portal installation directory>/tools/webgisdr directory, then re-run WebGISDR tool.
Example JSON for ap-east-1:
{
"name": "Hong Kong",
"id": "ap-east-1",
"s3endpoint": "s3.ap-east-1.amazonaws.com"
},
S3 Endpoints can be referenced from https://docs.aws.amazon.com/general/latest/gr/s3.html
You should be able to create the regionsforcloudstorage.dat file within the webgisdr tool folder. Somewhat follows this doc:
https://enterprise.arcgis.com/en/server/10.6/administer/linux/configure-regions-for-cloud-stores.htm
but move it into the webgisdr tool folder instead. There is a bug about it not working when it's in framework\etc, which should work:
BUG-000138487 WebGISDR tool does not recognize custom entries in regionsforcloudstorage.dat file in Portal's framework/etc directory
Workaround:
Download regionsforcloudstorage.dat file from http://arcgisstore105.s3.amazonaws.com/regionsforcloudstorage.dat and append necessary region to JSON. Save file and place in <Portal installation directory>/tools/webgisdr directory, then re-run WebGISDR tool.
Example JSON for ap-east-1:
{
"name": "Hong Kong",
"id": "ap-east-1",
"s3endpoint": "s3.ap-east-1.amazonaws.com"
},
S3 Endpoints can be referenced from https://docs.aws.amazon.com/general/latest/gr/s3.html
Hi @JonathanQuinn,
Thanks for your reply.
Indeed, your workaround does work but I wonder about the perenity: the documentation you linked about the 'regionsforcloudstorage.dat' file is from 10.6 and is removed starting from 10.8.
Why not including this type of configuration in the webgisdr config file directly ? Is it something you are trying to improve or something you are trying to get rid ?
Will it break at the next release 🙄 ?
Thanks,
Nicolas
Hi @JonathanQuinn ,
Any thought about the future of "Configure ArcGIS Server to access a local file" ?
Is it safe ? It's still gone from the documentation.
Thanks
It is still safe, I'm not completely sure why it was removed. The only reason why you'd want to use that file is if you're trying to use a region that isn't already supported by the SDK that we are using. If that's the case, the DR tool should look at a local file first and if it can't find it, look for the one in portal, which is the bug. We'll address that, but moving forward, it'll still expect that non-default regions are added to a manually created regionsforcloudstorage.dat file. I'll see what we don't have that documentation anymore.
Hi @JonathanQuinn ,
Thanks for the confirmation. Please let me know if you get any interesting information about non-default regions. I find the documentation really light about it now only for webgisdr backups (cf. https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/portal-for-arcgis-content-on-...).
Thanks !