v2.8.1

Author: AWS

CHANGELOG.md

@@ -4,6 +4,16 @@ 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.8.1] - 2024-12-09
+- Add support for Resource Control Policies (RCPs). RCPs help you ensure that resources in your accounts stay within 
+  your organization’s access control guidelines. Learn more [here](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html).
+  - To set up a configuration package for Resource Control Polices, see
+    [CfCT customization guide](https://docs.aws.amazon.com/controltower/latest/userguide/cfct-customizations-dev-guide.html).
+- Add support for GitHub as a version control system (VCS) alternative for CfCT. ([#21](https://github.com/aws-solutions/aws-control-tower-customizations/issues/21))
+  - Learn more on how to set up CfCT using GitHub in the [Set up GitHub as the configuration source](https://docs.aws.amazon.com/controltower/latest/userguide/cfct-github-configuration-source.html) 
+    section of the user guide.
+- Add guidance on CodeCommit availability to new customers.
+
 ## [2.7.3] - 2024-09-13
 - Update dependencies
   - `PyYAML` 5.4.1 ([#154](https://github.com/aws-solutions/aws-control-tower-customizations/issues/154), [#169](https://github.com/aws-solutions/aws-control-tower-customizations/issues/169))
@@ -19,7 +29,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Upgrade botocore to version 1.31.17 and boto3 to version 1.28.17
 
 ## [2.7.1] - 2024-05-30
-* Update dependencies & runtimes ([#186]((https://github.com/aws-solutions/aws-control-tower-customizations/issues/186)), [#193]((https://github.com/aws-solutions/aws-control-tower-customizations/issues/193)))
+* Update dependencies & runtimes ([#186](https://github.com/aws-solutions/aws-control-tower-customizations/issues/186), [#193](https://github.com/aws-solutions/aws-control-tower-customizations/issues/193))
   * Building the solution from source now requires Python 3.11 or higher
   * Update Python Lambda runtimes to 3.11
   * Update Ruby version to 3.3
@@ -140,4 +150,4 @@ in the input account list has an existing stack instance.
 
 ## [1.0.0] - 2020-01-10
 ### Added
-- Initial public release
+- Initial public release

README.md

@@ -1,10 +1,10 @@
 ## Customizations for AWS Control Tower Solution
-The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment based on AWS best practices. Customers can easily add customizations to their AWS Control Tower landing zone using an AWS CloudFormation template and service control policies (SCPs). Customers can deploy their custom template and policies to both individual accounts and organizational units (OUs) within their organization. Customizations for AWS Control Tower integrates with AWS Control Tower lifecycle events to ensure that resource deployments stay in sync with the customer's landing zone. For example, when a new account is created using the AWS Control Tower account factory, the solution ensures that all resources attached to the account's OUs will be automatically deployed. Before deploying this solution, customers need to have an AWS Control Tower landing zone deployed in their account.
+The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment based on AWS best practices. Customers can easily add customizations to their AWS Control Tower landing zone using an AWS CloudFormation template, service control policies (SCPs), and resource control policies (RCPs). Customers can deploy their custom template and policies to both individual accounts and organizational units (OUs) within their organization. Customizations for AWS Control Tower integrates with AWS Control Tower lifecycle events to ensure that resource deployments stay in sync with the customer's landing zone. For example, when a new account is created using the AWS Control Tower account factory, the solution ensures that all resources attached to the account's OUs will be automatically deployed. Before deploying this solution, customers need to have an AWS Control Tower landing zone deployed in their account.
 
 ## Getting Started 
 To get started with Customizations for AWS Control Tower, please review the [documentation](https://docs.aws.amazon.com/controltower/latest/userguide/customize-landing-zone.html)
 
-## Running unit tests for customization 
+## Running unit tests for customization
 * Clone the repository, then make the desired code changes 
 * Next, run unit tests to make sure added customization passes the tests 
 
@@ -53,11 +53,10 @@ chmod +x ./deployment/build-s3-dist.sh
 * Get the link of the custom-control-tower-initiation.template loaded to your Amazon S3 bucket. 
 * Deploy the Customizations for AWS Control Tower solution to your account by launching a new AWS CloudFormation stack using the link of the custom-control-tower-initiation.template.
 
-
 ## Collection of operational metrics
 
 This solution collects anonymous operational metrics to help AWS improve the quality and features of the solution. For more information, including how to disable this capability, please see the [documentation here](https://docs.aws.amazon.com/controltower/latest/userguide/cfct-metrics.html).
 
 ## License
 
-See license [here](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/LICENSE.txt) 
+See license [here](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/LICENSE.txt) 

VERSION

@@ -1 +1 @@
-v2.7.3
+v2.8.1