Skip to main content

AWS Quickstart Guide

This quickstart guide will help you get Causely up and running on AWS. This setup deploys Causely in your Kubernetes cluster (including EKS) with eBPF instrumentation enabled, and connects it to your AWS account to monitor cloud resources.

1

Get Your Installation Command​

  1. Log in to the Causely portal.
  2. Visit the mediators page.
  3. Click the "Add new" button (or "Add ➕" button) on the mediators page.
  4. In the instructions panel, you'll see the Helm installation command with your access token pre-filled.
  5. Copy the complete Helm command. It will look similar to the example below.
Example Command

The command you copy will include your specific access token and cluster name. Here's what it typically looks like:

export CAUSELY_TOKEN=<your_token>
export CAUSELY_CLUSTER_NAME=<your_cluster_name>
export CAUSELY_VERSION=<version>
helm upgrade --install causely \\
  --create-namespace oci://us-docker.pkg.dev/public-causely/public/causely \\
  --version "${CAUSELY_VERSION}" \\
  --namespace=causely \\
  --set image.tag="${CAUSELY_VERSION}" \\
  --set global.cluster_name="\${CAUSELY_CLUSTER_NAME}" \\
  --set mediator.gateway.token="\${CAUSELY_TOKEN}"
Screenshot Placeholder

Screenshots of the mediators page, "Add new" button, and instructions panel will be added here.

4

Run the Installation Command​

  1. Open a terminal with kubectl configured to access your Kubernetes cluster.
  2. Paste and run the Helm command you copied from the portal.
  3. Wait for the installation to complete:
kubectl wait --for=condition=Ready pod -l app.kubernetes.io/part-of=causely -n causely --timeout=300s
info

By default, Causely will use eBPF-based instrumentation to automatically instrument your applications running in Kubernetes. This provides zero-effort observability without code changes.

5

Connect Your AWS Account​

Now you need to configure Causely to monitor your AWS resources. Causely supports two authentication methods: IAM Role (recommended for EKS) or Access Keys.

If you're running on Amazon EKS, we recommend using IAM roles for service accounts (IRSA) or EKS Pod Identity for secure authentication.

  1. Create an IAM role with the necessary permissions. See the AWS integration documentation for the required IAM policy and trust relationship.

  2. Annotate the mediator service account to use the IAM role:

kubectl annotate serviceaccount causely-mediator \
  -n causely \
  eks.amazonaws.com/role-arn=arn:aws:iam::ACCOUNT_ID:role/CAUSELY_ROLE_NAME

Option 2: Access Keys​

  1. Create a Kubernetes secret with your AWS access key credentials:
kubectl create secret generic \
  --namespace causely aws-credentials \
  --from-literal=access-key-id="<your_access_key_id>" \
  --from-literal=secret-access-key="<your_secret_access_key>"
  1. Update your Causely configuration by creating or updating causely-values.yaml:
global:
  cluster_name: <your_cluster_name>
mediator:
  gateway:
    token: <your_token>
scrapers:
  aws:
    enabled: true
    accounts:
      - secretName: aws-credentials
        # namespace: causely  # optional; defaults to the pod namespace
  1. Upgrade your installation:
helm upgrade --install causely \\
  --namespace=causely \\
  --values causely-values.yaml \\
  oci://us-docker.pkg.dev/public-causely/public/causely \\
  --version "${CAUSELY_VERSION}"
Alternative: Credentials Autodiscovery

You can also use credentials autodiscovery by labeling the secret:

kubectl --namespace causely label secret aws-credentials "causely.ai/scraper=AWS"

This allows you to add new accounts without editing the configuration. See the AWS integration documentation for more details.

For complete setup instructions, including IAM role configuration and supported AWS services, see the AWS integration documentation.

6

What to Expect​

Once configured, Causely will:

  • Monitor Kubernetes services: Using eBPF instrumentation, Causely automatically discovers and monitors services running in your Kubernetes cluster.

  • Monitor AWS resources: Causely will discover and monitor AWS services including:

    • Application Load Balancer (ALB) and Network Load Balancer (NLB)
    • Amazon ECS, EC2, EBS
    • Amazon RDS, ElastiCache, MSK
    • AWS Lambda
    • And more

  • Unified view: Causely creates a unified topology showing relationships between your Kubernetes services and AWS resources.

  • Show data in the UI: Within a few minutes, you should start seeing entities appearing in the Causely UI at https://portal.causely.app.

7

Add More Telemetry Sources​

To help Causely identify root causes more effectively, connect additional telemetry sources. Visit the Telemetry Sources page to learn about the data sources that Causely supports, including:

8

Add Workflow Integrations​

Push insights into your existing workflows and notification tools. Visit the Workflow Integrations page to set up integrations with:

9

What's Your Goal?​

What's your goal?

Choose a goal to explore how Causely can help you achieve it.

Accelerate resolution

Get precise root cause insights during incidents to resolve issues faster.

Proactively prevent incidents

Identify emerging risks before they impact your services and SLOs.

Understand system behavior

Gain deep insights into why your systems behave the way they do.

Scale reliability

Maintain reliability across complex, fast-changing systems at scale.

Optimize performance

Continuously improve system performance with actionable insights.

Other Platforms Supported

While this quickstart guide focuses on Kubernetes, Causely also supports:

  • Container Orchestration: Nomad, Docker, ECS
  • GitOps: Argo CD, Flux
  • Virtual Machines: Direct installation on VMs

For detailed installation instructions for these platforms, visit the Installation Overview page.