It's conceptually similar to EMR in the way it works. You connect your AWS account and we'll deploy a cluster there. HopsFS will run on top a S3 bucket in your organization. You get a fully featured Spark environment (With metrics and logging included - no need for cloudwatch). UI with Jupyter notebooks, the Hopsworks feature store and ML capabilities that EMR does not provide.
EMRFS has dozens of optimisations for Spark/Hadoop workloads e.g. S3 select, partitioning pruning, optimised committers etc and since EMR is a core product it is continually being improved. Using HopsFS would negate all of that.
There is a blog post [1] talking about this use case. Unfortunately, we have not publish a English version, you can read it using google translate .
[1] https://juicefs.com/blog/cn/posts/globalegrow-big-data-platf...
Disclaimer: Founder of JuiceFS here.