AWS Elastic IP vs ENI pro ArcGIS Enterprise v cloudu

Question

Ahoj,<\/P> V nejnovější dokumentaci pro Deploy a base ArcGIS Enterprise portal on AWS rcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise<\/A> mluví o použití Elastic IP, které má problémy, když je EC2 instance zastavena\/spuštěna a elastic ip je z instance odebrána.<\/P>Myslel jsem, že lepší způsob je použít Elastic Network Interface (ENI), která zůstává připojena k instanci a odstraňuje problém se zastavením\/spuštěním instance.<\/P> Vidí někdo nějaké problémy s tímto nebo to někdo dělal sám v AWS?<\/P> Děkuji za váš čas.<\/P>

MarceloMarques · Answer

Note, it is easier if you use the "AWS Cloud Formation Templates" or the "ArcGIS Enterprise Cloud Builder Tool" to Deploy ArcGIS Enterprise in AWS.

AWS CloudFormation and ArcGIS—ArcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise

ArcGIS Enterprise Cloud Builder for Amazon Web Services—ArcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise

If you are trying to perform a manual deployment of each ArcGIS Enterprise component ( Portal / Server / Datastore / WebAdptors) then this can be very challenging if you are not an experience ArcGIS Enterprise Administrator.

Deploy a base ArcGIS Enterprise portal on AWS—ArcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise

MarceloMarques · Answer

Indeed, an Elastic IP can be created in the AWS Console for EC2 and then the Elastic IP assigned to the EC2 Instance, then the EC2 Instance Public IP will be the Elastic IP and if you power off / on the EC2 Instance the Public IP will not change. I hope this clarifies.

jcarlson · Answer

I thought the point of getting an Elastic IP was that the IP address of your instance does not change upon starting/stopping the instance.

We use that configuration, and have gone through half a dozen maintenance cycles, starting and stopping our instances, and have never had an issue.

Can't speak to the ENI, though, sorry.