We have deployed ArcGIS Enterprise 10.9 on AWS to conduct some Utility Network testing. Our issue is that when we try to log in to our portal via ArcGIS Pro we are getting nothing. We are entering the correct usernames and passwords because when we enter incorrect ones we see the error as well as a log entry on the portal. We have used this instance for prior testing on ArcGIS Enterprise 10.8.x without much trouble. When we first try to log in on a new machine, Pro will display a certificate warning, but no matter what we select (add cert, continue, etc.) we aren't able to log in. We are using an Amazon signed certificate created from their Certificate Manager service and have it assigned to a load balancer that is forwarding to our EC2 portal instance. We are able to connect and log in without any errors or certificate issues via a web browser so we are fairly confused at this point.
Solved! Go to Solution.
We ended up figuring out our issue using Fiddler. When accessing the portal via a web browser, everything looked fine and there were no obvious issues when looking at network traffic with Fiddler. When accessing via ArcGIS Pro, we noticed CONNECT attempts to the machine name where the web adapter was located. After some digging around we found the web adapter settings in the portal admin settings under /system/webadapters. For some reason, the web adapter's URL was set to https://machinename/portal. This was very surprising and we ended up trying a few things to correct this without damaging the web adapter's configuration. We were able to change the values of the web adapter to use our FQDN by adding /edit to the end of the address in the address bar. We then restarted the machine to ensure the changes were taken into effect and it worked! Full disclosure, we are not sure how this happened to begin with as this is a testing environment that gets used on occasion, and we aren't sure if our solution would be considered proper.
We ended up figuring out our issue using Fiddler. When accessing the portal via a web browser, everything looked fine and there were no obvious issues when looking at network traffic with Fiddler. When accessing via ArcGIS Pro, we noticed CONNECT attempts to the machine name where the web adapter was located. After some digging around we found the web adapter settings in the portal admin settings under /system/webadapters. For some reason, the web adapter's URL was set to https://machinename/portal. This was very surprising and we ended up trying a few things to correct this without damaging the web adapter's configuration. We were able to change the values of the web adapter to use our FQDN by adding /edit to the end of the address in the address bar. We then restarted the machine to ensure the changes were taken into effect and it worked! Full disclosure, we are not sure how this happened to begin with as this is a testing environment that gets used on occasion, and we aren't sure if our solution would be considered proper.
Hi Corey,
When you connected ArcGIS enterprise on AWS via ArcGIS Pro, did you have any performance issues to conduct analysis on Pro? I assume you installed ArcGIS Pro on your desktop.
From https://enterprise.arcgis.com/en/server/latest/cloud/amazon/geodatabases-and-arcgis-server-on-aws.ht... it's noted that "Geodatabases in AWS are not intended to be accessed directly from on-premises ArcGIS clients, as performance will be far slower than when the geodatabases are accessed from ArcGIS clients on AWS."
Could you please share your experience and observation in using ArcGIS enterprise on AWS via ArcGIS Pro?
Thanks,
Xuan