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
If the Subnets used are all private and without a NAT, then this Lambda won't run and return error below
[ERROR] EndpointConnectionError: Could not connect to the endpoint URL: "https://elasticloadbalancing.us-east-1.amazonaws.com/"
The best way to solve this issue is to create a Interface VPC Endpoint for elasticloadbalancing.us-east-1.amazonaws.com with Private DNS names enabled and then allow traffic Lambda Security Group in the VPCE SG.
The text was updated successfully, but these errors were encountered:
amazon-rds-crossaccount-access/CrossAccountRDSAccess.yml
Line 144 in 9eca428
If the Subnets used are all private and without a NAT, then this Lambda won't run and return error below
The best way to solve this issue is to create a Interface VPC Endpoint for
elasticloadbalancing.us-east-1.amazonaws.com
withPrivate DNS names enabled
and then allow traffic Lambda Security Group in the VPCE SG.The text was updated successfully, but these errors were encountered: