14 May 2021 06:41 AM - last edited on 30 Jun 2021 06:28 AM by MaciejNeumann
Are there issues with baking the OneAgent into an AWS AMI, so it is included for all resulting EC2 instances? My first take is that there is some registration guid or hostid that's created at install of OneAgent that would not be unique for all resulting EC2 instances, but I'm not sure how it works under the hood.
Solved! Go to Solution.
I chatted with support and got this response: the IDs will be regenerated in the AMI, and this improvement was added in Version 1.197. So to answer your question, baking the OneAgent into an AWS AMI should be all good and the IDs will be taken care of, as long as the version is higher than 1.197.
is there a good DT document on adding DT into AMI for EC2?