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

Cross Account DynamoDB and Kinesis Settings #100

Closed
erickertzvfc opened this issue May 10, 2023 · 3 comments
Closed

Cross Account DynamoDB and Kinesis Settings #100

erickertzvfc opened this issue May 10, 2023 · 3 comments

Comments

@erickertzvfc
Copy link

I have Logstash running in an EC2 instance on a completely different AWS account than Kinesis and cannot get this input plugin working. There are also no errors in the logs to begin debugging, which I saw there was already a separate open issue for. I suspect there is an issue with connecting to the DynamoDB table as it will fail on error connecting to kinesis on startup (which i have worked out those issues).

A couple of questions with this setup:

  1. Does the DynamoDB table need to exist in the same account as the Kinesis stream? If not and it looks for the table in the same account as the Logstash instance, how would I provide separate credentials? I am already using profiles if needed.
  2. Does the DynamoDB need anything additional setup for this to work or just a basic table?
  3. Is there any way to have more verbose logging?

I do have a DynamoDB table setup and matching application_name and the AWS creds are dynamodb:* resource * for testing.

Thanks in advance for any help.

@erickertzvfc
Copy link
Author

i figured this out by using the role_arn setting. However, unfortuanetly I'm also dealing with an older version of logstash, 6.8 and it fails silently without creating the dynamodb table and in turn not pulling messages from kinesis. i tested with logstash 7.x and everything works as should.

@erickertzvfc
Copy link
Author

im going to close this as 6.8 is at end of life support and updating to 7.x seems fine.

@erickertzvfc
Copy link
Author

also, unrelated, but for anyone using this with opensearch as an output set ilm_enabled => false in your elasticsearch output to disable the 4xx calls to _xpack endpoints. so far, opensearch version of ilm still works with it disabled.

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