account event updates, cfct template update

Author: andywick-aws

CHANGELOG.md

@@ -3,6 +3,7 @@
 ## Table of Contents<!-- omit in toc -->
 
 - [Introduction](#introduction)
+- [2022-05-15](#2022-05-15)
 - [2022-04-25](#2022-04-25)
 - [2022-04-14](#2022-04-14)
 - [2022-04-10](#2022-04-10)
@@ -27,6 +28,28 @@ All notable changes to this project will be documented in this file.
 
 ---
 
+## 2022-05-15
+
+### Added<!-- omit in toc -->
+
+- Added customizations-for-aws-control-tower.template to align with the latest [user guide](https://docs.aws.amazon.com/controltower/latest/userguide/cfct-template.html) instructions.
+
+### Changed<!-- omit in toc -->
+
+- [Common CFCT Setup](aws_sra_examples/solutions/common/common_cfct_setup) solution updates:
+  - Replaced the S3 template link with the latest template from the GitHub repository.
+- [EC2 Default EBS Encryption](aws_sra_examples/solutions/ec2/ec2_default_ebs_encryption) solution updates:
+  - Added account and organization event support.
+  - Added SNS fanout for configuring accounts to replace multi-threading.
+  - Added Lambda environment variables to replace SSM parameter for configuration.
+- [S3 Block Account Public Access](aws_sra_examples/solutions/s3_block_account_public_access) solution updates:
+  - Added account and organization event support.
+  - Added SNS fanout for configuring accounts to replace multi-threading.
+  - Added Lambda environment variables to replace SSM parameter for configuration.
+- [Security Hub Organization](aws_sra_examples/solutions/securityhub/securityhub_org) updates:
+  - Added account and organization event support.
+- Updated the staging script to include \*.template files.
+
 ## 2022-04-25
 
 ### Added<!-- omit in toc -->

CONTRIBUTING.md

@@ -5,7 +5,6 @@
 - [Introduction](#introduction)
 - [Reporting Bugs/Feature Requests](#reporting-bugsfeature-requests)
 - [Contributing via Pull Requests](#contributing-via-pull-requests)
-- [Finding contributions to work on](#finding-contributions-to-work-on)
 - [Code of Conduct](#code-of-conduct)
 - [Security issue notifications](#security-issue-notifications)
 - [Licensing](#licensing)
@@ -29,27 +28,11 @@ When filing an issue, please check existing open, or recently closed, issues to
 
 ## Contributing via Pull Requests
 
-Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+At this time, we are not accepting contributions via Pull Requests.
 
-1. You are working against the latest source on the _master_ branch.
-2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
-3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+If you have code to contribute, please fork the repository and create an issue with a link to your forked repository. Our team will review your code and contact you with insructions for submitting your code.
 
-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.
-
-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.
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/).
 
 ## Code of Conduct
 

GENERAL-CONTRIBUTING-GUIDANCE.md

@@ -36,8 +36,7 @@ factory, the solution ensures that all resources attached to the account's OUs w
 
 - The [Customizations for AWS Control Tower](https://aws.amazon.com/solutions/implementations/customizations-for-aws-control-tower/) (CFCT) solution to support deploying customizations easily to your AWS Control Tower landing zone.
 - Defaults updated per SRA recommendations:
-  <!-- markdownlint-disable MD034 -->
-  - `Amazon S3 URL` = https://s3.amazonaws.com/solutions-reference/customizations-for-aws-control-tower/latest/custom-control-tower-initiation.template
+  - Latest template downloaded from [GitHub - customizations-for-aws-control-tower.template](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/customizations-for-aws-control-tower.template)
   - `AWS CodePipeline Source` = AWS CodeCommit
   - `Failure Tolerance Percentage` = 0