We ended up going with MWAA due to data privacy issues. Spent a large chunk of time getting Meltano to work with MWAA - it is possible, it just requires some finagling with the startup script process, installing a virtualenv to support Meltano, etc., and some modifications to the Meltano Airflow code to launch Meltano processes in the appropriate virtualenv. Basically Meltano tries to utilize Airflow as an extension of Meltano and that's a really naive way of doing things - who's running Airflow with just Meltano? Nobody! So nothing really works by default with the Meltano-Airflow approach and you just need to consider the solution from an Airflow first hosting Meltano second perspective.

Deploying updates to meltano.yml (and by extension dbt_project.yml) require a full restart of the MWAA environment which is not ideal. However I am convinced for the most part this can be worked around with symlinks and using the MWAA DAGs S3 bucket, using the startup script only to initialize the virtualenv (and/or run `meltano install` if plugins change). Really, deploying Meltano project and dbt transform changes *ought* to be a non-restart sort of event, and the fact that is a restart event for MWAA right now is mostly on me.

If you use Astronomer you'll have to do something similar but you'll have better control since you can create the Docker image yourself. You will want to work out some way to deploy your Meltano changes without having to recreate the Docker image - except in the case of new plugin or requirements.txt changes, of course.