Amazon EKS Now Supports AWS PrivateLink for the Cluster OIDC Endpoint
IAM roles for service accounts (IRSA) can now reach the EKS cluster OIDC endpoint over AWS PrivateLink, so IRSA setup can complete entirely within a network-isolated VPC. This article also covers how it differs from customer-routed control plane egress and walks through the setup steps.
Introduction
On July 27, 2026, AWS announced AWS PrivateLink support for the Amazon EKS cluster OIDC endpoint. The key change is that the OIDC discovery endpoint and JWKS endpoint used by IAM roles for service accounts (IRSA) can now be reached privately from inside a VPC, without requiring internet egress.
If you run EKS in an environment with strict network isolation requirements, you may have run into trouble reaching the OIDC endpoint from inside your VPC while setting up IRSA. This update addresses that problem directly.
This article covers what changed, how it differs from the recently announced customer-routed control plane egress feature, which organizations will benefit most, and how to enable it. It's written for infrastructure and platform engineers who operate EKS, as well as anyone evaluating security or compliance requirements.
What Changed
Every EKS cluster publishes an OIDC discovery document and JWKS for IRSA. Until now, this endpoint was reachable only over the public internet.
Item | Before | After this update |
|---|---|---|
Access path to the OIDC endpoint | Internet only | Also reachable from inside the VPC via PrivateLink |
Setting up IRSA in a no-egress environment | Required internet egress | Fully self-contained, no internet egress required |
Behavior with private DNS enabled on the EKS-managed VPC endpoint | Name resolution could fail | Resolves correctly |
The Previous Challenge
In environments with strict network isolation requirements, creating the EKS VPC endpoint (
com.amazonaws.<region>.eks ) with private DNS enabled caused name resolution for the OIDC endpoint ( oidc.eks.<region>.amazonaws.com ) to fail. Under these conditions, running eksctl or Terraform from inside the VPC to set up IRSA resulted in an NXDOMAIN error, forcing teams to work around it by running the command from outside the VPC (for example, in AWS CloudShell) or by building a split-horizon DNS resolver.How PrivateLink Support for the OIDC Endpoint Solves This
By creating an interface VPC endpoint for the
com.amazonaws.<region>.oidc-eks service, access to the OIDC discovery document and JWKS now stays entirely within the VPC. Tools such as eksctl , Terraform, and custom token validators can complete IRSA setup and token validation without internet egress, and the name resolution issue that occurred when private DNS was enabled on the EKS-managed VPC endpoint is also resolved.This feature is available at no additional cost beyond standard AWS PrivateLink pricing. Regarding regional availability, the announcement states it's available in the AWS Regions where Amazon EKS is available, while the EKS user guide describes it as available "in most AWS Regions." Given this difference in wording, it's worth confirming availability in your target Region before you rely on it.
How This Differs from customer-routed control plane egress
The recently announced customer-routed control plane egress feature and this update are easy to confuse, since both involve "EKS," "OIDC," and "private" connectivity. In practice, though, they differ in both the direction of traffic and the problem they solve.
customer-routed control plane egress lets you route the EKS control plane's outbound traffic through your own VPC. This includes admission webhook callbacks and requests to an OIDC provider you operate internally. It's aimed at organizations with data perimeter or compliance requirements who need the control plane to reach a private OIDC provider or webhook server that's only accessible from inside a VPC, enabled by setting
controlPlaneEgressMode to CUSTOMER_ROUTED .This update, by contrast, targets the OIDC discovery endpoint and JWKS that the EKS cluster itself publishes. This is what IRSA uses to validate the signature on IAM roles bound to Pods, and the traffic here is inbound: tools inside the VPC, such as
eksctl , Terraform, or custom token validators, are the ones reaching out to this endpoint. | customer-routed control plane egress | PrivateLink support for the OIDC endpoint |
|---|---|---|
OIDC involved | An external OIDC provider you operate (used for cluster authentication) | The OIDC endpoint published by the EKS cluster (used for IRSA) |
Direction of traffic | Outbound from the control plane | Inbound from tools inside the VPC |
Problem it solves | An internal OIDC provider or webhook server that's confined to a VPC and unreachable from the control plane | An OIDC endpoint that was previously reachable only over the internet, unreachable from tools inside a VPC |
These are independent features, and enabling one doesn't solve the problem the other addresses. Even if you've already adopted customer-routed control plane egress, this update is worth considering separately if you're still struggling to reach the OIDC endpoint from inside your VPC while setting up IRSA.
Which Organizations Need This Feature
This isn't a must-have update for every EKS user. It benefits organizations that restrict, or fully block, internet egress from their VPCs.
A typical case is financial services, healthcare, or public sector systems with security policies that tightly restrict outbound internet traffic from their VPCs. Previously, teams in this position who wanted to use IRSA had to either open up internet egress through a NAT gateway or give up on IRSA altogether. Being able to set up IRSA with no internet egress opened at all is the value this update brings to these organizations.
It's also directly useful for organizations already running the EKS-managed VPC endpoint with private DNS enabled who have run into the name resolution issue described above. They no longer need to keep relying on workarounds like running commands from CloudShell or maintaining a split-horizon DNS resolver.
It's also relevant to teams automating IRSA setup with
eksctl or Terraform from CI/CD runners or Terraform execution environments running inside a VPC. Since OIDC provider creation and token validation can now complete without internet egress, it becomes easier to build an IaC pipeline that's fully self-contained within a closed network.On the other hand, if your VPC already has normal internet egress permitted, you're likely operating fine with the public OIDC endpoint as-is. For those environments, this update isn't essential — it simply adds another option.
Activation Steps
Enabling this is straightforward: you only need to create one interface VPC endpoint for the OIDC endpoint in your target VPC.
Creating the Interface VPC Endpoint
Use the service name
com.amazonaws.<region-code>.oidc-eks . With the AWS CLI, you can create it as follows:aws ec2 create-vpc-endpoint \ --vpc-id <vpc-id> \ --service-name com.amazonaws.<region-code>.oidc-eks \ --vpc-endpoint-type Interface \ --subnet-ids <subnet-id-1> <subnet-id-2> \ --security-group-ids <security-group-id> \ --private-dns-enabled
We recommend specifying subnets across multiple Availability Zones for availability. Private DNS is enabled by default for EKS interface endpoints, but specifying it explicitly, as shown above, makes the intent clearer. As long as
enableDnsHostnames and enableDnsSupport are enabled on the VPC, oidc.eks.<region-code>.amazonaws.com will resolve to this endpoint with no further configuration. For IPv6 clusters, the dual-stack hostname oidc-eks.<region-code>.api.aws is used instead (in the AWS China Regions, this is oidc-eks.<region-code>.api.amazonwebservices.com.cn ).A Note on Access Control
There's one important caveat here. Unlike the interface endpoint for the EKS API, the interface endpoint for this OIDC endpoint does not support VPC endpoint policies. Under the OpenID Connect specification, the OIDC discovery document and JWKS are served as anonymous requests with no credentials attached, so there's no IAM principal or action for an endpoint policy to evaluate. This endpoint only accepts the default full-access policy.
To restrict access, use security groups on the endpoint's network interfaces and subnet routing instead of an endpoint policy. For example, a basic setup would limit inbound traffic on port 443 to your VPC's CIDR range:
aws ec2 authorize-security-group-ingress \ --group-id <security-group-id> \ --protocol tcp \ --port 443 \ --cidr <vpc-cidr>
Verifying the Setup
After creating the endpoint, confirm that name resolution works from an instance inside the VPC.
nslookup oidc.eks.<region-code>.amazonaws.com
If this resolves correctly from inside a VPC with no internet egress, the endpoint is working. It's also worth running a command like the following from inside the VPC to confirm that IAM OIDC provider creation completes without the name resolution error you may have seen before.
eksctl utils associate-iam-oidc-provider --cluster <cluster-name> --approve
A Note on This Procedure
This endpoint only handles delivering the OIDC discovery document and JWKS privately within the VPC. When a workload calls
sts:AssumeRoleWithWebIdentity to obtain temporary IAM role credentials, that call is handled internally by AWS STS and doesn't go through this OIDC endpoint. If you also want to keep the workload's call to STS private, you'll need to separately create an interface endpoint for AWS STS and configure the workload to use the regional STS endpoint.
Use Cases
Setting Up IRSA in No-Egress Environments
If you run EKS in a VPC with no internet egress permitted at all, you may previously have had to give up on setting up IRSA entirely. With a single interface endpoint for the OIDC endpoint in your VPC, you can now create an IAM OIDC provider using
eksctl , Terraform, or the AWS CLI, and any custom token validators running inside the VPC can fetch the JWKS directly. A practical benefit is that you no longer need a NAT gateway or similar route just for this purpose.Resolving DNS Conflicts with the EKS-Managed VPC Endpoint
If you're running the EKS-managed VPC endpoint with private DNS enabled and have been affected by the name resolution conflict described earlier, creating a dedicated interface endpoint for the OIDC endpoint resolves it. You no longer need to keep relying on workarounds like manual execution from CloudShell or a split-horizon DNS resolver.
Automating IRSA in VPC-Contained IaC Pipelines
This is also useful for pipelines that automate IRSA setup with Terraform or
eksctl from CI/CD runners running inside a VPC. Even for teams that don't want to permit internet egress from their pipeline execution environment at all, switching OIDC endpoint access to a VPC-local interface endpoint makes it easier to build IAM OIDC provider creation into the pipeline.
Summary
You can now reach the EKS cluster's OIDC discovery endpoint and JWKS directly from inside a VPC over AWS PrivateLink. IRSA setup, which previously required internet egress, now works entirely within a network-isolated environment.
This is a distinct update from the recently announced customer-routed control plane egress feature — the OIDC involved and the problem solved are both different. If you operate EKS in an environment with network isolation requirements, this is a good moment to check whether this update applies to your setup.
References
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article