Scale your Private Access Connector VM instances based on metric thresholds by creating dynamic scaling policies.
Automatic scaling requires EC2 detailed monitoring which incurs charges. For more information, see Amazon CloudWatch documentation.
True: EC2 detailed monitoring is enabled. Go to step 3.
False: EC2 detailed monitoring is not enabled. Go to step 2.
The CloudWatch alarms are used to create dynamic scaling policies in the later step.
Field |
Setting |
|
---|---|---|
Metric |
Statistic |
Average |
Period |
1 minute |
|
Conditions |
Threshold type |
Static |
When CPUUtilization is |
Greater |
|
than... |
|
|
Datapoints to alarm |
5 out of 5 |
Field |
Setting |
|
---|---|---|
Metric |
Statistic |
Average |
Period |
1 minute |
|
Conditions |
Threshold type |
Static |
When CPUUtilization is |
Lower |
|
than... |
|
|
Datapoints to alarm |
10 out of 10 |
Field |
Setting |
---|---|
Policy type |
Simple scaling |
Scaling policy name |
A unique name to identify the policy |
CloudWatch alarm |
The CloudWatch alarm created for scaling out |
Take the action |
Add 1 capacity units |
And then wait |
600 |
Field |
Setting |
---|---|
Policy type |
Simple scaling |
Scaling policy name |
A unique name to identify the policy |
CloudWatch alarm |
The CloudWatch alarm created for scaling in |
Take the action |
Remove 1 capacity units |
And then wait |
1200 |