aws / aws/containers-roadmap

[EKS] [request]: Enable code pipeline support for private endpoints

Open
#574 2 comments 0 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

**Tell us about your request**
Use Codepipeline to create EKS with private endpoint and also to deploy apps to EKS with private endpoint

**Which service(s) is this request for?**
EKS, Codepipeline

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When we enable "private endpoint access" in EKS cluser, then this cluster can only be accessed from the VPC it is tagged to. AWS recommends to use bastion host for this. But this defeats automation and lot of workaround is required to deploy apps to EKS using bastion host.

Codepipeline gives required automation to create and deploy apps to EKS with public endpoint. However, when we have only private endpoint, Codepipeline is not able to connect to EKS cluster.

I feel if we have Codepipeline access the EKS cluster with private endpoint, then we can have a clean approach to create EKS and deploy apps to EKS.

**Are you currently working around this issue?**
Yes. By having a Bastion host within VPC.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the issue's description of AWS CodePipeline access to EKS clusters with private endpoint access, including the current bastion-host workaround. Clarify the required CodePipeline-to-EKS workflow and what supported behavior would count as done; the payload names no repository files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.