aws_vpc_endpoint type mismatch for ec2 service_name

[georgesvachulay]

Terraform Version

Terraform v0.11.1
+ provider.aws v1.5.0
+ provider.template v1.0.0

Terraform Configuration Files

# AWS service endpoint (to use CLI internally) for EC2
resource "aws_vpc_endpoint" "internal-ec2" {
  vpc_id          = "${aws_vpc.ps-eu.id}"
  service_name    = "com.amazonaws.eu-west-2.ec2"
  route_table_ids = ["${aws_vpc.ps-eu.main_route_table_id}"]
}

Debug Output

Crash Output

Error: Error applying plan:

1 error(s) occurred:

* aws_vpc_endpoint.internal-ec2: 1 error(s) occurred:

* aws_vpc_endpoint.internal-ec2: Error creating VPC Endpoint: InvalidParameter: Endpoint type (Gateway) does not match service type (Interface).
        status code: 400, request id: adca118c-c4bd-4814-92fc-c0bc3c2af51e

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Expected Behavior

successful run

Actual Behavior

type mismatch

Steps to Reproduce

Important Factoids

S3 and DynamoDB endpoints are Gateway types, but ec2, servicecatalog, ssm, etc. types are Interface types. It's likely that the class expects all input to be a gateway, however that's not the case anymore (instead of a gateway it should be creating an interface for the ec2 service_name)

References

hashicorp/terraform#16941

[ewbankkit]

This is addressed in #2515.

[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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!