fix: remove unnecessary VPC endpoints for RDS connections#3449
Open
fix: remove unnecessary VPC endpoints for RDS connections#3449
Conversation
Only the SSM VPC endpoint is needed for Lambda to access Parameter Store. The other 4 endpoints (ssmmessages, ec2, ec2messages, kms) are never used by the code but cost customers ~$350/year per AZ. Fixes #3409
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Only the SSM VPC endpoint is needed for Lambda to retrieve database credentials from Parameter Store. The other 4 endpoints (ssmmessages, ec2, ec2messages, kms) are created but never referenced in the code, costing customers ~$350/year per AZ.
Changes
ssmendpoint is retained (the only one actually used by the Lambda function)Technical Details
The code at resolver.ts only extracts the SSM DNS entry:
The other 4 services (ssmmessages, ec2messages, ec2, kms) are for SSM Agent on EC2, not for Parameter Store access from Lambda.
Cost Impact
Testing
Fixes #3409
Related: T.corp P371007397