Answers like this do not need to be CW, we just need to be wary of attracting many low quality answers to any question which does not have a specific answer. The issue in this case is the question - and I think the problem with the question is the research gap. To me, although I don't have a specific answer, I assume that there are tons of platforms which make ideal tester devices for AWS. This makes me assume that the OP has not done any research.
How do I get started will be a common question, and is for sure too general. There are just too many points in the stack that a specific person will want to develop their skills. Right through from custom ASIC, to data learning and eventually up to packaged platforms. Cross this with the target market (smart home, cities, building, industrial, agricultural) and there is a huge space.
This site is not best suited for writing tutorials, be it for AWS test data or any other niche. Ideally, the answer to this question would be to link to the appropriate AWS documentation and explain how it is relevant. Otherwise we are inviting every eval platform to provide an answer.
In the spirit of what we have been doing with closed questions all along on this site, I think the best approach is to try and edit the question so that this answer is good and specific. Then the OP gets a few points, and pointers about what the site expectations are, and might go on to ask a question that is actually relevant to them.
Also, I don't have a huge issue with closed but answered questions. They persist, and don't necessarily need to be deleted. We can still link to/from them, and this can help to guide others in the future.
