Product logo
DocsBlogPricing

@turbot/aws-emr

Version
5.6.0
Released On
May 02, 2022
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.6.0 (2022-05-02)

Control Types

Added

  • AWS > EMR > Block Public Access Configuration > Settings

Policy Types

Added

  • AWS > EMR > Block Public Access Configuration > Settings
  • AWS > EMR > Block Public Access Configuration > Settings > Permitted Public Security Group Rule Ranges

Action Types

Added

  • AWS > EMR > Block Public Access Configuration > Update Settings

5.5.0 (2022-04-18)

Resource Types

Added

  • AWS > EMR > Block Public Access Configuration

Control Types

Added

  • AWS > EMR > Block Public Access Configuration > CMDB
  • AWS > EMR > Block Public Access Configuration > Discovery

Policy Types

Added

  • AWS > EMR > Block Public Access Configuration > CMDB
  • AWS > EMR > Block Public Access Configuration > Regions

Action Types

Added

  • AWS > EMR > Block Public Access Configuration > Router

5.4.0 (2022-02-04)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • We've improved the process of deleting resources from Turbot if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Turbot's IAM role while deleting resources from Turbot. This will allow the CMDB controls to process resource deletions from Turbot more reliably than before.
  • The AWS > EMR > Cluster > Tags control would go into an error state due to an incorrect reference to TerminationProtected resource attribute in the GraphQL input query. This is now fixed.

Policy Types

Added

  • AWS > EMR > Cluster > Approved > Custom
  • AWS > EMR > Security Configuration > Approved > Custom

5.3.0 (2022-01-17)

What's new?

  • AWS/EMR/Admin and AWS/EMR/Metadata now include permissions for Block Public Access Configuration, Editor, Repository, Persistent App UI and Studio.
  • 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.
  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in 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 (2020-10-12)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.

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.
  • The OutpostArn property was not available for use in GraphQL queries. This issue has now been fixed.

5.1.4 (2020-08-17)

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.1.3 (2020-07-03)

Bug fixes

  • Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Turbot is great", Value: "true"}], we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.

5.1.2 (2020-05-29)

What's new?

  • Updated AWS > EMR > Regions policy default value to now include af-south-1, eu-south-1.

Bug fixes

  • Removed AWS > EMR > Security Configuration > Router control and re-added it as an action. It was previously released incorrectly as a control and should not appear in the UI.

Control Types

Removed

  • AWS > EMR > Security Configuration > Router

Action Types

Added

  • AWS > EMR > Security Configuration > Router