Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace Instana
Categories Sensor
Created by Guest
Created on Feb 14, 2023

High Availability (HA) for Instana AWS Agent (Cloud Watch Kinesis Stream)

We want to make heavy use of the AWS Instana Agent on various AWS Accounts 50+. The Teams want to see and use the AWS Metric Data in Instana for Alerting and Analysis.
Therefore we plan to set up an Instana AWS Agent. We learned that we could only use one dedicated instance of the AWS Agent per Account from the past and other customers. This means a failover of the Instance will cause metric data loss, which we want to prevent or keep as small as possible.
We plan to set up a 1:1 AWS Autoscaling group, which setups everything automatically. This will also have a turnaround of min. 5 min, which feels too long for us.
Therefore we ask for a better solution, enabling us to use Kubernetes or AWS Instances with multiple machines (warm standby) with the leader elector principle.

- When an Instana AWS Agent or its underlying hardware crashes, a warm standby AWS Instana Agent is immediately started, with almost no metric data loss.
- When an update is executed on the agents, the AWS Agent will hand over the metric collection to another Agent without metric data loss.
- We can use the AWS Agent on Kubernetes / Openshift like we use a Kubernetes Leader Agent.

Desired Solution:
Add a Kubernetes sensor like Leader / Elector principle for Instana AWS Agents on an Account basis. This should enable us always to have exactly one Instana AWS Agent per AWS Account active. Of Course, an Instana AWS Agent should be able to manage multiple AWS Accounts.



Idea priority Medium
  • Admin
    Rodoljub Radivojevic
    Mar 2, 2023

    We are currently working on AWS CloudWatch metric stream PoC including metrics ingestion in Instana Backend via Kinesis Firehose.

    This approach has several advantages:

    • Improved latency

    • Reduced costs 3.3x

    • Avoiding problems with agent such as deployment, updates, outages, scaling, HA, etc.

    • If you requests monitoring of new AWS service, we need to build new sensor and they can wait significant amount of time. With metric streams all AWS services are supported by default.

    During the call some time ago you agreeed to participate in PoC/Closed beta.

    After we have the implementatio ready for closed beta I will let you know so you can include and test it.