-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: Add new pattern for EKS cross account communication using VPC lattice #1953
Conversation
Signed-off-by: Sébastien Allamand <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
spec: | ||
containers: | ||
- name: {{ .Release.Name }}-{{ .Values.version }} | ||
image: public.ecr.aws/seb-demo/http-server:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use some public image like this instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure, the code to build the container is public : https://github.com/aws-samples/amazon-eks-security-immersion-day/blob/mainline/docker/http-server/launch_app.sh and I use a script to configure the CA at runtime
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put the link to the Dockerfile used
patterns/vpc-lattice/cross-cluster-pod-communication/cluster/eks.tf
Outdated
Show resolved
Hide resolved
patterns/vpc-lattice/cross-cluster-pod-communication/cluster/eks.tf
Outdated
Show resolved
Hide resolved
patterns/vpc-lattice/cross-cluster-pod-communication/cluster/eks.tf
Outdated
Show resolved
Hide resolved
patterns/vpc-lattice/cross-cluster-pod-communication/cluster/eks.tf
Outdated
Show resolved
Hide resolved
patterns/vpc-lattice/cross-cluster-pod-communication/cluster/logs.txt
Outdated
Show resolved
Hide resolved
Co-authored-by: Apoorva Kulkarni <[email protected]>
Co-authored-by: Apoorva Kulkarni <[email protected]>
Co-authored-by: Apoorva Kulkarni <[email protected]>
Co-authored-by: Apoorva Kulkarni <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
Co-authored-by: Apoorva Kulkarni <[email protected]>
…harts/demo/values.yaml Co-authored-by: Apoorva Kulkarni <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
Signed-off-by: Sébastien Allamand <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
This PR introduce a new pattern that show case how to leverage VPC lattice for cross-cluster communication, in a secure manner relying on AWS Private CA and AWS Certificate Manager on a private Route 53 hosted zone.
The pattern demonstrate how to leverage EKS Pod Identity Session tags to do service level authorization with ABAC verifications.
Motivation and Context
How was this change tested?
pre-commit run -a
with this PRAdditional Notes