...
AWS Cloud Log Collector icon is red and the Status is Not Running (message: The security token included in the request is invalid.)
| Expand | ||
|---|---|---|
| ||
When the AWS Cloud Log Collector icon is red and Status is Not Running (message: The security token included in the request is invalid), it is possible that the AWS Access Key ID is invalid or expired.   Go to AWS website and check if AWS Access Key ID is not yet expired and the value entered in the Snare Central configuration is correct.   If the value entered in the Snare Central Configuration is incorrect, you can simply edit it by clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
AWS Cloud Log Collector icon is red and the Status is Not Running (message: The request signature we calculated does not match the signature you provided.)
| Expand | ||
|---|---|---|
| ||
When the AWS Cloud Log Collector icon is red and Status is Not Running (message: The request signature we calculated does not match the signature you provided), it is possible that the AWS Secret Access Key is invalid or expired.   Go to AWS website and check if AWS Secret Access Key is not yet expired and is valid. If it is still valid and not yet expired, The value entered in the Snare Central Configuration maybe incorrect, you can simply edit it by clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
AWS Cloud Log Collector icon is red and the Status is Not Running (message: Stream <streamname> under account <account number> not found.)
...
| title | Possible Cause and Resolution |
|---|
...
Post "https://kinesis.us-east-11.amazonaws.com": dial tcp: lookup kinesis.us-east-11.amazonaws.com: no such host)
| Expand | ||
|---|---|---|
| ||
When the AWS Cloud Log Collector icon is red and Status is Not Running (message: Stream <streamname> under account <account number> not found), it is possible that the AWS Kinesis Data Stream Name you specified is not in the configured AWS Region Code or the AWS Kinesis Data Stream Name is wrong/Post "https://kinesis.us-east-11.amazonaws.com": dial tcp: lookup kinesis.us-east-11.amazonaws.com: no such host), it is possible that the AWS Region Code is invalid or does not exist.   Go to AWS website and check if the AWS Kinesis Data Stream Name exist in the AWS Region Code you specified.If it exist in the specified AWS Region Code then AWS Region Code exist/valid and the value entered in the Snare Central configuration is correct.  If the value entered in the Snare Central Configuration maybe incorrect. Double check the AWS Region Code entry and the AWS Kinesis Data Stream Name  Modify the wrong entry is incorrect, you can simply edit it by clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
AWS Cloud Log Collector icon is red and the Status is Not Running (Stream <streamname> under account <account number> not found.)
| Expand | ||
|---|---|---|
| ||
When the AWS Cloud Log Collector icon is red and Status is Not Running (Stream <streamname> under account <account number> not found), it is possible that the AWS Kinesis Data Stream Name you specified is not in the configured AWS Region Code or the AWS Kinesis Data Stream Name is wrong/does not exist.  Go to AWS website and check if the AWS Kinesis Data Stream Name exist in the AWS Region Code you specified. If it exist in the specified AWS Region Code then the value entered in the Snare Central Configuration maybe incorrect. Double check the AWS Region Code entry and the AWS Kinesis Data Stream Name  Modify the wrong entry by simply clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
AWS Cloud Log Collector takes too long to get new logs.
| Expand | ||
|---|---|---|
| ||
When AWS Cloud Log Collector takes too long to get new logs, it is possible that the Polling Interval(ms) is set too high.  Modify the entry to the desired interval for getting new logs in millisecond by simply clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
AWS Cloud Log Collector did not collect the old logs in AWS Kinesis Data Stream.
| Expand | ||
|---|---|---|
| ||
When AWS Cloud Log Collector is not collecting the old logs in AWS Kinesis Data Stream, it is possible that the Default Starting Position When Collecting Logs is configured to LATEST or that the old logs were already expired based from the set retention period in AWS Kinesis Data Stream. Go to AWS website and check if the old logs still exist in the AWS Kinesis Data Stream. If it still exist, then check the configured Default Starting Position When Collecting Logs if it is set to LATEST.  If it is LATEST, then change it to TRIM_HORIZON to start collecting from the oldest log in the AWS Kinesis Data Stream. You can simply edit it by clicking the Edit icon on the upper left corner. For more info, see: Step by Step Guide for Updating Snare Central - Amazon Web Services (AWS) Cloud Log Collection |
...