Linkedin

  • Home >
  • Access container applications privately on Amazon EKS using AWS PrivateLink and a Network Load Balancer

Access container applications privately on Amazon EKS using AWS PrivateLink and a Network Load Balancer

Project Overview

Project Detail

This pattern describes how to privately host a Docker container application on Amazon Elastic Kubernetes Service (Amazon EKS) behind a Network Load Balancer, and access the application by using AWS PrivateLink. You can then use a private network to securely access services on the Amazon Web Services (AWS) Cloud. 

The Amazon EKS cluster running the Docker applications, with a Network Load Balancer at the front end, can be associated with a virtual private cloud (VPC) endpoint for access through AWS PrivateLink. This VPC endpoint service can then be shared with other VPCs by using their VPC endpoints.

The setup described by this pattern is a secure way to share application access among VPCs and AWS accounts. It requires no special connectivity or routing configurations, because the connection between the consumer and provider accounts is on the global AWS backbone and doesn’t traverse the public internet.

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/access-container-applications-privately-on-amazon-eks-using-aws-privatelink-and-a-network-load-balancer.html?did=pg_card&trk=pg_card

To know more about this project connect with us

Access container applications privately on Amazon EKS using AWS PrivateLink and a Network Load Balancer