[maxbond]

The takeaway should be, "I should understand the system I'm deploying, regardless of the tool I'm using for search." You relied on ChatGPT to design your deployment strategy and to understand it for you. And consequently you were surprised when it didn't perform the way you expected and you were put on the spot to build a better understanding in order to respond to an incident.

Asking ChatGPT for downsides might be a good exercise, but that's not addressing the root of the issue. If that's all you do then you're still relying on ChatGPT to understand the system and anticipate issues for you. Unless it's ChatGPT's responsibility to maintain the system and ChatGPT's reputation at stake when it suffers incidents, then that prospect should make you uncomfortable.

Consider for instance that it's not uncommon for ChatGPT to have downtime. What are you going to do if your system is down and, by coincidence, so is ChatGPT?

[wink]

In OP's defense, people have misunderstood spot instances years before ChatGPT existed. IMHO it's just not messaged very clearly in AWS. Yes, RTFM and all that, but I think it's easy to miss. And yes, AWS is basically the only place I've ever deployed something VPS-/instance-like where there it was not clear if this is kinda ephemeral, if they even have that option.

[maxbond]

I don't mean to indict or attack OP. To the extent that I come across that way, I've failed in my editing.

I respect them for taking this as a learning experience and for being open about it.