Skip to content

VPC Endpoints shown as "CHECK FAILED" in a RAM-shared VPC/subnets context.. but actually unnecessary #72

@psantus

Description

@psantus

I'm facing the following result:

VPC Endpoints          | CHECK FAILED
     Amazon ECS Exec Checker doesn't support VPC endpoint validation for AWS RAM shared VPC/subnets.

I don't have VPC Endpoints and ECS Exec still works like a charm since I put my tasks in AWSVPC mode and my VPC has a NAT Gateway (and my subnet route table route 0.0.0.0/0 to this NAT Gateway).

Maybe additional checks can be performed and/or error message mention this alternative to VPC Endpoints?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions