Established design pattern for storing static files generated by a node app on Heroku?

I'm building a node app that has a tiny content management system in it for forms. I have the form builder and render working great. I want to have these forms go to static HTML pages, because I don't want to query the db on every page load (tell me if this is stupid). Obviously, on heroku if I were to generate a static file, it would only be on the one Dyno. I think I need a way to output the file to a CDN. Is this the established design pattern? Should I be looking into cacheing instead? I've looked briefly at AWS S3 but I came to the same conclusion I always do: overkill. Maybe I just need to dive in?

Thanks in advance for your advice.