@turbot/aws-amplify
Recommended Version
Version
5.3.0
Released On
Jul 09, 2021
Depends On
Resource Types
Control Types
- AWS > Amplify > App > Active
- AWS > Amplify > App > Approved
- AWS > Amplify > App > CMDB
- AWS > Amplify > App > Discovery
- AWS > Amplify > App > Tags
- AWS > Amplify > App > Usage
Policy Types
- AWS > Amplify > API Enabled
- AWS > Amplify > App > Active
- AWS > Amplify > App > Active > Age
- AWS > Amplify > App > Active > Last Modified
- AWS > Amplify > App > Approved
- AWS > Amplify > App > Approved > Regions
- AWS > Amplify > App > Approved > Usage
- AWS > Amplify > App > CMDB
- AWS > Amplify > App > Regions
- AWS > Amplify > App > Tags
- AWS > Amplify > App > Tags > Template
- AWS > Amplify > App > Usage
- AWS > Amplify > App > Usage > Limit
- AWS > Amplify > Approved Regions [Default]
- AWS > Amplify > Enabled
- AWS > Amplify > Permissions
- AWS > Amplify > Permissions > Levels
- AWS > Amplify > Permissions > Levels > Modifiers
- AWS > Amplify > Permissions > Lockdown
- AWS > Amplify > Permissions > Lockdown > API Boundary
- AWS > Amplify > Regions
- AWS > Amplify > Tags Template [Default]
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-amplify
Release Notes
5.3.0 (2021-07-09)
What's new?
- We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.
5.2.0 (2021-06-24)
What's new?
AWS/Amplify/Admin
now includes backend environment permissions.
5.1.2 (2020-12-14)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when intbd
andskipped
, resulting in faster and lighter control runs.
5.1.1 (2020-09-18)
Bug fixes
- We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.
5.1.0 (2020-09-01)
What's new?
- Discovery controls now have their own control category,
CMDB > Discovery
, to allow for easier filtering separately from other CMDB controls. - We've renamed the service's default regions policy from
Regions [Default]
toRegions
to be consistent with our other regions policies.
5.0.5 (2020-08-11)
Bug fixes
- In various Active controls, we were outputting log messages that did not properly show how many days were left until we'd delete the inactive resources (we were still deleting them after the correct number of days). These log messages have been fixed and now contain the correct number of days.
5.0.4 (2020-07-07)
Bug fixes
- Updated various resource configurations to provide better compatibility with AWS China regions.
5.0.3 (2020-06-11)
What's new?
- All resource Router actions now run even if Turbot is outside of its allowed change window. This allows Turbot to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Turbot's ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.
5.0.2 (2020-05-15)
Bug fixes
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.