- Newest
- Most votes
- Most comments
Hello.
It seems that you need to set up a VPC endpoint as explained in the answer at the URL below.
https://repost.aws/questions/QUcklm08auQjqdOQiOS9a7WA/lambda-access-to-the-mwaa-restful-api-on-a-private-vpc#ANHfQ2Eb4NSDCUmpyeRH3eTA
Please try setting up the VPC endpoint described in the following document to see if it improves the situation.
https://docs.aws.amazon.com/mwaa/latest/userguide/vpc-vpe-create-access.html#vpc-vpe-create-view-endpoints-attach-aa:~:text=Create%20endpoint.-,VPC%20endpoints%20required%20for%20Apache%20Airflow,-The%20following%20section
To resolve the MWAA invoke_rest_api issue in a private environment, first check whether your private subnets have NAT or outbound internet access that allows the MWAA worker nodes to reach the API endpoint. com.amazonaws.<region>.airflow.env.
If there is no internet access, the recommended approach is to use a VPC Interface Endpoint for MWAA. This allows the source MWAA private node to communicate with the destination MWAA managed endpoint securely through the AWS backbone network using PrivateLink, without requiring internet connectivity.
This ensures invoke_rest_api calls succeed while keeping the environment fully private.
Relevant content
- asked a year ago
