There are easier ways _depending on the context of what you already know_. There are better ways depending on what you're optimizing for. For you I bet this will be hard to beat. For me, I'd probably throw it in AWS S3, because that's what I know without having to think about it or do much work.
Containers and other such things are more for when you need different things, like a dynamic site or backend async processing, or not a site at all, and especially when you need some/all of that and are tired of sysadmining a VM.
S3 is the right answer for anyone with even passing familiarity with AWS. Bit of a pain that HTTPS requires cloudfront, but otherwise the dead-simplest way of getting HTML to a browser.
As an exercise a few months ago I tried deploying a static site to a freshly purchased domain on netlify, start to finish I found it took less time than any aws workflow and gave me free inbound forms.
I say this as a very experienced aws and s3 user who also has several static and dynamic sites on s3 buckets, VPS & ECS.
netlify for simple static sites is a simpler and faster workflow with https and forms as 0 config and free.
There are easier ways _depending on the context of what you already know_. There are better ways depending on what you're optimizing for. For you I bet this will be hard to beat. For me, I'd probably throw it in AWS S3, because that's what I know without having to think about it or do much work.
Containers and other such things are more for when you need different things, like a dynamic site or backend async processing, or not a site at all, and especially when you need some/all of that and are tired of sysadmining a VM.