Latest Contributions by RyanUthoff

I am in a similar situation where we are deploying ArcGIS Enterprise in AWS for the first time. First of all, it possible that ArcGIS Enterprise could have been deployed using an AWS AMI as well. At the software level within the VM, I am not sure if there are any differences between the AMI and CloudFormation. Using the AMI, we experienced the same things. Nothing (except ArcGIS Server) was running and all of the services had to be turned on. To answer your question about GeoEvent Server, that service is deployed in every instance when using the AMIs. Regarding the steps you listed, you essentially need to follow the ArcGIS Enterprise base deployment installation steps to get started. The only difference is that all of the software has been installed, just not configured. The ports have also been opened in Windows Firewall, but you'll also need to make sure they are open within AWS as well. To setup your ArcGIS Enterprise, you will need to create your server and portal site and configure your web adaptors. You are definitely on the right track with the steps you listed. You will need to: Configure Portal (create Portal) Configure Portal web adaptor Configure Server (create server site) Configure server web adaptor You didn't mention Data Store, but you can configure that as well. Obviously, there could potentially be a lot more steps depending on your deployment needs, but that's a good starting point. Also, don't forget to set your services to start automatically (such as Portal, Server, etc.). Otherwise, if you have a machine restart, it won't start those services automatically. Regarding licensing, I believe Esri follows the bring your own license model. So a CloudFormation/AMI will NOT have any licensing. You will need to contact your Esri account representative to obtain licensing information. There isn't any special AWS licensing or anything. The licensing is the same whether or not you use it on-premise or in the cloud. Unfortunately, Esri's documentation regarding AWS AMIs/CloudFormation is very......lacking. I understand that Esri can't necessarily provide documentation regarding AWS configuration, but it would be nice to have some documentation regarding the VMs itself. Such as, what is already pre-configured? What is turned on/off by default? I had to figure everything out on my own. Anyway, I hope that helps! I think what you are experiencing is "normal." You just need to continue with the configuration as if you were doing an on-premise deployment. ... View more

We actually encountered this issue yesterday. It turns out, the shape column had a NOT NULL constraint on it. It must be configured to allow nulls.   Unfortunately, Esri's 999999 error message did not specify which column it was referring to, so we had to go down the rabbit hole of figuring that one out. I also can't find any Esri documentation that states that this is a requirement of the shape field. Another failure of Esri's documentation.   Esri, if you are going to provide an error message, please provide documentation on how to fix it. I'd also recommend not giving general 999999 error message when the error message clearly lists a specific error. It's not a general error if the error message knows what the problem is. ... View more