Skip to content
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

Investigate VPC Endpoints #1426

Open
2 tasks
dj-maisy opened this issue Aug 13, 2024 · 0 comments
Open
2 tasks

Investigate VPC Endpoints #1426

dj-maisy opened this issue Aug 13, 2024 · 0 comments
Labels
enhancement New feature or request security Security-related issue or enhancement (DO NOT USE PUBLIC ISSUES FOR VULN REPORTS obvs!)

Comments

@dj-maisy
Copy link
Member

dj-maisy commented Aug 13, 2024

What?

We should explore whether we should be making more use of VPC Endpoints.

Tasks

Preview Give feedback

Why?

There are two good reasons to do this:

  • The majority of our traffic is currently routed through our NAT Gateways. This is expensive. A lot of our traffic consists of accessing resources and services provided by AWS. If we can route that traffic to use VPC Endpoints, you can avoid paying the premium price for traffic to be processed by the NAT Gateways (by a factor of about 4.8:1)
  • Traffic that passes through AWS PrivateLink rather than out of a Nat Gateway (and theoretically via the internet) is inherently more secure, as there is no opportunity for that traffic to leave the AWS ecosystem.

Considerations

We need to consider (or check) whether we need to do the following things:

  • Create or select an existing SG to enable the EKS Nodes to access the VPC Endpoints for the relevant services
  • Make sure that route tables are correctly configured to allow the EKS Nodes to access the relevant AWS services via the VPC Endpoints
@dj-maisy dj-maisy added enhancement New feature or request security Security-related issue or enhancement (DO NOT USE PUBLIC ISSUES FOR VULN REPORTS obvs!) labels Dec 13, 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 security Security-related issue or enhancement (DO NOT USE PUBLIC ISSUES FOR VULN REPORTS obvs!)
Projects
None yet
Development

No branches or pull requests

1 participant