Before the instance is spun down the UDR data should be transferred to the GWS UDR data repository.
If it is not transferred, the data will not be processed.
You can use your own method for data transfer or best1collect.exe -p PULL .
You can get a list of available UDR data via best1collect.exe -p LIST from the GWS.
The UDR data prior to the spin down would be preserved minus the last spill (usually 15 minutes).
Make sure to put the data in the same place where the manager run expects it.
For that to work it seems like the gateway server would need to know that the EC2 instance was going to spin down. Has any thought been given to having the agent handle this situation?
The GWS would only see that it can't contact the agent. Adding instances is different then removing existing instances If it is a matter of an agent being restarted. This works perfectly well, the UDR data will continue to be collected and when the time comes will be transfered.
I agree that the GWS would only see the agent can't be contacted which is why it seems like the solution would be for the agent to push the UDR data prior to the instance being spun down.
Push is not a viable solution due to firewalls.
All transfer is initiated from the GWS to the agents.
If you can send the request to collect the data, you can send a request to get the data.
To revisit the instance issue.
If the instance has the same name (same name in the agent list), and you restart it, without modifying the install, the data will continue to be collected and transfered after the instance is restarted.
If you have a new name, that name will have to be created as a new entity in the agent list.
in addition, if you continue to create new instances, that will be reflected in your license report. (Each new instance will be treated as a new license entity).