Andrew Gargan

## Overview When `taskcat -d package` (note the debug mode) lambda code using a `Dockerfile` if the execution goes wrong the logs from the container are truncated. This doesn't allow...

Currently builds give very little details when packaging lambdas by Dockerfile. I would like to see container logs in the taskcat output for more complex packaging Making the following changes...

**Describe the bug** Specifying a long stack name causes and error while creating the SQSMetering Queue **To Reproduce** Steps to reproduce the behavior: 1. Launch the solution with a long...

Fixing example in additional info

Documentation required for publication.

1

Before publication we need the documentation to be completed under `docs/partner_editable`.

Architecture Diagram in PPTX required.

1

An architecture diagram of the resources the solution with deploy is required in PPTX format using up to date AWS Icons as per: https://aws.amazon.com/architecture/icons/ The should be included here `docs/images/architecture.pptx`

We need to confirm what we are putting in place for outbound mail via SES. DKIM, SPF etc.

The input parameters for the SQS queue names etc should be possible for us to infer from the product code. We need to confirm if the account to which these...

Currently the stack has no outputs, meaning customers will need to dig into the nested stacks to find relevant info. Let's work to surface these values to make the customer...

This line causes the name to go over 80 characters which is invalid. https://github.com/aws-samples/aws-marketplace-serverless-saas-integration/blob/master/template.yaml#L384 As per: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-sqs-queues.html#aws-sqs-queue-name we should allow CloudFormation to generate the name for us.