issue #582 does not solve the problem with multiple VPC endpoints matched on Terraform 0.12 and aws provider 2.70

[dgonzalez]

In the issue it is recommended for people who cannot update the aws provider to version 3.10 to use the release 2.69.0 of terraform-aws-vpc.

I am in such situation (upgrading the provider is not trivial, we are working on it but will take us days if not a couple of weeks) and when I try to plan with the 2.69.0 I get the following error:

Error: "service_type": this field cannot be set

  on .terraform/modules/this.vpc/vpc-endpoints.tf line 4, in data "aws_vpc_endpoint_service" "s3":
   4: data "aws_vpc_endpoint_service" "s3" {



Error: "service_type": this field cannot be set

  on .terraform/modules/this.vpc/vpc-endpoints.tf line 45, in data "aws_vpc_endpoint_service" "dynamodb":
  45: data "aws_vpc_endpoint_service" "dynamodb" {

This is using the AWS provider 2.70.0. Am I wrong or it is not possible to use this module with a provider below 3.10 after AWS released the S3 PrivateLink interface?

[circa10a]

@dgonzalez I have the same problem, here's what I did to get around it until we can upgrade the provider. We forked the module and made the changes/took steps documented here: hashicorp/terraform-provider-aws#17417

[tbugfinder]

Hi @circa10a ,

#582 refers to 2.69.0 for older provider versions and 2.70 for newer provider versions.
Unfortunately 2.69.0 indeed is incompatible with AWS Provider v2.70.

I'm asking for a 2.69.1 bugfix.

[bryantbiggs]

hi all, could you try out the changes proposed here #597 to see if this resolves the issues you are currently facing please?

[tbugfinder]

Hi @bryantbiggs ,
your PR still requires provider v3.10.
We are looking for a fix with provider v2.70.0 compatibility.

https://github.com/bryantbiggs/terraform-aws-vpc/blob/fix/s3-interface-endpoint/versions.tf#L7

[bryantbiggs]

ah, you are right @tbugfinder - I forgot that change. I've just pushed that change up after testing/validating

[github-actions]

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.