AWS Elastic IP vs ENI para ArcGIS Enterprise na nuvem

Question

Olá,<\/P> Na documentação mais recente para Implantar um portal base do ArcGIS Enterprise na AWS rcGIS Enterprise na nuvem | Documentação do ArcGIS Enterprise<\/A> fala sobre o uso de um Elastic IP que apresenta problemas quando uma instância EC2 é parada\/iniciada e o elastic ip é removido da instância.<\/P>Eu pensei que a melhor forma de fazer isso é usar uma Elastic Network Interface (ENI) que permanece anexada a uma instância e elimina o problema da parada\/início da instância.<\/P> Alguém vê algum problema com isso ou já fez isso na AWS? <\/P> Obrigado pelo seu tempo com isso.<\/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.