AWS Workspace to AWS Enterprise - Performance issues?

[AmyCleare]

Has anyone had any experience connecting to Enterprise Portal on AWS from an AWS workspace? We are in a production editing team and need to move into this configuration but are concerned about responsiveness. Has anyone configured their digitizing/editing production team in this way? Thanks. 

[tigerwoulds]

There's a ton of variables here but in general, we've had great success with using ArcGIS Enterprise via Workspaces. 50% of our users edit their data via feature services in a Portal web map or app. The other half have Pro installed on their workspace and edit their data there. A lot of our end users mention that editing/geoprocessing is much faster via the workspace than on their local machines. 

[MikeSchonlau]

We've used Workspaces here and there over the years, but we still connect to Portal & AGO in ArcGIS Pro from other EC2 instances daily and have since Pro was first launched. In all instances, performance has been a significant improvement over local networks. Most organizations cannot match the infrastructure that the cloud providers offer - unless all of your users are located in one place with a fast LAN and good internet capacity. The good news is that you can test this performance fairly easily. Even if you don't have Enterprise Portal set up in AWS yet, you could try connecting Pro on Workspaces to AGO-hosted features to test out performance. Either way, one of the best features of cloud computing is how simple is to set up a test/dev environment.

[jcarlson]

@MikeSchonlau  We're moving in that direction with our setup, but how are you hosting your licenses? We've still got users who work in non-cloud settings, and we've had issues getting our License Server Administrator accessible to both.

[MikeSchonlau]

We don't use the License Server Administrator with Pro. We run all of our license management through AGO or Portal. We do still have a few License Server Administrators running locally for our ArcMap stragglers. Early on, we just split our licenses between an on-prem License Server Administrator and another one running on an EC2 instance in AWS.

[jcarlson]

Ah, we've moved all our Pro licenses off of AGO, as we exclusively use Portal. So, is the EC2 LSA the one registered to your Portal for named users? We'd like to avoid messing with concurrent / single use license and do everything with named users, but my understanding was that you can't have two LSAs registered to authenticate named users.

[MikeSchonlau]

The remaining LSA we have is only used by non-Pro users on premise. We have never used the LSA to manage Pro licensing. We've always done that through AGO and now starting to manage some of those with Portal. Most of our Pro users use both Portal and AGO, but their licensing is managed by AGO. They can still edit feature services hosted in both environments that way. No LSA in play for us with our Pro users.