ArcGIS Pro for Portal on AWS

[JohnPlunkett]

We have deployed a 10.6 Enterprise instance on Amazon Webservices

Installed a License Server configured the Pro Licenses for Portal assigned licenses etc...

When we use ArcGIS Pro on the Amazon Instance it works

However if we try and use the Pro License off the AWS we can't connect, it times out.

However we can add that portal and publish to it. (but we cant use that Pro License)

How have users got around this?

[AmnoyAm · Accepted solution]

The following is a section of the ArcGIS Pro documentation concerning Named User licensing in ArcGIS Enterprise:

When you sign in to ArcGIS Pro with your ArcGIS Enterprise user name and password, ArcGIS Enterprise validates your membership in the portal organization and confirms that you are licensed to use ArcGIS Pro. ArcGIS Pro then contacts ArcGIS License Manager to obtain a license. If a license is available, ArcGIS Pro starts. In this part of the process, ArcGIS Enterprise does not communicate with the license manager.

In your situation, the Portal is externally accessible but the license manager is not.  It sits behind a fire within AWS environment.  You will need to configure the license manager to work through the firewall which includes the following:

   1.  Locking down ports for the license manager daemons, arcgis.exe and lmgrd.exe. 

   2.  Create an exception through the firewall for the two ports specified. 

Here's a documentation to guide you through the process:

Configure ArcGIS License Manager to work through a firewall—License Manager Guide | ArcGIS Desktop 

[BrettMarraccini]

Hello, is there an updated version of this flow for 10.7 Portal?  We have the same issue - ArcGIS Pro on our AWS ec2 instance can connect to Portal and sign in as a named user, but when I attempt to do the same via my local laptop (outside aws) i keep getting errors when Pro attempts to connect to our license server on the same ec2 instance.

I have static IP address to that instance, and have ensured port 27000 is open in/outbound.

[BrettMarraccini]

I was able to resolve this by configuring the hostname of our license server in the Portal Admin Directory.

The hostname should be the fqdn address of the ec2 instance, as in 'ec2-ip-ad-dre-ss.us-west-2.compute.amazonaws.com' and port should be 27000

After changing this setting, and ensuring that port 27000 was open on both our inbound/outbound server rules and our ec2 security group rules, we were able to successfully connect to the license manager from our remote locations and retrieve our ArcPro licenses.