Product logo
DocsBlogPricing

@turbot/aws-elasticsearch

The aws-elasticsearch mod contains resource, control and policy definitions for AWS Elasticsearch service.

Version
5.5.0
Released On
Nov 02, 2023
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.5.0 (2023-11-02)

What's new?

  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

  • Resource's metadata will now also include createdBy details in Turbot CMDB.

  • Users can now perform quick actions on resources to remediate cloud configuration issues or skip Turbot alarms for issues that they want to come back to later. To get started, click on the Actions button, which will reveal a dropdown menu with available actions, and select one. See Quick Actions for more information.

Policy Types

  • AWS > Elasticsearch > Domain > Approved > Custom

Action Types

  • AWS > Elasticsearch > Domain > Delete from AWS
  • AWS > Elasticsearch > Domain > Set Tags
  • AWS > Elasticsearch > Domain > Skip alarm for Active control
  • AWS > Elasticsearch > Domain > Skip alarm for Active control [90 days]
  • AWS > Elasticsearch > Domain > Skip alarm for Approved control
  • AWS > Elasticsearch > Domain > Skip alarm for Approved control [90 days]
  • AWS > Elasticsearch > Domain > Skip alarm for Tags control
  • AWS > Elasticsearch > Domain > Skip alarm for Tags control [90 days]

5.4.0 (2021-07-08)

What's new?

  • 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.
  • 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.3.2 (2021-02-10)

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Guardrails Precheck feature (not to be confused with TSA PreCheck). With Guardrails Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.3.1 (2020-10-16)

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.3.0 (2020-09-02)

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] to Regions to be consistent with our other regions policies.

5.2.0 (2020-08-14)

Policy Types

  • AWS > Elasticsearch > Domain > Approved > Encryption at Rest
  • AWS > Elasticsearch > Domain > Approved > Encryption at Rest > Customer Managed Key

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

Bug fixes

  • Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Guardrails 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.1 (2020-06-15)

Bug fixes

  • After creating a domain in the Government Cloud region, it gets upserted into the database with an incorrect AKA. This issue has now been fixed.

5.1.0 (2020-05-27)

What's new?

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

Bug fixes

  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.