What Are Restrictions on Using AS?
Only applications that are stateless and horizontally scalable can run on instances in an AS group. ECS instances in an AS group can be released automatically by AS, so they cannot be used to save application status information (such as session statuses) or related data (such as database data and logs).
If the application status or related data must be saved, you can store the information on separate servers.
Table 1 lists the AS quotas.
Item |
Description |
Default |
---|---|---|
AS group |
Maximum number of AS groups per region per account |
10 |
AS configuration |
Maximum number of AS configurations per region per account |
100 |
AS policy |
Maximum number of AS policies per AS group |
10 |
Instance |
Maximum number of instances per AS group |
300 |
Bandwidth scaling policy |
Maximum number of bandwidth scaling policies per region per account |
10 |
General FAQs
- What Are Restrictions on Using AS?
- Must I Use AS Together With ELB and Cloud Eye?
- Is AS Billed?
- Will an Abrupt Change in Monitoring Metric Values Trigger an Unnecessary Scaling Action?
- How Many AS Policies and AS Configurations Can I Create and Use?
- Can AS Automatically Scale Up or Down vCPUs, Memory, and Bandwidth of ECSs?
- What Is an AS Quota?
- How Do I Fix the Error "The key pair does not exist" When I Connect to an Instance?
- What Types of EIP and Shared Bandwidths Can Be Adjusted by AS?
- What Types of ECS and HECS Instances Can Be Scaled by AS?
- If the OS of an ECS Instance in an AS Group Is Upgraded, Can AS Automatically Add Instances with the Newest OS During the Next Scale-out Action?
- Can AS Add Yearly/Monthly ECS Instances When It Scales Out an AS Group?
- Can AS Increase Bandwidths as Required?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more