MWAA environment still searching for a startup script after the update

This problem was solved with adding a dummy startup script and rerunning the MWAA update.

When you update your Amazon MWAA environment and remove the startup script, the environment may continue to search for it if the startup script configuration hasn't been properly cleared from the environment settings.

To resolve this issue, you should explicitly remove the startup script reference from your environment configuration during the update. When updating your environment, ensure that you're not just removing the file from S3, but also updating the environment configuration to remove the startup script path parameter entirely.

If your environment update fails and goes into an UPDATE_FAILED state, Amazon MWAA will roll back to the previous stable version of the environment, which may still include the startup script configuration. This could explain why the environment continues to search for the script.

I recommend the following steps:

1. Test your configuration changes locally to ensure they work as expected
2. Run a troubleshooting script to verify your Amazon VPC network setup and configuration
3. When updating the environment, explicitly set the startup script parameter to null or remove it from the update command to ensure the reference is completely removed

Make sure you're updating the environment configuration through the proper channels (AWS Management Console, AWS CLI, or API) to ensure the startup script reference is fully removed from the environment settings.
Sources
Troubleshooting: Creating and updating an Amazon MWAA environment - Amazon Managed Workflows for Apache Airflow
Using a startup script with Amazon MWAA - Amazon Managed Workflows for Apache Airflow