Important
This release fixes an issue with the deployment of AWS Budgets, and only affects customers that have deployed an AWS Budget, with multiple enabled regions defined in their global-config.yaml, and are using v1.2.1.
In v1.2.1, the definition of AWS Budgets was not limited to only the home region, which caused the object to be deployed to multiple regions. In this release, logic has been added to ensure that AWS Budgets are only added in the defined home region.
These steps are required for if you currently have an AWS Budget deployed through LZA release/v1.2.1:
- In the AWS console, delete the existing budget within management or any other account where a budget was deployed.
- Go into the LZA config repository and remove (or comment out) budgets from the config.
- Update to this version (release/v1.2.2) by updating the branch name for your InstallerStack through the AWS CloudFormation console.
- Release the changes to the LZA pipeline within the AWS console once to ensure that the current budget is removed from the account.
- Once the pipeline has completed, add the budgets back into the global-config.yaml file and release the CodePipeline for LZA
Changed
- fix(app) wrap execution in try/catch to surface errors
- fix(budgets) budgets causing operations stack to fail
We highly recommend that you keep your environments up to date by upgrading to the latest version. To upgrade your environments to this version, use the CloudFormation console to update your AWSAccelerator-Installer stack using the latest installer template and ensure that that you set Branch Name to the latest version (release/v1.2.2 for this release)