[
https://issues.apache.org/jira/browse/FLUME-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved FLUME-1691.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: v0.9.5
Won't fix. 0.X branch not maintained anymore
> Allow use of EC2 roles with S3 sink
> -----------------------------------
>
> Key: FLUME-1691
> URL: https://issues.apache.org/jira/browse/FLUME-1691
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v0.9.4
> Reporter: Steve Stogner
> Priority: Minor
> Fix For: v0.9.5
>
>
> If you assign an IAM role to an EC2 instance, then AWS exposes role
> credentials through the metadata interface. These credentials are temporary
> credentials that AWS rolls periodically. When making calls to AWS with
> temporary credentials, you have to use a token in addition to the access ID
> and secret key. Flume would impress if it would default to the EC2 role
> credentials when using an S3 sink with no credentials configuration required.
> Flume would either refresh the credentials from the metadata with every call
> to S3 or when it detects that the credentials have expired. Users could
> still override the use of role credentials with user credentials via the
> current configuration method (fs.s3.awsAccessKeyId, fs.s3.awsSecretAccessKey,
> fs.s3n.awsAccessKeyId, fs.s3n.awsSecretAccessKey).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
