Set up Application Design Center

This document guides administrators through the initial setup for Application Design Center, which lets you design, share, and manage cloud infrastructure using an application-centric model. The setup process configures the following:

  • Application management, which lets you define the boundary for your application and manage its lifecycle.
  • An initial space where your team can collaborate.
  • A default catalog to store templates.
  • A Google-managed catalog with templates based on best practices.
  • One of the following Cloud Storage buckets for Terraform storage:

Before you begin

Choose a storage bucket option

When you create templates and applications, App Design Center stores Terraform code in a Cloud Storage bucket. Choose one of the following storage bucket options:

  • Automatically create a new bucket: Perform the setup in the console.
  • Use an existing storage bucket: Complete the setup using the App Design Center API.

You might use your own bucket if you have organization policies that prevent you from creating new buckets, or if you have established business practices that dictate bucket creation.

Verify existing storage bucket access

To complete the setup and use your own bucket, verify the following:

  1. You have access to use APIs. For more information, see Set up API access.

  2. Your bucket is in the same management project where you want to set up App Design Center.

  3. You have the following permissions on the bucket:

    • storage.buckets.get
    • storage.objects.create

Choose your application management boundary

An application management boundary is a centralized place for application management tasks, including API enablement, access control, billing, and quotas. Within the boundary, you can monitor, troubleshoot, optimize costs, and manage your Google Cloud resources in the context of your application.

Choose the boundary model that fits your organization:

  • Single-project boundary (Preview): Best for new users or small organizations where all resources reside in one project.
  • Folder-level boundary: Best for large organizations that manage resources across multiple projects and subfolders.

The following table compares the features of each boundary model:

Feature Single-project boundary (Preview) Folder-level boundary
Flexibility Complete the setup using default settings.
  • Specify a name for your space.
  • Select whether to disable Google-provided templates.
  • Post-setup, you can create additional spaces in the application management boundary.
Integrated products

Enable application management

When you enable application management, the system does one of the following to help you manage quotas and billing for your application:

  • Single-project (Preview): The system configures your project as a management project.
  • Folder-level: The system creates a new management project in the folder.

To enable application management, do the following:

Single-project (Preview)

  1. Make sure that your project has a linked billing account.

  2. Make sure that you have the required roles to enable application management and complete the setup, which creates your space.

  3. Application management is automatically enabled on your project when you complete the setup using the console. Alternatively, to perform the setup using the App Design Center API, enable application management on your project.

Folder-level

  1. Make sure that you have an organization resource.

  2. Make sure that you have the required roles to enable application management.

  3. Configure a folder for application management.

  4. Link a billing account to the management project.

  5. Configure the observability scope for the management project.

  6. Make sure that you have the required roles to complete the setup and create your space.

Verify required IAM roles

To perform the setup, ask your administrator to grant you the necessary roles on your project or boundary folder, as listed in the following table:

Task Required roles
Perform single-project initial setup Project Owner (roles/owner), or both of the following:
Application Design Center Admin (roles/designcenter.admin) and
Service Usage Admin (roles/serviceusage.serviceUsageAdmin)
Perform folder-level initial setup Both of the following:
Application Design Center Admin (roles/designcenter.admin) and
Application Admin (roles/designcenter.applicationAdmin)

For more information about roles, see Access control with IAM.

Set up App Design Center and create a new storage bucket

The setup process in the console creates a new Cloud Storage bucket to store application information. To use an existing bucket, see Set up App Design Center and use your own storage bucket.

Single-project (Preview)

To enable application management on a single project and set up App Design Center, do the following:

  1. Go to the Application Design Center Overview page.

    Go to Overview

  2. From the project picker, select the project where you want to configure application management.

  3. Click Go to Setup.

  4. In the Setup your project for application management pane, review the list of APIs that will be enabled.

  5. Click Enable. The system enables the APIs, and creates the storage bucket and default-space space.

  6. To store the Google Cloud resources that you deploy with App Design Center, create standard projects in your organization.

Folder-level

To set up App Design Center on your app-enabled folder, do the following:

  1. Go to the Application Design Center Overview page.

    Go to Overview