Product logo
DocsBlogPricing

@turbot/aws-dynamodb

Version
5.9.0
Released On
May 09, 2022
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.9.0 (2022-05-09)

What's new?

  • AWS > DynamoDB > Table CMDB will now also include information about Scalable Targets.

5.8.1 (2022-03-22)

Bug fixes

  • The AWS/DynamoDB/Metadata, AWS/DynamoDB/ReadOnly, AWS/DynamoDB/Operator, AWS/DynamoDB/Admin and AWS/DynamoDB/Owner grants would fail to show up on the Permissions tab while assigning access to users for an account when the AWS > DynamoDB > Permissions policy was set to Enabled. This is now fixed.

5.8.0 (2022-02-15)

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.

Policy Types

Added

  • AWS > DynamoDB > Backup > Approved > Custom
  • AWS > DynamoDB > Global Table > Approved > Custom
  • AWS > DynamoDB > Table > Approved > Custom

5.7.1 (2022-02-01)

Bug fixes

  • PIT recovery details on a Table did not update automatically in Turbot via real-time event handling. This is now fixed.
  • We've made a few improvements in the GraphQL query for AWS > DynamoDB > Table > Encryption at Rest control. You won't notice any difference, but things should run lighter and quicker than before.

5.7.0 (2022-01-07)

What's new?

  • AWS/DynamoDB/Admin AWS/DynamoDB/Metadata AWS/DynamoDB/Operator now include permissions for Table Replica, Kinesis Streaming Destination and PartiQL.

5.6.2 (2021-10-21)

Bug fixes

  • We've made some more improvements in the GraphQL queries for various permission policies to be more reliable than before. You won't notice any difference and things should continue to run smoothly as expected.

5.6.1 (2021-09-15)

Bug fixes

  • We’ve made a few improvements in the GraphQL queries for various controls to be more reliable than before. You won’t notice any difference and things should continue to run smoothly as expected.

5.6.0 (2021-08-13)

What's new?

  • AWS recently announced support for logging of data events for DynamoDB. Enabling these data level events would lead to a huge number of unnecessary events being raised and handled by Turbot. Hence, we've improved our event handling configuration and now filter which AWS events Turbot listens for based on resources' CMDB policies. If a resource's CMDB policy is not set to Enforce: Enabled, the EventBridge rules will be configured to not send any events for that resource. This will greatly reduce the number of unnecessary events that Turbot listens for and handles today.

Policy Types

Added

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-dynamodb

Removed

  • AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-dynamodb

5.5.0 (2021-07-16)

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.4.5 (2021-05-18)

Bug fixes

  • We've updated the AWS > DynamoDB > Permissions > Lockdown > Table Approved Regions policy's default value to be [*]. This will allow the policy to run much lighter and faster than before.

    We recommend that users include the approved regions from all AWS > DynamoDB > Table > Approved > Regions policy settings in their respective lockdown policies to ensure that these lockdown policies do not restrict any approved regions for tables.

5.4.4 (2020-12-15)

Bug fixes

  • Controls run faster now when in the tbd and skipped 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 in tbd and skipped, resulting in faster and lighter control runs.

5.4.3 (2020-12-09)

Bug fixes

  • The AWS > DynamoDB > Backup > CMDB control would go into an error state if the backup name had a hyphen (-). This issue has now been fixed.

5.4.2 (2020-12-04)

Bug fixes

  • We've updated various resources' Discovery and CMDB controls to ensure array properties are consistently sorted in the CMDB.

5.4.1 (2020-09-21)

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

5.3.4 (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.3.3 (2020-07-10)

Bug fixes

  • Fixed connection issues in AWS China regions for the AWS > DynamoDB > Global Table > Discovery control.

5.3.2 (2020-07-07)

Bug fixes

  • Updated various resource configurations to provide better compatibility with AWS China regions.

5.3.1 (2020-06-01)

Policy Types

Renamed

  • AWS > DynamoDB > Global Table > Configured > Precedence to AWS > DynamoDB > Global Table > Configured > Claim Precedence

5.3.0 (2020-05-15)

What's new?

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