@turbot/aws-neptune
Recommended Version
Version
5.4.0
Released On
Nov 09, 2023
Depends On
@turbot/aws ^5.0.0
@turbot/turbot ^5.22.0
@turbot/turbot-iam ^5.1.0
@turbot/aws-iam ^5.1.0
@turbot/aws-rds ^5.0.0
@turbot/turbot ^5.22.0
@turbot/turbot-iam ^5.1.0
@turbot/aws-iam ^5.1.0
@turbot/aws-rds ^5.0.0
Resource Types
Control Types
- AWS > Neptune > DB Cluster > Active
- AWS > Neptune > DB Cluster > Approved
- AWS > Neptune > DB Cluster > CMDB
- AWS > Neptune > DB Cluster > Discovery
- AWS > Neptune > DB Cluster > Tags
- AWS > Neptune > DB Cluster > Usage
- AWS > Neptune > DB Instance > Active
- AWS > Neptune > DB Instance > Approved
- AWS > Neptune > DB Instance > CMDB
- AWS > Neptune > DB Instance > Discovery
- AWS > Neptune > DB Instance > Tags
- AWS > Neptune > DB Instance > Usage
Policy Types
- AWS > Neptune > Approved Regions [Default]
- AWS > Neptune > DB Cluster > Active
- AWS > Neptune > DB Cluster > Active > Age
- AWS > Neptune > DB Cluster > Active > Budget
- AWS > Neptune > DB Cluster > Active > Last Modified
- AWS > Neptune > DB Cluster > Approved
- AWS > Neptune > DB Cluster > Approved > Budget
- AWS > Neptune > DB Cluster > Approved > Custom
- AWS > Neptune > DB Cluster > Approved > Regions
- AWS > Neptune > DB Cluster > Approved > Usage
- AWS > Neptune > DB Cluster > CMDB
- AWS > Neptune > DB Cluster > Regions
- AWS > Neptune > DB Cluster > Tags
- AWS > Neptune > DB Cluster > Tags > Template
- AWS > Neptune > DB Cluster > Usage
- AWS > Neptune > DB Cluster > Usage > Limit
- AWS > Neptune > DB Instance > Active
- AWS > Neptune > DB Instance > Active > Age
- AWS > Neptune > DB Instance > Active > Budget
- AWS > Neptune > DB Instance > Active > Last Modified
- AWS > Neptune > DB Instance > Approved
- AWS > Neptune > DB Instance > Approved > Budget
- AWS > Neptune > DB Instance > Approved > Custom
- AWS > Neptune > DB Instance > Approved > Regions
- AWS > Neptune > DB Instance > Approved > Usage
- AWS > Neptune > DB Instance > CMDB
- AWS > Neptune > DB Instance > Regions
- AWS > Neptune > DB Instance > Tags
- AWS > Neptune > DB Instance > Tags > Template
- AWS > Neptune > DB Instance > Usage
- AWS > Neptune > DB Instance > Usage > Limit
- AWS > Neptune > Regions
- AWS > Neptune > Tags Template [Default]
Release Notes
5.4.0 (2023-11-09)
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 > Neptune > DB Cluster > Approved > Custom
- AWS > Neptune > DB Instance > Approved > Custom
Action Types
- AWS > Neptune > DB Cluster > Delete from AWS
- AWS > Neptune > DB Cluster > Set Tags
- AWS > Neptune > DB Cluster > Skip alarm for Active control
- AWS > Neptune > DB Cluster > Skip alarm for Active control [90 days]
- AWS > Neptune > DB Cluster > Skip alarm for Approved control
- AWS > Neptune > DB Cluster > Skip alarm for Approved control [90 days]
- AWS > Neptune > DB Cluster > Skip alarm for Tags control
- AWS > Neptune > DB Cluster > Skip alarm for Tags control [90 days]
- AWS > Neptune > DB Instance > Delete from AWS
- AWS > Neptune > DB Instance > Set Tags
- AWS > Neptune > DB Instance > Skip alarm for Active control
- AWS > Neptune > DB Instance > Skip alarm for Active control [90 days]
- AWS > Neptune > DB Instance > Skip alarm for Approved control
- AWS > Neptune > DB Instance > Skip alarm for Approved control [90 days]
- AWS > Neptune > DB Instance > Skip alarm for Tags control
- AWS > Neptune > DB Instance > Skip alarm for Tags control [90 days]
5.3.1 (2021-02-09)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
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 intbd
andskipped
, resulting in faster and lighter control runs.
5.3.0 (2020-10-16)
What's new?
- We've made improvements to how Approved controls interact with CMDB policies and controls for more reliable approved checks. Now, if a resource's CMDB policy is set to
Skip
, its Approved control will move toinvalid
to prevent the Approved control from making a decision based on outdated information. Also, Approved controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.
5.2.0 (2020-10-12)
What's new?
- We've made improvements to how Active controls interact with CMDB policies and controls for more reliable active checks. Now, if a resource's CMDB policy is set to
Skip
, its Active control will move toinvalid
to prevent the Active control from making a decision based on outdated information. Also, Active controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.
5.1.1 (2020-09-29)
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.1.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]
toRegions
to be consistent with our other regions policies.
5.0.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.0.1 (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.0.0 (2020-06-12)
Resource Types
- AWS > Neptune
- AWS > Neptune > DB Cluster
- AWS > Neptune > DB Instance
Control Types
- AWS > Neptune > DB Cluster > Active
- AWS > Neptune > DB Cluster > Approved
- AWS > Neptune > DB Cluster > CMDB
- AWS > Neptune > DB Cluster > Discovery
- AWS > Neptune > DB Cluster > Tags
- AWS > Neptune > DB Cluster > Usage
- AWS > Neptune > DB Instance > Active
- AWS > Neptune > DB Instance > Approved
- AWS > Neptune > DB Instance > CMDB
- AWS > Neptune > DB Instance > Discovery
- AWS > Neptune > DB Instance > Tags
- AWS > Neptune > DB Instance > Usage
Policy Types
- AWS > Neptune > Approved Regions [Default]
- AWS > Neptune > DB Cluster > Active
- AWS > Neptune > DB Cluster > Active > Age
- AWS > Neptune > DB Cluster > Active > Budget
- AWS > Neptune > DB Cluster > Active > Last Modified
- AWS > Neptune > DB Cluster > Approved
- AWS > Neptune > DB Cluster > Approved > Budget
- AWS > Neptune > DB Cluster > Approved > Regions
- AWS > Neptune > DB Cluster > Approved > Usage
- AWS > Neptune > DB Cluster > CMDB
- AWS > Neptune > DB Cluster > Regions
- AWS > Neptune > DB Cluster > Tags
- AWS > Neptune > DB Cluster > Tags > Template
- AWS > Neptune > DB Cluster > Usage
- AWS > Neptune > DB Cluster > Usage > Limit
- AWS > Neptune > DB Instance > Active
- AWS > Neptune > DB Instance > Active > Age
- AWS > Neptune > DB Instance > Active > Budget
- AWS > Neptune > DB Instance > Active > Last Modified
- AWS > Neptune > DB Instance > Approved
- AWS > Neptune > DB Instance > Approved > Budget
- AWS > Neptune > DB Instance > Approved > Regions
- AWS > Neptune > DB Instance > Approved > Usage
- AWS > Neptune > DB Instance > CMDB
- AWS > Neptune > DB Instance > Regions
- AWS > Neptune > DB Instance > Tags
- AWS > Neptune > DB Instance > Tags > Template
- AWS > Neptune > DB Instance > Usage
- AWS > Neptune > DB Instance > Usage > Limit
- AWS > Neptune > Regions [Default]
- AWS > Neptune > Tags Template [Default]
Action Types
- AWS > Neptune > DB Cluster > Delete
- AWS > Neptune > DB Cluster > Router
- AWS > Neptune > DB Cluster > Update Tags
- AWS > Neptune > DB Instance > Delete
- AWS > Neptune > DB Instance > Router
- AWS > Neptune > DB Instance > Update Tags