2 Answers
- Newest
- Most votes
- Most comments
1
When a new instance is created (as is done during most failover/failback processes) it gets a new instance identifier (I think that's what you mean by UUID).
You might be able to achieve what you want by always having the instance in a running or shutdown state (i.e. they've been created and are waiting to be activated) but there is extra cost involved there.
Why is it important to have the same instance id?
1
How are you running your DR tests. If an instance is terminated, and recreated it will have a different UUID. Would recommend using the below blog for non disruptive tests of EDR. https://aws.amazon.com/blogs/storage/how-to-perform-non-disruptive-tests-with-aws-elastic-disaster-recovery/
answered 23 days ago
Relevant content
- asked 7 months ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thank you. one of our legacy app using this identifier for custom billing purpose. so we want to maintain the same identifier for total billing purpose.
Have you considered using tags instead of the instance identifier?