OLD | NEW |
(Empty) | |
| 1 ============== |
| 2 Change history |
| 3 ============== |
| 4 |
| 5 .. contents:: |
| 6 :local: |
| 7 |
| 8 .. _version-2.0: |
| 9 |
| 10 2.0 |
| 11 === |
| 12 :release-date: 2011-07-14 |
| 13 |
| 14 .. _v20-important: |
| 15 |
| 16 Important Notes |
| 17 --------------- |
| 18 |
| 19 * Backwards-incompatible filter changes in the latest 2011 EC2 APIs |
| 20 |
| 21 In the latest 2011 EC2 APIs all security groups are assigned a unique |
| 22 identifier (sg-\*). As a consequence, some existing filters which used to t
ake |
| 23 the group name now require the group *id* instead: |
| 24 |
| 25 1. *group-id* filter in DescribeInstances (ie get_all_instances()) |
| 26 |
| 27 To filter by group name you must instead use the *group-name* filter |
| 28 |
| 29 2. *launch.group-id* filter in DescribeSpotInstanceRequests (ie get_all_spot
_instance_requests()) |
| 30 |
| 31 Unfortunately for now, it is *not* possible to filter spot instance |
| 32 requests by group name; the security group id *must* be used instead. |
| 33 |
| 34 This new security group id can be found in the *id* attribute of a boto |
| 35 SecurityGroup instance. |
OLD | NEW |