Sauce Labs Customer Idea Portal

Submit an idea and make Sauce Labs even better!

Improved Tunnel management

We use a lot of Tunnels while running our jobs because we run many concurrent jobs. Each jenkins jobs creates its own tunnel (no sharing). We observe the following issues


1. No insight into the number of tunnels for the account. SauceLabs portal show clearly show the max tunnel limit.

2. By default the account should be pre-configured to have at least one tunnel per VM.


As a customer, I actually don't really want to deal with tunnel management. SauceLabs should handle this behind the scenes for me. I just want to buy the VM.

  • Guest
  • Nov 5 2015
  • Already exists
  • Attach files
  • Zuzana Bodikova commented
    5 Jun, 2017 07:10pm

    From our customer Splunk: 


    In a large organization, how can we enforce policies around tunnels? Seems like anyone with an account can spin up a tunnel and as an organization, we can run into issues due to the max limit.

    o    It would be helpful to see these tunnel limits and who is using these limits in the analytics dashboard.

    o    It would be helpful for org admins to assign some number of tunnels to specific accounts. In our setup, I would have loved to assign 10 tunnels out of the 30 to qtidev so that others cannot cannibalize them and starve out important accounts.

    o    It would be helpful to disallow certain accounts and their child accounts from being able to spin up their own tunnels. This way, we can force users to leverage the shared tunnel setup.

  • Chiarng Lin commented
    27 Sep, 2016 09:02pm

    1) New dashboard UI includes a tunnels section, please refer to that to see how many existing tunnels you are running actively. 

    2) We highly do not suggest that you run one tunnel per job. Generally, customers either run one tunnel forever, or a tunnel per build.