amazon web services - Why does Elastic Beanstalk create new EC2 instances when I change my EB settings? -


If I make a configuration change in the Amazon EB interface (for example, changing the EC2 key / pair or monitoring interval) , The EB will close the current EC2 example and create a new one. Why does not it use the current EC2 example? Is there any implication for accumulation of EC 2 examples? Some EC2 example properties (key pairs and others) are irreversible, therefore elastic beanstock need to be made a new one. Excluding property replaced with similar properties. There is no implication for the collection of finished examples, but it will charge for a new example. For example, if you change the property 2 times an hour, you will be charged for 3 hours.

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -