MWAA terraform script failed with 403 error, but MWAA stuck with "Creating" state since last 2 hours

Here are a few options you can try to delete the stuck MWAA environment that is stuck in 'Creating' state:

In the AWS Management Console, navigate to the MWAA environments page, select the environment and click 'Delete'. This should force a deletion.
Use the AWS CLI/SDK to call the 'DeleteEnvironment' API and pass the '--force' option. For example:

aws mwaa delete-environment --name my-env --force

Verify that you don't have any VPC lockdown or restrictive IAM policies on your account that could be blocking MWAA from creating resources. Relax policies if needed.
Check the service limits page in AWS to see if you are hitting any AWS account limits related to VPCs, subnets or other resources MWAA requires. Request limit increases if needed.
Try manually deleting VPCs, subnets or other resources that MWAA may have partially created before getting stuck.
As a last resort, open a support ticket with AWS to have them fully clean up the failed environment resources.

The key is to first try forcing a delete via CLI/API calls with the '--force' flag. If that doesn't work, look for restrictive policies, service limits or partially created resources that could be manually cleaned up. Let me know if the environment persists and I can provide further troubleshooting suggestions.