Amazon Elastic Compute Cloud (EC2) is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale cloud computing easier for developers. A VPC (Virtual Private Cloud) endpoint allows you to privately connect your VPC to supported AWS services and VPC endpoint services powered by AWS PrivateLink without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection.
When working with VPC endpoint services, you might encounter the error InvalidVpcEndpointServiceID.NotFound. This error typically appears when you attempt to create or manage a VPC endpoint and the specified service ID is not found.
The error message usually looks like this:
InvalidVpcEndpointServiceID.NotFound: The specified VPC endpoint service ID does not exist.
The InvalidVpcEndpointServiceID.NotFound error indicates that the VPC endpoint service ID you provided does not match any existing service. This could be due to a typo, an incorrect ID, or the service being deleted or not yet created.
To resolve the InvalidVpcEndpointServiceID.NotFound error, follow these steps:
Ensure that the service ID you are using is correct. You can list your VPC endpoint services using the AWS CLI:
aws ec2 describe-vpc-endpoint-services
Check the output to confirm the service ID is correct.
If the service ID was previously valid, verify whether the service has been deleted. You can check the AWS Management Console or use the AWS CLI to list existing services.
Sometimes, there might be a delay in the availability of newly created services. Wait for a few minutes and try again.
If you find that the service ID was incorrect, update your configuration or script with the correct ID.
For more information, you can refer to the following resources:
Let Dr. Droid create custom investigation plans for your infrastructure.
Book Demo
