S3 endpoint creation broken due to S3 endpoint Interface type availability

[aglarendil]

Hi there

According to
https://aws.amazon.com/blogs/aws/aws-privatelink-for-amazon-s3-now-available/

there are now 2 types of S3 VPC Endpoints available, which breaks VPC module in case enable_s3_endpoint variable is set.

The workaround is to disable S3 endpoint management and add it via plain TF resource.

the error message is:

Error: multiple VPC Endpoint Services matched; use additional constraints to reduce matches to a single VPC Endpoint Service

here is how it looks like:

{
    "ServiceNames": [
        "com.amazonaws.eu-central-1.s3",
        "com.amazonaws.eu-central-1.s3"
    ],
    "ServiceDetails": [
        {
            "ServiceId": "....",
            "Owner": "amazon",
            "BaseEndpointDnsNames": [
                "s3.eu-central-1.amazonaws.com"
            ],
            "Tags": [],
            "AcceptanceRequired": false,
            "ManagesVpcEndpoints": false,
            "ServiceType": [
                {
                    "ServiceType": "Gateway"
                }
            ],
            "AvailabilityZones": [
                "eu-central-1a",
                "eu-central-1b",
                "eu-central-1c"
            ],
            "ServiceName": "com.amazonaws.eu-central-1.s3",
            "VpcEndpointPolicySupported": true
        },
        {
            "ServiceId": "...",
            "Owner": "amazon",
            "BaseEndpointDnsNames": [
                "s3.eu-central-1.vpce.amazonaws.com"
            ],
            "Tags": [],
            "AcceptanceRequired": false,
            "ManagesVpcEndpoints": false,
            "ServiceType": [
                {
                    "ServiceType": "Interface"
                }
            ],
            "AvailabilityZones": [
                "eu-central-1a",
                "eu-central-1b",
                "eu-central-1c"
            ],
            "ServiceName": "com.amazonaws.eu-central-1.s3",
            "VpcEndpointPolicySupported": true
        }
    ]
}

[antonbabenko]

#573 covers it all. Please upgrade the module to v2.70.0.

[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.