Specifications

This topic describes CAE specifications and restrictions.

Supported Regions

Table 1 lists the supported regions.

**Table 1** Supported regions
Region	Region ID
AP-Singapore	ap-southeast-3
ME-Riyadh	me-east-1
TR-Istanbul	tr-west-1
AF-Johannesburg	af-south-1
LA-Mexico City2	la-north-2

Quota Limits

A quota is the maximum number of resources that you can create. Table 2 provides the resource quota limitations.

**Table 2** Quota
Resource	Maximum Quota	Modifiable
Environment in each region	1	Yes
Number of components that can be created by each tenant in each region	50	Yes
Number of instances of each component	99	No
CPU cores	2 cores per instance	No
Memory	4 GB per instance	No

To increase environments and components, submit a service ticket.

Component Specifications

Table 3 lists memory sizes for each CPU core.

**Table 3** Component specifications
CPU (cores)	Memory (GiB)
0.5	1
0.5	2
1	1
1	2
1	4
2	2
2	4

More specifications are coming soon.

Bandwidth Limits

Table 4 lists bandwidth limits in public network access through EIP

**Table 4** Bandwidth limits
Access	Bandwidth Limit (Mbit/s)
Public network to CAE	20
Application to public network	20

To increase bandwidth limit, submit a service ticket.

Storage

CAE cannot read or write local disks. You are advised to mount an OBS parallel file system. For details, see Parallel File System Overview.

Specifications on Temporary Storage

If you have configured a log path and selected local disk storage, CAE uses the storage to store log files. The temporary files generated by the file system or program running on the image occupy the storage space.

Containerized applications can read temporary data and write it to the temporary storage. The storage is temporary and will be cleared after the container is stopped or restarted. Files written to the storage are visible only to the processes running in the current container.

The total storage of each instance depends on the total number of CPUs allocated to the instance. For details about specifications on the temporary storage, see Table 5. Specifications with more than three cores can be used only by whitelisted users. If you need to use such specifications, submit a service ticket

When using local disks for storage, you are advised to properly plan log storage and periodically rotate and clear logs to prevent component restart caused by excessive logs. If the log usage exceeds the limit, you are advised to use cloud storage for log configuration.