AWS Elastic IP vs ENI para ArcGIS Enterprise en la nube

Question

Hola,

En la documentación más reciente para Implementar un portal base de ArcGIS Enterprise en AWS—ArcGIS Enterprise en la nube | Documentación para ArcGIS Enterprise se habla sobre el uso de un Elastic IP que presenta problemas cuando una instancia EC2 se detiene/inicia y el Elastic IP se desconecta de la instancia.

Pensé que la mejor manera de hacer esto es usar una Interfaz de Red Elástica (ENI) que permanece adjunta a una instancia y elimina el problema al detener/iniciar la instancia.

¿Alguien ve algún problema con esto o lo ha hecho por sí mismo en AWS?

Gracias por su tiempo con esto.

MMBR · 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

MMBR · 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.