You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
Does the DynamoDB need anything additional setup for this to work or just a basic table?
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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:
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.
The text was updated successfully, but these errors were encountered: