Skip to main content

Splunk Lantern turns 5 on May 28th. Thank you for being one of our 750,000 annual users!
Click here to join our Slack channel to tell us what you love about the site or what content you'd like to see more of.
Lantern Home

 

Splunk Lantern

Monitoring Amazon Elastic Kubernetes Services (EKS) with Splunk Observability Cloud

  1. Last updated
  2. Save as PDF

 

This guide outlines the integration of Amazon Elastic Kubernetes Service (EKS) with Splunk Observability Cloud so you can observe EKS alongside the rest of your application telemetry data.

For additional context, refer to the following resources:

Splunk Observability Cloud provides a unified platform for monitoring and troubleshooting application infrastructure across multiple environments. You can collect and store Amazon CloudWatch metrics data, and if pieces of your applications and infrastructure live outside of AWS, you can view that data alongside your AWS data for a complete observability picture.

Data required

Amazon EKS

Process

To integrate AWS with Splunk Observability Cloud:

  1. In Splunk Observability Cloud, navigate to the Data Management section.
  2. Select AWS as the data source.

    integrate AWS.png

  3. Follow the integration wizard to prepare your AWS account.

    prepare AWS account.png

  4. Complete the wizard to import AWS data.

    renew inventory new.png

Install the Splunk Distribution of the OpenTelemetry Collector

Even with AWS integrated with Splunk Observability Cloud, you’ll notice from the Available Integrations page that you still need to deploy the OpenTelemetry Collector to get EKS data in.

fix missing colelctors.png

Follow these steps to install the Splunk Distribution of the OpenTelemetry Collector:

  1. In Splunk Observability Cloud, follow the integration wizard to install the Splunk Distribution of the OpenTelemetry Collector, specifying Amazon Web Services as the Provider and Amazon EKS (or Amazon EKS / Fargate profiles) as the Distribution.

    integrate k8s.png

  2. Connect to your EKS cluster and follow the rest of the installation instructions. This example uses the AWS CLI in the terminal, but with Helm installed, you could also use AWS CloudShell. Start by configuring kubectl for the EKS cluster by updating your kubeconfig file.

    clipboard_e5447447c8aec073e243355314861aeed.png

  3. Verify the connection.

    clipboard_e4166c5dbe2e10f46d6c4928a515523db.png

  4. Run the commands in the Splunk Observability Cloud installation instructions with splunk-otel-collector --version pinned to 0.111.0.

    clipboard_e9e1717e7a424dea964f9d8d61601a243.png

  5. View the EKS telemetry data from within Splunk Observability Cloud.

    clipboard_e683892db81fd2925b8dc2b915a665207.png

Validating the integration

Now that your EKS cluster is sending data to Splunk Observability Cloud, you can use all the same products and features within Splunk Observability Cloud to monitor your Amazon EKS environment.

From Infrastructure Monitoring, you can:

  • View your Amazon EKS navigators.

    clipboard_e5af011b0dffd5d4ef9f1c7af4c4f3fa4.png

  • Get insight into all of your Kubernetes clusters.

    clipboard_e55747e5f681b1d8b12a9ef4897cd9c57.png

  • View the health of a specific cluster.

    clipboard_edea8605242247b3f79a99c60898c5d21.png

  • Observe critical performance data around nodes, containers, daemonsets, deployments, namespaces, pods, replicasets, and workloads.

    clipboard_ef7488a04ce32e535c0e2430f1a33c7e5.png

From these critical usage metrics, you can create detectors and alerts from within your navigators, and they can live alongside the detectors and alerts for the rest of your applications and infrastructure.

clipboard_e08c3fed3b5147755497b40debc9be3dd.png

Next steps

With Amazon EKS now successfully integrated, you can use Splunk Observability Cloud to proactively monitor, detect, and alert on anomalies in your EKS environment, alongside the rest of your application and infrastructure telemetry data.

In addition, these resources might help you understand and implement this guidance: