Hi,
I've tried clicking the "Apply now" button on the Elastic Beanstalk > Managed updates overview page, but when I do so and the managed update starts running, it soon reverts back to the original with the following error:
FAILED - RollbackSuccessful Successful abort of the Managed Action.
Or in detail:
Failed to deploy configuration.
Service:AmazonCloudFormation, Message:Stack named 'xxx' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBEIP].
Creating EIP failed Reason: The maximum number of addresses has been reached. (Service: AmazonEC2; Status Code: 400; Error Code: AddressLimitExceeded; Request ID: xxx; Proxy: null)
I haven't experienced these before and I wonder why could that be. It is true that there are 5 Elastic IP addresses already occupied in the same region, however either it was the case before too or I didn't notice that, but I thought that running a managed update will still make the container continue using the same IP it was assigned before.
Could you please confirm/shed some more light on why is that the case and if I e.g. need to have one free IP address slot in the list of Elastic IP addresses so managed updates to work?
I've not been able to find an answer to this particular question hence asking here.
Thank you!