I've been working with AWS Backup to set up a backup and restore standard operating procedure, but I've run into some challenges. One issue is password recovery, and another relates to needing to restore instances with the same IP address. I'm interested in recommendations for third-party backup solutions that could make the backup and restore processes simpler. Ideally, I'm looking for a solution that can automate the moving of Elastic Network Interfaces (ENIs) from the old instance to the new one and handle these kinds of tasks seamlessly. Any suggestions would be greatly appreciated!
4 Answers
To avoid issues with IP addresses, it’s better to configure your applications to communicate with instances using DNS rather than fixed IPs. You could set up a startup script on your instances to automatically update their own DNS records during boot.
You can't actually move the ENI to a new instance; you'd have to terminate the old instance and create a new one. The only exception is if you have a secondary ENI, which you can move. Regardless, the general advice here is to stick with using DNS.
Restoring with the same IP isn't too complicated if you're using AWS's basic features, but I'm curious why that requirement is so important. It's not really a good practice in terms of idempotency.
Are you trying to restore public IPs or private IPs? That distinction could impact your approach.
Many people use AWS Backup precisely because their instances aren’t idempotent. If you're deploying from GitHub to an ECS cluster, you probably wouldn’t need AWS Backup, but if you have a custom Windows server that was manually set up, then AWS Backup makes sense.