App Launchpad does not require inbound access and does not expose network ports to the Internet.

App Launchpad communicates only with VMware Cloud Director and the AMQP Broker in your environment. If you use VMware Cloud Director 10.2, App Launchpad only communicates with VMware Cloud Director and does not require communicating with an AMQP broker.

App Launchpad requires outbound access to the Internet to connect to VMware Marketplace, customer defined Helm Chart repositories, VMware Cloud services, and the services used by the Customer Experience Improvement Program. Make sure that outbound access is allowed for the following destinations:
  • For connections to VMware Marketplace, allow access to https://gtw.marketplace.cloud.vmware.com/*.
  • For connections to VMware Cloud services, allow access to https://console.cloud.vmware.com/*.
  • For connections to services used by the Customer Experience Improvement Program, allow access to https://scapi.vmware.com/*.

The following diagram illustrates the network architecture and the connections between internal and external components of App Launchpad.

The diagram illustrates the network architecture and the connections between external and internal components of App Launchpad.

VMware Marketplace Requirements

To import VM applications from VMware Marketplace, make sure that the public REST API endpoint of VMware Cloud Director is accessible for VMware Marketplace. When importing VM applications, VMware Marketplace creates or updates the catalogs of App Launchpad by using VMware Cloud Director API. Make sure that VMware Marketplace can access the following VMware Cloud Director API endpoints:
  • /api/admin/org/%s/catalogs
  • /api/catalog/%s
  • /api/admin/catalog/%s
  • /action/sync

Container Service Extension Requirements

To use the Container Service Extension of VMware Cloud Director as an application deployment target, App Launchpad requires outbound access to the control plane node of each Kubernetes cluster that the Container Service Extension manages.