From: Jeff Darcy <jdarcy@redhat.com>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: Amazon bucket-policy API extensions
Date: Thu, 08 Jul 2010 07:17:28 -0400 [thread overview]
Message-ID: <4C35B3C8.5070203@redhat.com> (raw)
Yet another thing for the to-do list, I guess.
-------- Original Message --------
Subject: Announcing Amazon S3 Bucket Policies
Date: Thu, 8 Jul 2010 08:43:40 +0000 (UTC)
From: Amazon Web Services <no-reply-aws@amazon.com>
To: jeff@pl.atyp.us <jeff@pl.atyp.us>
<http://aws.amazon.com/about-aws/whats-new/2010/07/06/aws-management-console-adds-support-for-amazon-s3-2/>
We are pleased to announce beta support for Amazon S3 bucket policies,
which gives customers the ability to create conditional rules for
managing access to their buckets and objects. Amazon S3 customers now
have the following options for restricting access to their resources:
* Authenticated requests: Allow or deny access based on AWS account
* Query string authentication with expiring URLs: Allow temporary
access to resources
* Request-based restrictions: Allow or deny access based on request
attributes, such as HTTP referrer and IP address
With bucket policies, customers can also now define security rules that
apply to more than one object, including all objects or a subset of
objects within a bucket. This makes updating and managing permissions
easier.
There are no additional Amazon S3 fees when using bucket policies. For
more information, please refer to the Amazon S3 FAQs and Developer Guide
or attend the Introduction to Bucket Policies Webcast on July 13.
next reply other threads:[~2010-07-08 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 11:17 Jeff Darcy [this message]
2010-07-09 21:45 ` Amazon bucket-policy API extensions Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C35B3C8.5070203@redhat.com \
--to=jdarcy@redhat.com \
--cc=hail-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox