When performing cdk deploy the .ts handler file is missing.

Solution:
Revert to official cdk-lib lambda function construct to simplify build process

In README example

 },
      emails: [
        `[email protected]`,
        `[email protected]`,
      ] <<<<<<<<<<<<<<<<<<< ADD COMMA
      slackProps: {
        slackToken: '...',
        slackChannel: '...',
      },
    });
  }

• Update Medium Profile
• Create Medium Blog Post
• Post on LinkedIn
• Post on Daily Dev

Would it be possible to allow provisioning of DLQ properties similar to the main queue properties (or reuse props from the main queue)?

A simple use case: enforceSSL
This can be set for the monitored queue via the QueueProps, but is not passed on to the DLQ. Only option at the moment is to create a DLQ outside of the construct and provide that, which sort of defeats its purpose / usefulness.

Although the CDK defaults to false, from a security perspective enforcing SSL should perhaps even be the default.

Our use case can be found here.

Following from the use case described in #89 we'd like to enforceSSL on SNS topics.
We can't see a way to do this with the current code.

Clean up main CDK construct by adding seperate methods for each step.

This should simplify maintenance.

cdk-nag is very useful when testing constructs against AWS best practises and externals standards.
Standards compliance and security best practises are crucial for our production workloads.

Issues #89 and #90 were flagged by cdk-nag as violating the AWS solutions rules.

If the Slack CLI could be integrated then bots could be created on behalf of the package user, thus skipping the setup process before a Slack notification can be sent

Related to #90

An announcement has been made by AWS that AWS Lambda can be invoked directly without using SNS.

https://aws.amazon.com/about-aws/whats-new/2023/12/amazon-cloudwatch-alarms-lambda-change-action/

This could simplify the infrastructure considerably and is possibly a very good fit for this project

Improve tests by testing resource properties using template.hasResourceProperties

test('SQS Queues created', () => {
    template.resourceCountIs('AWS::SQS::Queue', 2);
    template.hasResourceProperties('AWS::SQS::Queue', {
      QueueName: 'TestQueueName',
      RedrivePolicy: {
        deadLetterTargetArn: Match.anyValue(),
        maxReceiveCount: 3,
      },
    });

    template.hasResourceProperties('AWS::SQS::Queue', {
      QueueName: 'TestQueueName-dlq',
    });
  });

  test('SQS Queue configured with SSL', () => {
    template.resourceCountIs('AWS::SQS::QueuePolicy', 2);
    template.hasResourceProperties('AWS::SQS::QueuePolicy', {
      PolicyDocument: Match.objectLike({
        Statement: [
          {
            Action: 'sqs:*',
            Effect: 'Deny',
            Condition: {
              Bool: {
                'aws:SecureTransport': 'false',
              },
            },
          },
        ],
      }),
    });
  });

Source: https://github.com/umccr/orcabus/blob/f589d49fdbc660440cba2a29534922ce8eeeccdc/test/stateful/icaEventPipeConstruct.test.ts

Add Integration tests to match the aws-cdk standard:

https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md

Spelling:
"Be sure to check you Spam folder as well."

Be more accurate in the description:
"An AWS CDK construct to wrap AWS Simple-Queue Service (SQS) Dead-Letter Queues with a CloudWatch alarm to notify if the number of messages cross a certain threshold."

Improve description:
"A Bot user token..."

Investigate functionality for users to somehow add code to the execution of the Lambda Function to allow for maximum customisation.

AWS Chatbot natively supports integration with Slack without the need for a custom Lambda.

For an idea of how that may work, see here.