WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Not Supported / What is vc-ws1a-broker service on vCenter Server Appliance (VCSA)?

What is vc-ws1a-broker service on vCenter Server Appliance (VCSA)?

09.07.2023 by William Lam // 2 Comments

When vSphere 8.0 Update 1 was released, I noticed an interesting message about containers being installed while deploying the vCenter Server Appliance (VCSA) ...

Interesting ... while runc has been part of the VCSA for a few releases, it looks like it now launches ws1a-broker container in #vSphere80U1 by default ... ws1a-broker = Workspace One Broker? pic.twitter.com/cNVwx2vwFA

— William Lam (@lamw.bsky.social | @*protected email*) (@lamw) April 18, 2023

As shared in the Tweet/X above, it turns out this was for a service called vc-ws1a-broker, which I came to learn was for enabling the new Identity Federation Provider for the VCSA with Okta.

I ended up correctly guessing that the vc-ws1a-broker process was indeed our very own VMware Workspace One Access (WS1A) application but running as a Container workload within the VCSA. In vSphere 8.0 Update 2, support for Microsoft EntraID (formally Azure AD) is now also possible as additional identity provider option.

One important thing to be aware of the vc-ws1a-broker service is that it is configured to be able to consume up to 2GB of memory, as shown using the cloudvm-ram-size utility in the screenshot below.


This was something I had also indirectly discovered when comparing a "Tiny" VCSA deployment between vSphere 8.0 and 8.0 Update 1 release, where I noticed an additional 2GB of memory had been allocated for each deployment size. I confirmed this with Engineering that the additional 2GB of memory was indeed for the vc-ws1a-broker service also known as VMware Identity Single Container Service.

In fact, this very question came up recently on the VMTN communities about this additional 2GB of memory and whether the vc-ws1a-broker service could be disabled if you are not using the feature?

While I will not speak from a support standpoint, but from a technical point of view you can disable the vc-ws1a-broker service and reduce the memory footprint of your VCSA by 2GB if you have no intentions of using the new identity federation features. I currently do this for my homelab setup and that was also the basis of the VMTN post in an effort to reduce the amount of memory needed to run the VCSA.

Disclaimer: Disabling the vc-ws1a-broker service may lead to other unintentional impact, this should not be done in a production environment and GSS support should be consulted if you wish to disable this service.

By default, the vc-ws1a-broker service is configured to automatically start up which you can confirm by using the following command:

vmon-cli -s vc-ws1a-broker

If you wish to disable the service from starting up, you first need stop the vc-ws1a-broker service and then disable it by running the following two commands:

vmon-cli --stop vc-ws1a-broker
vmon-cli --update vc-ws1a-broker --starttype DISABLE

If we re-check the vc-ws1a-broker service, we can now see that it is now disabled and will not start when VCSA boots up.

vmon-cli -s vc-ws1a-broker


Finally, you can shutdown the VCSA and reduce the overall configured memory by 2GB to 12GB which is currently what I use in my homelab.

I was also interested to see whether updating or patching the VCSA would revert the disablement of the the vc-ws1a-broker service. I ran quick experiment by deploying VCSA 8.0 Update 1, disable the vc-ws1a-broker service and then update it to latest VCSA 8.0 Update 1c and it looks to maintain the disabled service, which is good.

With that said, it is possible that in future upgrades, especially when using a migration-based VCSA upgrade, that the default behavior of the VM will be configured with the additional 2GB of memory along with the vc-ws1a-broker service being enabled and you may need to periodically check and update.

More from my site

  • Exploring the new vSphere Privilege Recorder in vSphere 8.0 Update 1
  • Building custom Tanzu Kubernetes Releases (TKR) for vSphere with Tanzu
  • vSphere Pods using VDS based Supervisor in vSphere with Tanzu?
  • USB Network Native Driver Fling for ESXi 8.0 Update 1
  • ESXi configstorecli enhancement in vSphere 8.0 Update 1

Categories // Not Supported Tags // vc-ws1a-broker, vSphere 8.0 Update 1, Workspace One Access

Comments

  1. *protectedSomeDude says

    09/12/2023 at 11:30 pm

    Worked perfectly, thanks!

    Reply
  2. *protectedVess says

    04/01/2025 at 10:26 am

    Followed the instructions, the service is stopped and disabled, but running cloudvm-ram-size -l still shows 2GB allocated to it. I even ran cloudvm-ram-size -C 0 vc-ws1a-broker, then stopped and re-started all services and still the same. Finally, I rebooted the vCenter and again the damn service has 2GB allocated to it even if not running.

    [ ~ ]# cloudvm-ram-size -l
    OS = 1889
    vmdird = 22
    vmware-netdumper = 20
    vmware-rbd-watchdog = 100
    vmware-imagebuilder = 50
    applmgmt = 200
    vmware-envoy = 75
    vmware-envoy-hgw = 75
    vmware-envoy-sidecar = 75
    vmware-rhttpproxy = 25
    vmafdd = 22
    vmware-vsan-health = 100
    vsphere-ui = 853
    vmware-vapi-endpoint = 396
    vmware-cis-license = 192
    vmware-eam = 168
    lookupsvc = 100
    vmware-vpxd-svcs = 1045
    vmware-perfcharts = 357
    vmware-sca = 128
    vmware-sps = 478
    vmware-stsd = 538
    vmware-content-library = 473
    vmcad = 124
    vmware-vpostgres = 699
    vmware-postgres-archiver = 5
    vmware-vdtc = 35
    vmware-vpxd = 1024
    vmware-vsm = 160
    vmonapi = 15
    vmware-vmon = 5
    vmware-updatemgr = 314
    vcha = 46
    vmware-hvc = 120
    vmware-trustmanagement = 130
    vmware-certificatemanagement = 274
    vmware-certificateauthority = 100
    vmware-pod = 200
    observability = 80
    observability-vapi = 112
    vmware-infraprofile = 212
    vmware-analytics = 306
    vmware-topologysvc = 120
    wcp = 128
    vlcm = 150
    vstats = 40
    vtsdb = 220
    vc-ws1a-broker = 2048
    TOTAL(MB) = 14048

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...