2.1 Creating a subaccount

The first step when setting up BAS is to create a subaccount, which needs to be created against the main account in the BTP cockpit. A main account can consist of several subaccounts. It lets you manage your subscription, enable services, and deploy applications. It is important to note that subaccounts under a single global account are independent of each other.

A global account has a quota and an entitlement based on the service you purchase:

• Quota—this is the total memory that you purchase as part of your license.
• Entitlement—this is the service you want to purchase. It could be based on a specific service plan or tools.

Each subaccount needs to be enabled for a runtime environment. If you enable a Cloud Foundry environment, the system will create a Cloud Foundry org (organization) for which you create Space(s) to help you separate services. If you select a Kyma environment, the system will create a Kubernetes Cluster (multiple node machines—virtual or physical—that host containerized applications, managed and coordinated centrally). You can then create a Namespace to separate your services.

BAS is available in the US region, so you can create a new subaccount from the BTP cockpit by selecting US as the region. Name it BAS_DEMO. You only need to provide the subaccount name, description (usually free text) and the region. Figure 2.1 shows the subaccount which has been created under the global account for hosting our BAS application

Figure 2.1: Subaccount created

It only takes a couple of minutes to create a subaccount. The next step is to assign a service plan to your subaccount