ec2 create-vpc-endpoint
fails to create an AWS service interface endpoint when both the full service-name and service-region are specified
#9216
Labels
Describe the bug
When attempting to create a VPC endpoint of type Interface for an AWS service the operation fails when both service-name and service-region are specified, even if they are in alignment.
Regression Issue
Expected Behavior
When creating a VPC interface endpoint for an AWS service, if both service-name and service-region are included in the request and both reference the same region the request should not be blocked by the presence of service-region. Alternatively, if the intended behavior is to discourage the use of these options in combination then either the call should fail with a message that is more helpful than "An internal error has occurred" and ideally the documentation should be updated to mention the conflict between these two options.
Current Behavior
Example command with redacted resource IDs:
Result:
The full output from this command (with resource IDs & security tokens redacted) run in debug mode is included in the attached file, debug-logs.txt.
Reproduction Steps
The only prerequisites are access to an AWS account with a default VPC and IAM access to create the VPC endpoint. The error can be created with a minimal setup referencing the default VPC. Using eu-west-1 as an example region:
Possible Solution
No response
Additional Information/Context
No response
CLI version used
aws-cli/2.23.0 Python/3.12.8 Darwin/24.2.0 source/arm64
Environment details (OS name and version, etc.)
macOS 15.2
The text was updated successfully, but these errors were encountered: