Hi all s3cmd fans!
The long requested *CloudFront invalidation* support is now available in
s3cmd-1.1.0-beta1 thanks to a sponsorship from Philipp Winkler and
Interactive 21 <http://interactive21.de>.
CF Invalidation is integrated with /s3cmd sync/ command:
~$ s3cmd *--cf-invalidate* --acl-public sync /local/path/
s3://<bucket>/remote/path/
[... uploading ...]
Created invalidation request for 4 paths
Check progress with: s3cmd cfinvalinfo cf://E9RB4B71C06M7/IJK5N4YQBAG8K
It takes a couple of minutes for the invalidation requests to be
processed on the Amazon side. Can check the status with s3cmd cfinvalinfo:
~$ s3cmd *cfinvalinfo* cf://E9RB4B71C06M7/IJK5N4YQBAG8K
URI: cf://E9RB4B71C06M7/IJK5N4YQBAG8K
Status: InProgress
Created: 2011-04-11T03:05:55.270Z
Nr of paths: 4
Reference: E9RB4B71C06M7.20110411150554.2741
As there can be up to 3 invalidation requests running in parallel you
can list them all (using either s3://bucket or cf://dist-id identifier):
~$ s3cmd cfinvalinfo s3://public.example.com
URI: cf://E9RB4B71C06M7/IJK5N4YQBAG8K
Status: *InProgress*
Created: 2011-04-11T03:05:55.270Z
Nr of paths: 4
Reference: E9RB4B71C06M7.20110411150554.2741
URI: cf://E9RB4B71C06M7/I1TA7E8XR7J70P
Status: *Completed*
Created: 2011-04-08T14:59:02.714Z
Nr of paths: 20
Reference: E9RB4B71C06M7.20110409025901.2531
[...]
There is also a couple of limitations:
- invalidation is only available for sync, there is no dedicated /s3cmd
cfinval/ command that would invalidate without uploading. Yet.
- the maximum number of paths invalidated in one run is 999 (that's a
single request size limit in Amazon). If more than 999 paths are to be
invalidated the list is saved in a file and the user will have to deal
with that in some other way, possibly using the future /s3cmd cfinval/
command.
Download the package from this link:
http://sourceforge.net/projects/s3tools/files/testing/s3cmd-1.1.0-beta1.tar.gz/download
For testing it is /not/ necessary to install s3cmd into the system.
Simply unpack it and run from that directory. For instance instead of
invoking the installed s3cmd run /tmp/s3cmd-1.1.0-beta1/s3cmd (if that's
where you unpacked the tarball).
S3cmd 1.1.0-beta1 should work as expected and there should be no
regressions against s3cmd 1.0.0 but please test it and let me know.
Enjoy!
Michal
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
S3tools-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s3tools-general
