You create a project to which you add members and cloud zones so that the project members can deploy their cloud templates to the associated zones. As the Automation Assembler administrator, you create a project for a development team. You can then assign a project administrator or you can operate as the project administrator.

When you create a cloud template, you first select the project to associate it with. The project must exist before you can create the cloud template.

Ensure that your projects support the business needs of the development team.

  • Does the project provide the resources that support the team's goals. For an example of how the infrastructure resources and a project support a cloud template, see Tutorial: Setting up and testing multi-cloud infrastructure and deployments in Automation Assembler.
  • Do your project members require or expect their deployments to be shared or private. Shared deployments are available to all the project members on the Deployments page, not only the deploying member. You can change the deployment sharing state at anytime.

    When you share the deployment with project members, the members can run the same day 2 action. To manage the ability of members to run day 2 actions, you can create day 2 policies in Automation Service Broker. The policies apply to Automation Assembler and Automation Service Broker deployments.

    To learn more about the day 2 policies, see How do I entitle deployment users to day 2 actions using policies

You might see a project in your projects list named org-default-project that you did not create in the VMware Cloud Services console or in VMware Aria Automation. This project is a default project that might be used by other VMwareVMware integrations. It does not affect your projects. You cannot change the name, remove it, or create another project with this name.

This procedure is based on creating an initial project that includes only the basic configurations. As your development team creates and deploys their cloud templates, you might modify to the project. You can add constraints, custom properties, and other options to improve deployment efficiencies. See the articles available in Learn more about Automation Assembler projects.



  1. Select Infrastructure > Administration > Projects, and click New Project.
  2. Enter the project name.
  3. Click the Users tab.
    1. To make deployments by project members accessible only to the requesting user, turn off Deployment sharing. To ensure that you can assign the ownership of a deployment to another member of the project, verify that the Deployment sharing is turned on.
    2. Add users or user groups with assigned roles.
      User roles based on groups allows users to come and go from your Active Directory groups rather than requiring the project administrator to constantly update the individual users in the project. For example, if deployment ownership is based on groups, you can change the ownership of a deployment to the group. Any notifications are sent to all the group members, allowing anyone to respond.
  4. Click the Provisioning tab and add one or more cloud zones.

    Add any cloud zones and virtual private zones that contain the resources that support the cloud templates deployed by the project users.

    For each zone, you can set a zone priority and you can limit the amount of resources that the project can use. For more information about limits see Using cloud zone resource limits.

  5. If the workloads requested for this project take more than two hours to deploy, enter a longer value for the Timeout.
    The default value is two hours.
  6. Click Create.
  7. To test your project with the project cloud zones, click Test Configuration on the Projects page.
    The simulation runs a standardized hypothetical deployment test against the project cloud zone resources. If it fails, you can review the details and correct your resource configuration.

What to do next

Get started with cloud templates. See Designing your Automation Assembler deployments.