Hi,
@kk. If you don't mind using Postgres or another database backend for this, that would be the default and smoothest experience as of now. Some users have developed processes where they export state to S3 after the execution so they can spin down or delete their systemdb, and then load it back from S3 before the next execution.
There's also a feature request
here to add support for S3 backends (currently accepting pull requests).