Skip to main content

Kubernetes ingress to services hosted on EKS

The ngrok Kubernetes Operator is our official open-source controller for adding public and secure ingress traffic to your k8s services. It works out of the box with n AWS EKS Kubernetes cluster to provide ingress to your services no matter the network configuration, as long as it has outbound access to the ngrok service. This allows ngrok to be portable and work seamlessly across any type of infrastructure.

What you'll need​

Ensure kubectl can speak with your cluster​

With an AWS EKS cluster, authentication for kubectl happens with a credential helper. So in-order to deploy the ngrok Kubernetes Operator to your cluster, you'll need to ensure that you can use the aws CLI and that the credential helper is available.

Recent versions of eksctl rely on the aws eks get-token command, which requires the aws CLI to be at-least version 1.16.156.

Let's ensure that you have the aws CLI installed and configured with your AWS credentials. You can confirm this works and you're authenticated correctly by running the following command:

Loading…

If this works, we can now request a kubeconfig:

Loading…

Install a sample application and Kubernetes ingress​

Create a manifest file (for example ngrok-manifest.yaml) with the following contents. You will need to replace the NGROK_DOMAIN on line 45 with your own custom value. This is the URL you will use to access your service from anywhere. If you're on a free account, it must be on a static subdomain which you can claim by logging into your account and following the instructions on the claim static subdomain banner. For paid accounts, you can use a custom domain or a subdomain of ngrok.app or ngrok.dev (for example, username-loves-ingress.ngrok.app or k8s.example.com).

Loading…

  1. Apply the manifest file to your k8s cluster.

    Loading…

    Note: If you get an error when applying the manifest, double check that you've updated the NGROK_DOMAIN value and try again.

  2. Access your ingress URL using the subdomain you chose in the manifest file above (i.e. https://my-awesome-k8s-cluster.ngrok.app) to confirm the 2048 app is accessible from the internet.

    application public

Add edge security to your app​

With our Traffic Policy system and the oauth action, ngrok manages OAuth protection entirely at the cloud edge. ngrok's edge authenticates and authorizes all requests before allowing ingress and access to your endpoint, meaning you don't need to add any additional services to your cluster, or alter any routes.

To enable the oauth action, you'll create a new NgrokTrafficPolicy custom resource and apply it to your entire Ingress with an annotation. You can also apply the policy to just a specific backend or as the default backend for an Ingress—see our doc on using the Operator with Ingresses.

  1. Edit your existing 2048.yaml manifest with the following, leaving the Service and Deployment as they were. Note the new annotations field and the NgrokTrafficPolicy CR.

    Loading…

  2. Re-apply your 2048.yaml configuration.

    Loading…

  3. When you open your demo app again, you'll be asked to log in via Google. That's a start, but what if you want to authenticate only yourself or colleagues?

  4. You can use expressions and CEL interpolation to filter out and reject OAuth logins that don't contain example.com. Update the NgrokTrafficPolicy portion of your manifest after changing example.com to your domain.

    Loading…

  5. Check out your deployed 2048 app once again. If you log in with an email that doesn't match your domain, ngrok rejects your request. Authentication... done!