$ aws autoscaling put-scaling-policy \
--policy-name as-policy-scale-up \
--auto-scaling-group-name as-group \
--adjustment-type ChangeInCapacity \
--scaling-adjustment 1 \
--cooldown 300
{
"ResponseMetadata": {
"RequestId": "4411e437-9b6a-11e2-933c-010eb2f029e6"
},
"PolicyARN": "arn:aws:autoscaling:us-east-1:332100208493:scalingPolicy:c534dcbe-91c1-4714-907a-b4974bac7c57:autoScalingGroupName/as-group:policyName/as-policy-scale-up"
}
把 PolicyARN 記下來，下一步會用到$ aws cloudwatch put-metric-alarm \ --evaluation-periods 1 \ --namespace "AWS/EC2" \ --comparison-operator GreaterThanThreshold \ --alarm-name alarm-high-cpu \ --statistic Average \ --threshold 60 \ --period 600 \ --metric-name CPUUtilization \ --alarm-actions arn:aws:autoscaling:us-east-1:332100208493:scalingPolicy:c34f62a8-bb82-4430-9390-67468a7a65f9:autoScalingGroupName/as-group:policyName/as-policy-scale-up
$ aws autoscaling put-scaling-policy \
--policy-name as-policy-scale-down \
--auto-scaling-group-name as-group \
--adjustment-type ChangeInCapacity \
--scaling-adjustment -1 \
--cooldown 300
{
"ResponseMetadata": {
"RequestId": "c58093f7-9b6b-11e2-82fc-2bb2a883e37c"
},
"PolicyARN": "arn:aws:autoscaling:us-east-1:332100238493:scalingPolicy:141d692b-9ae8-4ef8-8d98-7de605c3fe04:autoScalingGroupName/as-group:policyName/as-policy-scale-down"
}
$ aws cloudwatch put-metric-alarm \ --evaluation-periods 1 \ --namespace "AWS/EC2" \ --comparison-operator LessThanThreshold \ --alarm-name alarm-low-cpu \ --statistic Average \ --threshold 40 \ --period 600 \ --metric-name CPUUtilization \ --alarm-actions arn:aws:autoscaling:us-east-1:332100238493:scalingPolicy:141d692b-9ae8-4ef8-8d98-7de605c3fe04:autoScalingGroupName/as-group:policyName/as-policy-scale-down
$ aws autoscaling create-launch-configuration \ --launch-configuration-name as-config \ --image-id ami-7061fb19 --instance-type t1.micro
$ aws autoscaling describe-launch-configurations
$ aws autoscaling create-auto-scaling-group \ --auto-scaling-group-name as-group \ --launch-configuration-name as-config \ --availability-zones us-east-1a \ --load-balancer-names webserver \ --max-size 3 --min-size 2 \ --default-cooldown 300這個指令一執行，auto scaling 就被啟動了。
$ aws autoscaling describe-auto-scaling-groups
"Instances": [
{
"InstanceId": "i-e0a77c8c",
"AvailabilityZone": "us-east-1a",
"HealthStatus": "Healthy",
"LifecycleState": "Pending",
"LaunchConfigurationName": "as-config"
},
{
"InstanceId": "i-e2a77c8e",
"AvailabilityZone": "us-east-1a",
"HealthStatus": "Healthy",
"LifecycleState": "Pending",
"LaunchConfigurationName": "as-config"
}
],
$ aws autoscaling create-auto-scaling-group \ --auto-scaling-group-name as-group \ --launch-configuration-name as-config \ --availability-zones us-east-1a \ --load-balancer-names webserver \ --max-size 3 --min-size 2 \ --health-check-type ELB --health-check-grace-period 300
$ aws autoscaling update-auto-scaling-group \ --auto-scaling-group-name as-group \ --min-size 0 --max-size 0
$ aws autoscaling delete-auto-scaling-group --auto-scaling-group-name as-group
$ pip install awscli
$ vim ~/.aws.conf
aws_access_key_id=AKIAIJQ7YGMRQTBIH7HJ aws_secret_access_key=ngbsB02udwOmDztTesTJuuZ8ZdkA2ZRq0VHvunX region=us-east-1
$ export AWS_CONFIG_FILE=~/.aws.conf
$ export AWS_ACCESS_KEY_ID=AKIAIJQ7YGMRQTBIH7HJ $ export AWS_SECRET_ACCESS_KEY=ngbsB02udwOmDztTesTJuuZ8ZdkA2ZRq0VHvunX $ export AWS_DEFAULT_REGION=us-east-1
$ aws ec2 run-instances --image-id ami-002bf169 --min-count 1 --max-count 1 \
--instance-type m1.small --placement '{"availability_zone":"us-east-1a"}'
{
"OwnerId": "132130202433",
"ReservationId": "r-ec8f2587",
"requestId": "05125c46-dfbd-4ef4-89a8-0efe6f59ba87",
"Groups": [
{
"GroupName": "default",
"GroupId": "sg-2337df4f"
}
],
"Instances": [
{
"Monitoring": {
"State": "disabled"
},
"PublicDnsName": "",
"KernelId": "aki-825ea7eb",
"State": {
"Code": 0,
"Name": "pending"
},
"EbsOptimized": false,
"LaunchTime": "2013-03-30T02:58:42.000Z",
"ProductCodes": [],
"StateTransitionReason": "",
"InstanceId": "i-ff16069f",
"ImageId": "ami-002bf169",
"PrivateDnsName": "",
"SecurityGroups": [
{
"GroupName": "default",
"GroupId": "sg-2437df4f"
}
],
"ClientToken": "",
"InstanceType": "m1.small",
"NetworkInterfaces": [],
"Placement": {
"Tenancy": "default",
"GroupName": "",
"AvailabilityZone": "us-east-1a"
},
"Hypervisor": "xen",
"BlockDeviceMappings": [],
"Architecture": "x86_64",
"StateReason": {
"Message": "pending",
"Code": "pending"
},
"VirtualizationType": "paravirtual",
"RootDeviceType": "instance-store",
"AmiLaunchIndex": 0
}
]
}
$ aws ec2 describe-instances
$ aws ec2 help $ aws ec2 run-instances help
上例就是設定 logs 底下的 object 在 365天後轉移到 Glacier，並在3650天後自動刪除。rule_id logs/ Enabled 365 GLACIER 3650
SELECT * FORM `article` OFFSET LIMIT 10取第二頁:
SELECT * FORM `article` OFFSET LIMIT 10 OFFSET 10取第三頁:
SELECT * FORM `article` OFFSET LIMIT 10 OFFSET 20
sdb_conn = SDBConnection(...)
# Skip first 20 items
query = "SELECT COUNT(*) FORM `article` OFFSET LIMIT 20"
rs = sdb_conn.select(sdb_domain, query=query)
# Get target page
query = "SELECT * FORM `article` OFFSET LIMIT 10"
rs2 = sdb_conn.select(sdb_domain, query=query, next_token=rs.next_token)
for item in rs2:
...
Too many value tests per predicate in the query expression
或
Client error : Too many value tests per predicate in the query expression.
SELECT * FROM domain WHERE id='1' OR id='2' OR ... id='20' OR id='21'
SELECT * FROM domain WHERE id in ('1', '2', ... '20', '21')
SELECT * FROM domain WHERE id in ('1', '2', ... '20') OR id in ('21', ...)
SELECT * FROM `domain` WHERE
account in ('key1', 'key2', 'key3', 'key4', 'key5', 'key6', 'key7', 'key8', 'key9', 'key10',
'key11', 'key12', 'key13', 'key14', 'key15', 'key16', 'key17', 'key18', 'key19', 'key20') OR
dummy IS NOT NULL OR
account in ('key21', 'key22', 'key23', 'key24', 'key25', 'key26', 'key27', 'key28', 'key29', 'key30',
'key31', 'key32', 'key33', 'key34', 'key35', 'key36', 'key37', 'key38', 'key39', 'key40')
沒錯，就是加了"OR dummy IS NOT NULL"這個多餘的條件在中間就可以下達多個條件了！
Cannot complete the install because one or more required items could not be found.
Software currently installed: Amazon SimpleDB Management 1.0.0.v201110211341 (com.amazonaws.eclipse.datatools.enablement.simpledb.feature.feature.group 1.0.0.v201110211341)
Missing requirement: Eclipse Data Tools Platform Amazon SimpleDB UI Plug-in 1.0.0.v201110211341 (com.amazonaws.eclipse.datatools.enablement.simpledb.ui 1.0.0.v201110211341) requires 'bundle org.eclipse.datatools.sqltools.sqlscrapbook 1.0.0' but it could not be found
Cannot satisfy dependency:
From: Amazon SimpleDB Management 1.0.0.v201110211341 (com.amazonaws.eclipse.datatools.enablement.simpledb.feature.feature.group 1.0.0.v201110211341)
To: com.amazonaws.eclipse.datatools.enablement.simpledb.ui [1.0.0.v201110211341]