VPC Endpoint charges with zero endpoints on dashboard

Question

I used VPC Endpoints generated by connecting MySQL databases to an Amplify app with the `data/resource.ts`. When I started noticing the generated Endpoints were generating additional charges, I deleted any reference of MySQL databases on the `resource.ts` file, and deploying it deleted the 8 Endpoints CloudFormation was generating on each deploy. But now that I have 0 Endpoints on the dashboard, the billing for VPC endpoints is growing out. I kept using MySQL databases on the Amplify app, but instead of managing them with the `resource.ts` file that was generating the Endpoints, I switch to Prisma and just used a connection string, skipping the Endopints on CloudFormation.

Deeksha · Accepted Answer

1. Even though you deleted the VPC endpoints visible in the dashboard, other AWS services (like Lambda functions, ECS tasks, etc.) might still be using VPC endpoints that are not directly managed by CloudFormation.
Action: Go through your AWS resources, particularly in the same VPC, and check if any other services are configured to use VPC endpoints. You can also check your AWS billing dashboard to see which specific services are incurring VPC endpoint charges.

2. Sometimes, resources might not get fully deleted even when CloudFormation stacks are deleted, especially if there were dependencies or errors during deletion.
Action: Manually review all VPCs and subnets in your account to ensure no VPC endpoints are lingering. Use the AWS CLI or SDK to list all VPC endpoints programmatically and confirm there are no active ones:

```
aws ec2 describe-vpc-endpoints --query 'VpcEndpoints[*].VpcEndpointId'

```

I hope this information is helpful. If it is, please consider accepting the answer so that others can benefit from the clarity when searching for similar questions in the community. Thank you!

VPC Endpoint charges with zero endpoints on dashboard

Add your answer

Relevant content