camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (Work started) (JIRA) <>
Subject [jira] [Work started] (CAMEL-4435) Allow specifiying ACL on S3 producer
Date Sat, 19 Nov 2011 00:08:52 GMT


Work on CAMEL-4435 started by Christian Müller.

> Allow specifiying ACL on S3 producer
> ------------------------------------
>                 Key: CAMEL-4435
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Brendan Long
>            Assignee: Christian Müller
>            Priority: Minor
> With the S3 component, there's currently no way to specify ACLs on either the component
or message level.
> I'm proposing:
> 1. Add a URL parameter, "acl", which can be either:
>   * A canned ACL (private, public-read, public-read-write, authenticated-read). Ex: acl=private
>   * A reference to an ACL bean (
> 2. Add CamelAwsS3ACL header, which can contain a string ("private", "public-read", etc.),
a CannedAccessControlList object, or an AccessControlList object
> I'm working on a patch for this, but I want to make sure the way I'm going about it will
be accepted before getting too far.
> Some questions:
>   * Is "acl" a good URL parameter? Should it be "access"? Should ACL references be separate
>   * Should we accept a string for the canned ACL when it's a header, or just expect a
CannedAccessControlList object?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message