Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 (https://ideas.ibm.com).

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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Workspace Instana
Categories Backend Enablement
Created by Guest
Created on Jul 9, 2026

Enable configurable Instana backend and agent communication ports instead of requiring default 80/443 ports.

Many enterprise customers operate Instana in highly restricted network environments where standard HTTP/HTTPS ports such as 80 and 443 may be tightly controlled by centralized security or network teams. In these environments, customers may be required to use internally approved non-standard ports for specific systems, zones, or monitoring platforms. Requiring Instana backend or agent communication to use only the default 80/443 ports can delay deployment, require additional exception approvals, or prevent production adoption.

This idea is to provide an officially supported way to configure alternative ports for Instana backend ingress and agent communication endpoints.

The feature should allow customers to:

  • Change the default backend listener or ingress ports from 80/443 to customer-approved ports.
  • Configure Instana agents to communicate with the backend using those alternative ports.
  • Reflect the selected ports consistently across stanctl, installation templates, agent deployment commands, health checks, TLS/certificate configuration, and documentation.

This would benefit customers with strict internal network standards, healthcare, public sector, financial customers, and managed Kubernetes environments where port usage is centrally governed.

Idea priority High
  • Admin
    Marcelo Ibanez
    Jul 16, 2026

    Thank you for raising this idea.

    After investigating with our team, we can confirm that this capability is technically supported in Instana Self-Hosted — however, we recognize that the current documentation does not make this clear for your use case.

    The external HTTPS port is configurable in the coreSpec. This is actually already used internally for a specific use case, so we know it works.

    I will set this idea to In Development. As soon as our capacity allows it, we will work on the docs.
    In the meantime I'll slack you to see how we can help you