The Airflow docs actually state that setting the encryption key to an empty string makes Connections fall back to plaintext.
But does the same thing hold true on AWS-managed MWAA?
This post traces that question from Airflow’s native Fernet mechanism all the way to MWAA’s reserved environment variables.

When tasks depend on each other yet remain independent events, what is the most elegant way to handle them?
Should we use a loop? Add another DAG? Or is there a better solution?

When building dependencies between DAGs, you don’t always have to rely on RESTful APIs.
Airflow also provides a built-in Operator for this purpose.