Changes from previous(Excerpt from release notes):
boto v2.30.0
============
This release adds new Amazon EC2 instance types, new regions for AWS
CloudTrail and Amazon Kinesis, Amazon S3 presigning using signature
version 4, and several documentation and bugfixes.
boto v2.31.0
============
This release adds support for Amazon CloudWatch Logs.
boto v2.31.1
============
This release fixes an installation bug in the 2.31.0 release.
boto v2.32.0
============
This release includes backward-compatible support for Python 3.3 and
3.4, support for IPv6, Amazon VPC connection peering, Amazon SNS
message attributes, new regions for Amazon Kinesis, and several fixes.
boto v2.32.1
============
This release fixes an incorrect Amazon VPC peering connection call,
and fixes several minor issues related to Python 3 support including a
regression when pickling authentication information.
boto v2.33.0
=============
This release adds support for Amazon Route 53 Domains, Amazon Cognito
Identity, Amazon Cognito Sync, the DynamoDB document model feature,
and fixes several issues.
boto v2.34.0
============
This release adds region support for ``eu-central-1`` , support to
create virtual mfa devices for Identity and Access Management, and
fixes several sigv4 issues.
boto v2.35.0
===========
This release adds support for Amazon EC2 Classic Link which allows
users to link classic instances to Classic Link enabled VPCs, adds
support for Amazon CloudSearch Domain, adds sigv4 support for Elastic
Load Balancing, and fixes several other issues including issues making
anonymous AWS Security Token Service requests.
boto v2.35.1
============
This release fixes a regression which results in an infinite while
loop of requests if you query an empty Amazon DynamoDB table.
boto v2.32.2
============
This release adds ClassicLink support for Auto Scaling and fixes a few
issues.
boto v2.36.0
============
This release adds support for AWS Key Management Service (KMS), AWS
Lambda, AWS CodeDeploy, AWS Config, AWS CloudHSM, Amazon EC2 Container
Service (ECS), Amazon DynamoDB online indexing, and fixes a few
issues.
boto v2.37.0
============
This release updates AWS CloudTrail to the latest API, adds new regional
service endpoints and fixes bugs in several services.
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
Changes:
2.5.2
Release 2.5.2 is a bugfix release.
2.5.1
Release 2.5.1 is a bugfix release.
2.5.0
This release includes:
Support for IAM Roles for EC2 Instances
Added support for Capabilities in CloudFormation
Spot instances in autoscaling groups
Internal ELB's
Added tenancy option to run_instances
2.4.0
This release includes:
Initial support for Amazon Cloudsearch Service.
Support for Amazon's Marketplace Web Service.
Latency-based routing for Route53
Support for new domain verification features of SES.
A full rewrite of the FPS module.
Support for BatchWriteItem in DynamoDB.
Additional EMR steps for installing and running Pig scripts.
Support for additional batch operations in SQS.
Better support for VPC group-ids.
Many, many bugfixes from the community. Thanks for the reports
and pull requests!
2.3.0
This release includes initial support for Amazon Simple Workflow
Service.
The API version of the FPS module was updated to 2010-08-28.
This release also includes many bug fixes and improvements in the
Amazon DynamoDB module. One change of particular note is the behavior
of the new_item method of the Table object. See
http://readthedocs.org/docs/boto/en/2.3.0/ref/dynamodb.html#module-boto.dynamodb.table
for more details.
2.2.2
This is a bugfix release.
2.2.1
The 2.2.1 release fixes a packaging problem that was causing problems
when installing via pip.
2.2.0
Some highlights of this release:
Support for Amazon DynamoDB service.
Support for S3 Object Lifecycle (Expiration).
Allow anonymous request for S3.
Support for creating Load Balancers in VPC.
Support for multi-dimension metrics in CloudWatch.
Support for Elastic Network Interfaces in EC2.
Support for Amazon S3 Multi-Delete capability.
Support for new AMIversion and overriding of parameters in EMR.
Support for SendMessageBatch request in SQS.
Support for DescribeInstanceStatus request in EC2.
Many, many improvements and additions to API documentation and
Tutorials. Special thanks to Greg Taylor for all of the Sphinx
cleanups and new docs.
2.1.1
The 2.1.1 release fixes one serious issue with the RDS module.
2.1.0
Some highlights of this release:
Server-side encryption now supported in S3.
Better support for VPC in EC2.
Support for combiner in StreamingStep for EMR.
Support for CloudFormations.
Support for streaming uploads to Google Storage.
Support for generating signed URL's in CloudFront.
MTurk connection now uses HTTPS by default, like all other
Connection objects.
You can now PUT multiple data points to CloudWatch in one call.
CloudWatch Dimension object now correctly supports multiple
values for same dimension name.
Lots of documentation fixes/additions
2.0
Highlights
There have been many, many changes since the 2.0b4 release. This overview highlights some of those changes.
Fix connection pooling bug: don't close before reading.
Added AddInstanceGroup and ModifyInstanceGroup to boto.emr
Merge pull request #246 from chetan/multipart_s3put
AddInstanceGroupsResponse class to boto.emr.emrobject.
Removed extra print statement
Merge pull request #244 from ryansb/master
Added add_instance_groups function to boto.emr.connection.
Built some helper methods for it, and added AddInstanceGroupsResponse
class to boto.emr.emrobject.
Added a new class, InstanceGroup, with just a init and repr.
Adding support for GetLoginProfile request to IAM. Removing
commented lines in connection.py. Fixes GoogleCode issue 532.
Fixed issue #195
Added correct sax reader for boto.emr.emrobject.BootstrapAction
Fixed a typo bug in ConsoleOutput sax parsing and some PEP8
cleanup in connection.py.
Added initial support for generating a registration url for
the aws marketplace
Fix add_record and del_record to support multiple values, like
change_record does
Add support to accept SecurityGroupId as a parameter for ec2
run instances. This is required to create EC2 instances under
VPC security groups
Added support for aliases to the add_change method of
ResourceRecordSets.
Resign each request in a retry situation. Some services are
starting to incorporate replay detection algorithms and the
boto approach of simply re-trying the original request triggers
them. Also a small bug fix to roboto and added a delay in the
ec2 test to wait for consistency.
Fixed a problem with InstanceMonitoring parameter of
LaunchConfigurations for autoscale module.
Route 53 Alias Resource Record Sets
Fixed App Engine support
Fixed incorrect host on App Engine
Fixed issue 199 on github.
First pass at put_metric_data
Changed boto.s3.Bucket.set_acl_xml() to ISO-8859-1 encode the
Unicode ACL text before sending over HTTP connection.
Added GetQualificationScore for mturk.
Added UpdateQualificationScore for mturk
import_key_pair base64 fix
Fixes for ses send_email method better handling of exceptions
Add optional support for SSL server certificate validation.
Specify a reasonable socket timeout for httplib
Support for ap-northeast-1 region
Close issue #153
Close issue #154
we must POST autoscale user-data, not GET. otherwise a HTTP
505 error is returned from AWS. see:
http://groups.google.com/group/boto-dev/browse_thread/thread/d5eb79c97ea8eecf?pli=1
autoscale userdata needs to be base64 encoded.
Use the unversioned streaming jar symlink provided by EMR
Updated lss3 to allow for prefix based listing (more like actual
ls)
Deal with the groupSet element that appears in the instanceSet
element in the DescribeInstances response.
Add a change_record command to bin/route53
Incorporating a patch from AWS to allow security groups to be
tagged.
Fixed an issue with extra headers in generated URLs. Fixes
http://code.google.com/p/boto/issues/detail?id=499
Incorporating a patch to handle obscure bug in apache/fastcgi.
See http://goo.gl/0Tdax.
Reorganizing the existing test code. Part of a long-term project
to completely revamp and improve boto tests.
Fixed an invalid parameter bug (ECS) #102
Adding initial cut at s3 website support.
Remove devel/py-ctypes (only needed by and supporting python24).
Remove PYTHON_VERSIONS_ACCEPTED and PYTHON_VERSIONS_INCOMPATIBLE
lines that just mirror defaults now.
Miscellaneous cleanup while editing all these files.
- Support for RDS, BootFromEBS, Spot Instances, and more
- Fixes Issue 251, a problem with POST when using Eucalyptus
- Fixes serious S3 issue (245) and issue 243 and 244
- Adds support for Autoscale, CloudWatch, ELB.
- Adds support for new SQS features
Also, added 26 to PYTHON_VERSIONS_ACCEPTED.
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
Adds support for Signature Version 2 for increased security with EC2, SQS, SDB
Add support for Regions in EC2
Fixes Issue 172, Issue 178, Issue 180, Issue 181, Issue 182
Fixes issue 165, issue 172, issue 173, issue 174, issue 176, issue 177
Adds initial support for CloudFront (ahem) service
Fixes stupid and dangerous copy/paste error in SDB support.
Support for EBS, QueryWithAttributes, lots of bugfixes.
not provide a ChangeLog, instead referring users to the subversion
history. This version has quite a few bug fixes over 1.0a--I simply do
not have the time to list them here.
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
sysutils/duplicity could use amazon web services.
Blurb:
Boto is a Python package that provides interfaces to Amazon Web Services.
At the moment, boto supports S3 (Simple Storage Service) and SQS (Simple
Queue Service) via the REST API's provided by those services and EC2
(Elastic Compute Cloud) via the Query API. The intent is to support
additional services in the future.
The goal of boto is to provide a very simple, easy to use, lightweight
wrapper around the Amazon services. Not all features supported by the
Amazon Web Services will be supported in boto. Basically, those
features I need to do what I want to do are supported first. Other
features and requests are welcome and will be accomodated to the best
of my ability. Patches and contributions are welcome!
Boto was written using Python 2.4.1 on Mac OSX. It has also been tested
on Linux Fedora Core 4 using Python 2.4.1. Boto requires no additional
libraries or packages other than those that are distributed with Python 2.4.1.
NOTE: A patch was supplied recently by josh.bressers that should allow
boto to run in Python 2.3. I have not tested this myself.
[NOTE: I did not mark 23 as an acceptable python version]
There is some documentation for boto, mainly in the form of tutorials.
Check in the doc directory of the distribution. You can also check out
the unit tests in the tests directory of the distribution for examples of use.
You AWS credentials can be passed into the methods that create S3 and SQS
connections. Alternatively, boto will check for the existance of the
following environment variables to ascertain your credentials:
AWS_ACCESS_KEY_ID - Your AWS Access Key ID
AWS_SECRET_ACCESS_KEY - Your AWS Secret Access Key
