Product logo
DocsBlogPricing

@turbot/aws-secretsmanager

Version
5.7.0
Released On
Feb 27, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.7.0 (2024-02-27)

What's new?

  • The AWS > Secrets Manager > Secret > CMDB control would go into an error state if Guardrails did not have permissions to describe a secret. Users can now ignore such permission errors and allow the CMDB control to run its course to completion. To get started, set the AWS > Secrets Manager > Secret > CMDB policy to Enforce: Enabled but ignore permission errors.

5.6.0 (2023-11-03)

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 > Secrets Manager > Secret > Approved > Custom

Action Types

  • AWS > Secrets Manager > Secret > Delete from AWS
  • AWS > Secrets Manager > Secret > Set Tags
  • AWS > Secrets Manager > Secret > Skip alarm for Active control
  • AWS > Secrets Manager > Secret > Skip alarm for Active control [90 days]
  • AWS > Secrets Manager > Secret > Skip alarm for Approved control
  • AWS > Secrets Manager > Secret > Skip alarm for Approved control [90 days]
  • AWS > Secrets Manager > Secret > Skip alarm for Encryption at Rest control
  • AWS > Secrets Manager > Secret > Skip alarm for Encryption at Rest control [90 days]
  • AWS > Secrets Manager > Secret > Skip alarm for Tags control
  • AWS > Secrets Manager > Secret > Skip alarm for Tags control [90 days]

5.5.1 (2022-01-27)

Bug fixes

  • We've made a few improvements in the GraphQL query for AWS > Secrets Manager > Secret > Encryption At Rest control. You won't notice any difference, but things should run lighter and quicker than before.

5.5.0 (2021-12-20)

Control Types

  • AWS > Secrets Manager > Secret > Policy
  • AWS > Secrets Manager > Secret > Policy > Trusted Access

Policy Types

  • AWS > Secrets Manager > Secret > Policy
  • AWS > Secrets Manager > Secret > Policy > Trusted Access
  • AWS > Secrets Manager > Secret > Policy > Trusted Access > Accounts
  • AWS > Secrets Manager > Secret > Policy > Trusted Access > Identity Providers
  • AWS > Secrets Manager > Secret > Policy > Trusted Access > Organization Restrictions
  • AWS > Secrets Manager > Secret > Policy > Trusted Access > Services
  • AWS > Secrets Manager > Trusted Accounts [Default]
  • AWS > Secrets Manager > Trusted Identity Providers [Default]
  • AWS > Secrets Manager > Trusted Organizations [Default]
  • AWS > Secrets Manager > Trusted Services [Default]

Action Types

  • AWS > Secrets Manager > Secret > Set Policy Trusted Access

5.4.0 (2021-07-12)

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.3.0 (2021-03-09)

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.

5.2.2 (2021-01-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.2.1 (2020-09-22)

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.2.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.

Bug fixes

  • The ResourcePolicy field for secret resources is now properly and consistently sorted.

5.1.3 (2020-08-28)

Bug fixes

  • The AWS > Secrets Manager > Secret > CMDB control would sometimes remain in an error state when the secret was deleted from the AWS console. This has been fixed and now the secret will be deleted successfully from the Guardrails console as well.

Policy Types

Renamed

  • AWS > Secrets Manager > Regions to AWS > Secrets Manager > Regions [Default]

5.1.2 (2020-08-12)

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.1 (2020-07-01)

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.0 (2020-05-27)

What's new?

  • Updated AWS > SecretsManager > 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.