You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
Function check_service_vpc_endpoints returns wrong information, mentioning that not all vpc endpoints are associated with the corresponding subnets used in the environment creation of mwaa.
Context:
I created VPC endpoints of the following services: s3, ecr, kms, sqs, monitoring, airflow.api, airflow.env, airflow.ops
These VPC endpoints are associated to the same VPC and subnets as the mwaa environment
Moreover, this endpoints are supported to a 3rd subnet that is not associated with the mwaa environment (as 2 subnets only are right now supported)
it's checking whether all the subnets associated with the endpoints are present in the subnets of the MWAA environment, but it should be the other way around.
The text was updated successfully, but these errors were encountered:
Function check_service_vpc_endpoints returns wrong information, mentioning that not all vpc endpoints are associated with the corresponding subnets used in the environment creation of mwaa.
Context:
Promt
What is expected:
Possible bug:
I think this line can be the problem:
aws-support-tools/MWAA/verify_env/verify_env.py
Line 658 in a143ec9
it's checking whether all the subnets associated with the endpoints are present in the subnets of the MWAA environment, but it should be the other way around.
The text was updated successfully, but these errors were encountered: