Merge pull request #3 from aws-solutions/release/v2.0.0

v2.0.0 release

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,52 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Please complete the following information about the solution:**
+- [ ] Version: [e.g. v1.0.0]
+
+To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "_(SO0193) - Amazon Marketing Cloud Insights. Version **v1.0.0**_". If you have not yet installed the stack, or are unable to install due to a problem, you can find the version and solution ID in the template with a text editor. Open the .template file and search for `SOLUTION_VERSION` in the content. You will find several matches and they will all be the same value:
+
+```json
+    "Environment": {
+      "Variables": {
+        "SOLUTION_ID": "SO0193",
+        "SOLUTION_VERSION": "v1.0.0"
+      }
+    },
+```
+
+This information is also provided in `source/infrastructure/cdk.json`:
+
+```json
+    "SOLUTION_ID": "SO0193",
+    "SOLUTION_VERSION": "v1.0.0",
+```
+
+
+
+- [ ] Region: [e.g. us-east-1]
+- [ ] Was the solution modified from the version published on this repository?
+- [ ] If the answer to the previous question was yes, are the changes available on GitHub?
+- [ ] Have you checked your [service quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) for the sevices this solution uses?
+- [ ] Were there any errors in the CloudWatch Logs?
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem (please **DO NOT include sensitive information**).
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this solution
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the feature you'd like**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,5 @@
+*Issue #, if available:*
+
+*Description of changes:*
+
+By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

.gitignore

@@ -0,0 +1,37 @@
+*.swp
+package-lock.json
+__pycache__
+.pytest_cache
+.env
+.*venv*
+*.egg-info
+.DS_Store
+/.DS_Store 
+.c9/*
+.vscode
+**/.idea/*
+
+# CDK asset staging directory
+cdk.context.json
+.cdk.staging
+cdk.out
+ddk.out/*
+.ddk.out/*
+.out
+*.zip
+
+global-s3-assets
+regional-s3-assets
+build-s3-assets
+
+# python build files
+source/cdk_solution_helper_py/helpers_common/build/*
+source/cdk_solution_helper_py/helpers_cdk/build/*
+
+# coverage
+.coverage
+*coverage-reports*
+
+# local sonarqube
+.scannerwork/*
+

CHANGELOG.md

@@ -0,0 +1,42 @@
+# Change Log
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [2.0.0] - 2023-10-05
+
+### Added
+
+- Promote to AWS Solutions.
+- Integrate Microservice 2.0.
+- Add Cross-Account and Cross-Region functionality.
+- Update cross-account template synthesis and deployment process.
+- Enhancements for multi-instance customers.
+- Add CloudWatch alarms to DLQs when message count > 0.
+- Add CloudWatch alarms to Lambdas for error and throttle metrics.
+- Enable CloudTrail for S3 and Lambda data events and logs for Step Functions
+- User's ability to optionally deploy either microservices or data lake.
+- User's ability to add other data source to the data lake.
+- Remove CodeBuild infrastructure and usage of AWS DDK.
+- Add functional and unit tests.
+- Add AppRegistry support.
+- Improve codebase to meet Solution quality bar.
+- Reforge and simplify six stacks to one stack. 
+- Allow multiple stack deployment in one region. 
+- Update folder structure and add files for Solutions layout.
+- Incorporate CDK solution helper and update build output.
+- Update runtimes, layers, timeouts, architectures, dependencies, package hierarchy, and copyrights.
+- Reforge AWS Data Wrangler layer build.
+- Update DynamoDB tables to on-demand capacity.
+- Update scripts for uninstalling solution.
+- Add, update and fix IAM role and policy.
+- Restrict KMS permissions. 
+- Bug fix and enhancements
+
+## [1.1.3] - 2023-06-01
+
+### Added
+
+- Final version before promotion to AWS Solutions
+

CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
 opensource-codeofconduct@amazon.com with any additional questions or comments.

CONTRIBUTING.md

@@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+When filing an issue, please check [existing open](https://github.com/aws-solutions/amazon-marketing-cloud-insights-on-aws/issues), or [recently closed](https://github.com/aws-solutions/amazon-marketing-cloud-insights-on-aws/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
@@ -31,17 +31,18 @@ To send us a pull request, please:
 
 1. Fork the repository.
 2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
-3. Ensure local tests pass.
-4. Commit to your fork using clear commit messages.
-5. Send us a pull request, answering any default questions in the pull request interface.
-6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+3. Ensure all build processes execute successfully (see README.md for additional guidance).
+4. Ensure all unit, integration, and/or snapshot tests pass, as applicable.
+5. Commit to your fork using clear commit messages.
+6. Send us a pull request, answering any default questions in the pull request interface.
+7. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
 
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/amazon-marketing-cloud-insights-on-aws/labels/help%20wanted) issues is a great place to start.
 
 
 ## Code of Conduct
@@ -51,9 +52,11 @@ opensource-codeofconduct@amazon.com with any additional questions or comments.
 
 
 ## Security issue notifications
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public GitHub issue.
 
 
 ## Licensing
 
-See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](https://github.com/aws-solutions/amazon-marketing-cloud-insights-on-aws/blob/main/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+
+We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.