Limit Monitor on AWS
AWS Limit Monitor

Appendix A: Troubleshooting

The AWS Limit Monitor logs error, warning, informational, and debugging messages for the solution’s AWS Lambda functions. To choose the type of messages to log, find the applicable function in the Lambda console and change the LOG_LEVEL environment variable to the applicable type of message.

Level Description
ERROR Logs will include information on anything that causes an operation to fail.
WARNING Logs will include information on anything that can potentially cause inconsistencies in the function but might not necessarily cause the operation to fail. Logs will also include ERROR messages.
INFO Logs will include high-level information about how the function is operating. Logs will also include ERROR and WARN messages.
DEBUG Logs will include information that might be helpful when debugging a problem with the function. Logs will also include ERROR, WARNING, and INFO messages.

Common Errors

Amazon CloudWatch Events Bus Permissions Error

If during spoke stack deployment, you received a CREATE_FAILED message for the TAWarnRule and/or the TASErrorRule, verify that the Amazon CloudWatch Events Bus in the primary account allows the spoke account to send events to the primary account.

Resolution

Update the primary stack with the secondary account ID or complete the following task:

  1. In the primary account, navigate to the Amazon CloudWatch console.

  2. In the navigation pane, select Event Buses.

  3. Select Add Permissions.

  4. For Principal, enter the applicable secondary account ID.

  5. Select the Everybody(*) checkbox.

  6. Choose Add.

Amazon DynamoDB Is Not Showing Events

If the solution’s Amazon DynamoDB table is not updating or there are no messages in the solution’s Amazon Simple Queue Service (Amazon SQS) queue, verify that the account IDs you entered in the solution’s Account List parameter are comma-separated and use double quotation marks.

Resolution

Complete the following task:

  1. In the primary account, navigate to the Amazon CloudWatch console.

  2. In the navigation pane, select Rules.

  3. Select the TASNSRule and verify the account parameter shows a comma-separated value inside double quotation marks.

  4. Select the TASQSRule and verify the account parameter shows a comma-separated value inside double quotation marks.

  5. Select the TASlackRule and verify the account parameter shows a comma-separated value inside double quotation marks.

  6. If the account parameter in the TASNSRule, TASQSRule, or TASlackRule rules are not formatted correctly, update the stack with the correct format.

  7. Choose Add.

Slack Notifications Are Not Being Received

If you do not receive Slack notifications for WARN or ERROR events, check the Amazon CloudWatch logs for an error message.

  1. In the primary account, navigate to the Amazon CloudWatch console.

  2. In the navigation pane, select Logs.

  3. Select the /aws/lambda/<stackname>-SlackNotifier-<randomstring> Log Group.

  4. Select the top (most recent) Log Stream.

  5. Look for the following error.

    
                AWS Limit Monitor Slack Notification Error

    Figure 3: Slack notification error

Resolution

Complete the following task:

  1. In the primary account, navigate to the AWS Systems Manager console.

  2. In the navigation pane under Shared Resources, select Parameter Store.

  3. Select the SlackChannel parameter and verify that the parameter shows the correct value.

  4. Select the SlackHookURL parameter and verify that the parameter shows the correct value.

Email Notifications Are Not Being Received

If you do not receive email notifications, check to make sure that you have subscribed to the Amazon SNS topic.

  1. In the primary account, navigate to the Amazon SNS console.

  2. In the navigation pane, select Topics.

  3. Select the <stackname>-SNSTopic-<randomstring> Amazon Resource Name (ARN) value.

  4. Verify that the Subscription ID shows an ARN value.

Resolution

If the Subscription ID field shows PendingConfirmation, complete the following task:

  1. Select the checkbox next to PendingConfirmation.

  2. Under Subscriptions, select Request Confirmations.

  3. Navigate to the applicable email inbox.

  4. In the subscription notification email, select the SubscribeURL link.

  5. In the Amazon SNS console, refresh and verify that the Subscription ID has an ARN value.

On this page: