Make template available in public S3 bucket, so customers can launch stack with one command with AWS CLI, instead of having to clone repo and packaging the template themselves.
Updates readme to reflect the new installation process
Fix for CloudWatch subscriptions when forwarder is provided - ensures that log group is created before subscription filter
Motivation
For the public beta, we released a version of the macro where the customer deployed through the AWS CLI. Customers also needed to set up a S3 bucket through the console or CLI prior to deploying, and the deployment itself involved two separate steps in the CLI on top of having to clone the repo. This solution follows the forwarder installation example, and allows customers to launch a CloudFormation stack with the macro resources with one command and without cloning the repository.
Overall jira ticket for macro
Testing Guidelines
Added ./tools/installation_test.sh (referenced forwarder solution) to test stack creation. Also launched a CloudFormation stack on the sandbox account in sa-east-1 using the launch stack button, and used macro in a test deployment with SAM.
What does this PR do?
Motivation
For the public beta, we released a version of the macro where the customer deployed through the AWS CLI. Customers also needed to set up a S3 bucket through the console or CLI prior to deploying, and the deployment itself involved two separate steps in the CLI on top of having to clone the repo. This solution follows the forwarder installation example, and allows customers to launch a CloudFormation stack with the macro resources with one command and without cloning the repository. Overall jira ticket for macro
Testing Guidelines
Added
./tools/installation_test.sh(referenced forwarder solution) to test stack creation. Also launched a CloudFormation stack on the sandbox account in sa-east-1 using the launch stack button, and used macro in a test deployment with SAM.Types of changes