AWS Elastic IP vs ENI für ArcGIS Enterprise in der Cloud

Question

Hallo,

In der neuesten Dokumentation für Deploy a base ArcGIS Enterprise portal on AWS—ArcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise wird die Verwendung einer Elastic IP beschrieben, die Probleme verursacht, wenn eine EC2-Instanz gestoppt/gestartet wird und die Elastic IP von der Instanz getrennt wird.

Ich dachte, der bessere Weg wäre die Verwendung eines Elastic Network Interface (ENI), das an eine Instanz angehängt bleibt und das Problem beim Stoppen/Starten der Instanz beseitigt.

Kann jemand Probleme damit erkennen oder hat das schon selbst in AWS gemacht?

Vielen Dank für Ihre Zeit.

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.