You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add proxy servers for both inbound and outbound traffic, providing more control over the network traffic.
For inbound traffic add a Envoy proxy server on top of the ingress, that is exposed by the cluster.
For outbound traffic add a Squid proxy server and deny any and all outbound traffic directly accessibly from EKS.
Changes
For ingress, come-up with an approach to fetch the ingress URL exposed by EKS
For egress, come-up with a way, to insert the proxy url in EKS
Creating user data for deploying the changes
Add their respective configuration in S3 buckets and fetch them while constructing images
Add this in a ASG, and include a LG on top of it
The text was updated successfully, but these errors were encountered:
Description
Add proxy servers for both inbound and outbound traffic, providing more control over the network traffic.
For inbound traffic add a
Envoy
proxy server on top of the ingress, that is exposed by the cluster.For outbound traffic add a
Squid
proxy server and deny any and all outbound traffic directly accessibly from EKS.Changes
The text was updated successfully, but these errors were encountered: