Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

S3Sink - should support instance-profile for bucket access #78

Open
eytan-avisror opened this issue Aug 14, 2019 · 2 comments
Open

S3Sink - should support instance-profile for bucket access #78

eytan-avisror opened this issue Aug 14, 2019 · 2 comments

Comments

@eytan-avisror
Copy link

Currently the s3sink interface panics if s3SinkAccessKeyID / s3SinkSecretAccessKey are not provided.

	case "s3sink":
		accessKeyID := viper.GetString("s3SinkAccessKeyID")
		if accessKeyID == "" {
			panic("s3 sink specified but s3SinkAccessKeyID not specified")
		}

		secretAccessKey := viper.GetString("s3SinkSecretAccessKey")
		if secretAccessKey == "" {
			panic("s3 sink specified but s3SinkSecretAccessKey not specified")

Ignoring the fact that this should probably use a secret vs. a configmap to store this secret, for my use-case I need to use an instance profile to access the bucket.

This will not work with current code as it simply panics.

Suggested change:

  • if key/secret not provided, check if instance-profile is attached
  • if instance-profile is attached and no creds provided, use the instance-profile to try and access the bucket
  • if both not provided (no instance-profile attached) - panic.

Happy to send a PR for this if you are open to having eventrouter support instance-profile for access.

Is this project still active? no release here for the last year+

@jia2
Copy link

jia2 commented Sep 11, 2019

s3sink support for instance-profile is appreciated.

@vigith
Copy link
Contributor

vigith commented Sep 13, 2019

I will try to include this in #82

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants