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

Running local Kinesis still requires AWS access #31

Open
cjbottaro opened this issue Sep 7, 2019 · 0 comments
Open

Running local Kinesis still requires AWS access #31

cjbottaro opened this issue Sep 7, 2019 · 0 comments

Comments

@cjbottaro
Copy link

Even when using local Kinesis (Kinesalite) and the --kinesisendpoint option, pg2k4j still requires I put in AWS creds and it makes AWS API calls:

[kpl-daemon-0003] WARN com.amazonaws.services.kinesis.producer.LogInputStreamReader - [2019-09-07 18:32:42.777668] [0x000005b2][0x00007fe2cb436700] [warning] [AWS Log: WARN](AWSErrorMarshaller)Encountered AWSError
AccessDenied
User: arn:aws:iam::xxxxxxxxxxx:user/ci is not authorized to perform: cloudwatch:PutMetricData:

If using this --kinesisendpoint option, shouldn't it assume that the user is developing locally and thus not require AWS creds or try to use the AWS API at all?

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

No branches or pull requests

1 participant