Let me ask you two questions about the behavior of ENIs during failover.
◼
·Connecting to the instance using a private IPv4 address
◼
I would like to know how to quickly forward traffic to the standby instance.
It seems that the following actions are correct.
What are the actions (1) and alternatives (2) on ENIs in the event of an actual failover?
·Connect a secondary ENI to an instance configured with a private IP address.
·Move ENIs to the standby instance for the primary instance.
(1) Operation during ENI failover
If I do the following, will failover occur automatically in the event of an AZ failure?
Do I need to manually detach and attach the instance?
·Create a secondary ENI that can be migrated to a failover instance
·Assign secondary private IP addresses to ENIs
(2) ALB Weighted Routing Failover
ALB weighted routing allows failover, so
I thought it would be unnecessary to prepare ENIs as primary and secondary, but is it wrong to recognize them?
Note:
How do I configure a weighted target group for the Application Load Balancer?
Also, could you tell me what is wrong with the following actions?
Deploy the ALB configured on the listener for the private IP address and register the primary instance with the load balancer.If a failure occurs, unregister the instance and register the secondary instance.
aws amazon-ec2
As I pointed out in the comment, I will answer the current question.
I will deny EC2, but if you want to operate it stably, you should make it serverless such as Lambda.Instances are provided on request to ensure applications run, and management networks are no longer required.
If you're going to do it with EC2, you're going to have to do both in an Active-Active configuration.Then, if you let ELB sort it out, it will sort it out to the other even if one stops.
When you are forced to configure Active-StandBy, I personally do not recommend replacing ENIs.First, the subnet closes to AZ, so you cannot take over the private IP address across the AZ.If something else could be done, the OS and applications would need to know the ENI and private IP addresses, while the processing would be interrupted.
In such cases, AWS uses the Elastic IP address.
Elastic IP addresses allow you to quickly remap addresses to another instance in your account to mask instances and software failures.
is described as .
The Elastic IP address is a NAT feature provided by AWS.Communications destined for the Elastic IP address are translated to the private IP address assigned at that time.Therefore, as soon as the Elastic IP address is switched, it is routed as communication to that machine.Each machine is treated as a communication to itself, so you can switch almost without interruption without having to reconfigure the operating system or application.
© 2024 OneMinuteCode. All rights reserved.