Skip to content

Architecture: evaluate VPC endpoints and network topology impacts #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
giusedroid opened this issue Jun 15, 2024 · 0 comments
Open
Labels
enhancement New feature or request helpmebuild

Comments

@giusedroid
Copy link
Contributor

We want to evaluate what's the (performance gain+cost saving) vs (cold-start performance impact+operational overhead) of introducing the usage of VPC endpoints (S3, Bedrock). It could potentially suck because customers would end up dealing with VPCs, NAT GW, ENIs for Lambda, subnets, but cost and performance should improve. We need to evaluate changes to the overall network topology and check if a NAT gateway is needed. A NAT gateway is a showstopper for me, because it's introducing static charges and defeats the purpose of a fully serverless architecture.

@giusedroid giusedroid added the enhancement New feature or request label Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request helpmebuild
Projects
None yet
Development

No branches or pull requests

1 participant