Newly added to AWS instance elastic IP address replaced the previous one in Plesk

Symptoms

• A second elastic IP address was added to the AWS instance, where the Route53 extension is used.
• After some time or after the reboot all websites became unavailable.
• In Plesk, the second IP address only can be seen in Tools & Settings > IP Addresses 
• All DNS records in Domains > example.com > DNS Settings were rewritten to use the second IP only.

Cause

This issue is caused by a Plesk bug #PPPM-7796, that is going to be fixed in future Plesk updates. 

Resolution

Until a fix becomes available, the following workaround may be used:

1. Connect to the server over RDP.
2. Go to Start > Task Scheduler > Task Scheduler Library > Prepare Public IP > right click - Disable.
3. Use manual mapping in the Plesk panel by assigning the first and the second public IPs to private IPs in Tools & Settings > IP Addresses