Introduction The bearse-feature-reporting system has been enhanced with a new feature that automatically handles large reports by partitioning them into smaller chunks when they exceed the AWS SNS message size limit.

The 0.11.11 release of Guardian introduces a new resource type and various bug fixes.

The 0.9.10 release of shelvery includes a refactor of the re-encryption process used to share snapshots between accounts.

The 0.1.0 release of the Start Stop feature introduces a massive code refactor to improve performance and reliability of the start-stop functionality with AWS infrastructure.

The 0.4.4 release of the Account Health feature introduces a new lambda to the monitoring stack which provides the capability to monitor all lambda functions deployed by bearse features.

With the 0.9.9 release of shelvery we’ve updated all lambda functions to utilise the Python 3.

The 0.4.1 release of the Account Health feature introduces a new lambda to the latest monitoring stack which provides the capability to monitor the washery tool.

The 0.3.9 release of the Account Health feature introduces a new stack to deploy called Monitoring with the purpose of providing an extra layer of monitoring on the developers tools deployed to enviroments.

With the existence of shared AMI’s and snapshots between accounts comes the rising issue of whats in use and what isn’t?

With the latest release of the Bearse API, we have added the ability to designate dependencies between stacks from other features.