@turbot/aws-appflow
Recommended Version
Version
5.2.0
Released On
Apr 12, 2021
Depends On
Resource Types
Policy Types
- AWS > AppFlow > API Enabled
- AWS > AppFlow > Approved Regions [Default]
- AWS > AppFlow > Enabled
- AWS > AppFlow > Permissions
- AWS > AppFlow > Permissions > Levels
- AWS > AppFlow > Permissions > Levels > Modifiers
- AWS > AppFlow > Permissions > Lockdown
- AWS > AppFlow > Permissions > Lockdown > API Boundary
- AWS > AppFlow > Regions
- AWS > AppFlow > Tags Template [Default]
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-appflow
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-appflow
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-appflow
Release Notes
5.2.0 (2021-04-12)
What's new?
- Permissions for Appflow flows, connector profiles and connector entities will now also be managed under the
AWS > Appflow > Enabled
policy. To get started, set this policy toEnabled
.
5.1.0 (2020-09-03)
What's new?
- We've renamed the service's default regions policy from
Regions [Default]
toRegions
to be consistent with our other regions policies.
5.0.1 (2020-07-07)
Bug fixes
- Updated various resource configurations to provide better compatibility with AWS China regions.
5.0.0 (2020-05-05)
Resource Types
Added
- AWS > AppFlow
Policy Types
Added
- AWS > AppFlow > API Enabled
- AWS > AppFlow > Approved Regions [Default]
- AWS > AppFlow > Enabled
- AWS > AppFlow > Permissions
- AWS > AppFlow > Permissions > Levels
- AWS > AppFlow > Permissions > Levels > Modifiers
- AWS > AppFlow > Permissions > Lockdown
- AWS > AppFlow > Permissions > Lockdown > API Boundary
- AWS > AppFlow > Regions [Default]
- AWS > AppFlow > Tags Template [Default]
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-appflow
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-appflow
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-appflow