Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scala Stream Collector: update AWS credentials to support iam/env/default not cpf #1518

Closed
alexanderdean opened this issue Mar 17, 2015 · 3 comments

Comments

@alexanderdean
Copy link
Member

No description provided.

@alexanderdean alexanderdean added this to the Kinesis #7 milestone Mar 17, 2015
@alexanderdean alexanderdean changed the title Scala Stream Collector: update creds options to be iam/env/default not cpf Scala Stream Collector: update AWS credentials to support iam/env/default not cpf Mar 17, 2015
@alexanderdean alexanderdean assigned jbeemster and unassigned fblundun Jul 16, 2015
@fblundun fblundun modified the milestones: Kinesis #7, Kinesis #8 Sep 7, 2015
@fblundun fblundun assigned fblundun and unassigned jbeemster Sep 8, 2015
@fblundun
Copy link
Contributor

@alexanderdean - am I right in thinking that this means completely removing support for reading creds from a file on the classpath as described here?

@alexanderdean
Copy link
Member Author

@fblundun - this is an old ticket, but I believe the intent is to harmonize the SSC with the ES Sink.

SSC options:

      # The following are used to authenticate for the Amazon Kinesis sink.
      #
      # If both are set to 'cpf', a properties file on the classpath is used.
      # http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/ClasspathPropertiesFileCredentialsProvider.html
      #
      # If both are set to 'iam', use AWS IAM Roles to provision credentials.
      #
      # If both are set to 'env', use environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

ES Sink options:

  # The following are used to authenticate for the Amazon Kinesis sink.
  #
  # If both are set to 'default', the default provider chain is used
  # (see http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html)
  #
  # If both are set to 'iam', use AWS IAM Roles to provision credentials.
  #
  # If both are set to 'env', use environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

Does that make sense?

@fblundun
Copy link
Contributor

That makes sense... I don't think there's any reason to keep supporting the classpath configuration option.

fblundun added a commit that referenced this issue Sep 30, 2015
fblundun added a commit that referenced this issue Sep 30, 2015
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 15, 2016
fblundun added a commit that referenced this issue Feb 29, 2016
fblundun added a commit that referenced this issue Feb 29, 2016
fblundun added a commit that referenced this issue Feb 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants