[
https://issues.apache.org/jira/browse/FLUME-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940711#comment-14940711
]
Otis Gospodnetic commented on FLUME-2437:
-----------------------------------------
+1 for getting this in.
I see [~jrufus] mentioned the Flume needs have have this:
{noformat}
agent1.sources.s3src.bucketName = <bucket name to be processed/monitored>
agent1.sources.s3src.accessKey = <S3 access key>
agent1.sources.s3src.secretKey = <S3 secret key>
{noformat}
A few things [~prog] mentioned:
{quote}
* fetch data from multiple S3 buckets
* dynamically (i.e. without editing/writing config files stored on disk) add
new S3 buckets from which data should be fetch
* dynamically (i.e. without editing/writing config files stored on disk) stop
fetching data from some S3 buckets
{quote}
Imagine a multi-user system where each user has data in their own bucket and,
of course, they own keys. Having a single, fixed bucket and keys in a config
file won't work for that use case. Is there a way to create S3Source and *pass
in* the bucket, access key, and secret key?
> S3 Source
> ---------
>
> Key: FLUME-2437
> URL: https://issues.apache.org/jira/browse/FLUME-2437
> Project: Flume
> Issue Type: New Feature
> Reporter: Jonathan Natkins
> Assignee: Johny Rufus
> Attachments: FLUME-2437-2.patch, FLUME-2437.patch
>
>
> There have been multiple requests on the mailing list for an S3 source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
