And I think that's been around for at least 8 years - I remember looking at it in 2015 - or maybe 2016(?). Was working with a small startup that needed a small bit of hosting, and they were trying to do it all at AWS because... name cachet. They were getting lost in trying to cobble together lambda, s3 and some other stuff to basically host some JS and images. I suggested Linode (had a working example) but "that's not enterprise" (this was a small pre-revenue startup testing ideas). I then suggested (and setup) a lightsail instance for $5/month doing what was needed, and it too was rebuffed as not enterprise(y) enough. Even being 'at AWS' wasn't enough to start with - they wanted to hit the ground running with lambdas, microservices, multi-region load balancing and complex IAM stuff.
Stated justification was "If we don't bake this in now, it'll be harder to do later", but it was mostly a couple fokls in charge wanted to learn new stuff (someone said that out loud later, confirming my concerns about resume-driven-development).
EDIT: FWIW, my couple small experiences with lightsail itself were fine. Seems like a decent onramp to ease in to the AWS ecosystem, if that's on your roadmap.