Feature Request: VPC Endpoint route table association resource

[coen-hyde]

Feature

A vpc endpoint route table association resource

Why

So all route tables do not have to exist at the time the endpoint is created.

My Use Case:

I use Terraform's remote state to logically group infrastructure. Having a this resource would allow me to create the endpoint in one deployment but associate route tables in another.

[kwilczynski]

@coen-hyde hi there! Thank you for this! It is not a bad idea at all, actually.

I will have a look into it.

[supergibbs]

I'd love this too but I assumed it didn't exist since the AWS CLI doesn't seem to support it:

http://docs.aws.amazon.com/cli/latest/reference/ec2/create-route.html

[supergibbs]

Actually could be done with http://docs.aws.amazon.com/cli/latest/reference/ec2/modify-vpc-endpoint.html

[kwilczynski]

@coen-hyde @supergibbs hi there! Yes, modifying the VPC endpoint is the key here, especially since the route_table_ids are already optional. A clear low hanging fruit. 👍

[kwilczynski]

@coen-hyde @supergibbs hi! Apologies for the delay. I have began work in #9244.

[coen-hyde]

@kwilczynski awsome! Hardly a delay. I wasn't expecting this to be worked on so soon

[stack72]

Closed via #10137

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.