Control types for @turbot/aws-neptune
- 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
AWS > Neptune > DB Cluster > Active
Take an action when an AWS Neptune db cluster is not active based on the
AWS > Neptune > DB Cluster > Active > * policies.
The Active control determines whether the resource is in active use, and if not, has the ability to delete / cleanup the resource. When running an automated compliance environment, it's common to end up with a wide range of alarms that are difficult and time consuming to clear. The Active control brings automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Neptune > DB Cluster > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.
See Active for more information.
AWS > Neptune > DB Cluster > Approved
Take an action when an AWS Neptune db cluster is not approved based on AWS > Neptune > DB Cluster > Approved > * policies.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
See Approved for more information.
AWS > Neptune > DB Cluster > CMDB
Record and synchronize details for the AWS Neptune db cluster into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Neptune > DB Cluster > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > Neptune > DB Cluster > Discovery
Discover all AWS Neptune db cluster resources and add them to the CMDB.
The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > Neptune > DB Cluster > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > Neptune > DB Cluster > Tags
Take an action when an AWS Neptune db cluster tags is not updated based on the AWS > Neptune > DB Cluster > Tags > * policies.
If the resource is not updated with the tags defined in AWS > Neptune > DB Cluster > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Neptune > DB Cluster > Usage
The Usage control determines whether the number of AWS Neptune db cluster resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Neptune > DB Cluster > Usage policy, and set the limit with the AWS > Neptune > DB Cluster > Usage > Limit policy.
AWS > Neptune > DB Instance > Active
Take an action when an AWS Neptune db instance is not active based on the
AWS > Neptune > DB Instance > Active > * policies.
The Active control determines whether the resource is in active use, and if not, has the ability to delete / cleanup the resource. When running an automated compliance environment, it's common to end up with a wide range of alarms that are difficult and time consuming to clear. The Active control brings automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Neptune > DB Instance > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.
See Active for more information.
AWS > Neptune > DB Instance > Approved
Take an action when an AWS Neptune db instance is not approved based on AWS > Neptune > DB Instance > Approved > * policies.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
See Approved for more information.
AWS > Neptune > DB Instance > CMDB
Record and synchronize details for the AWS Neptune db instance into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Neptune > DB Instance > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > Neptune > DB Instance > Discovery
Discover all AWS Neptune db instance resources and add them to the CMDB.
The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.
Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in AWS > Neptune > DB Instance > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > Neptune > DB Instance > Tags
Take an action when an AWS Neptune db instance tags is not updated based on the AWS > Neptune > DB Instance > Tags > * policies.
If the resource is not updated with the tags defined in AWS > Neptune > DB Instance > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > Neptune > DB Instance > Usage
The Usage control determines whether the number of AWS Neptune db instance resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > Neptune > DB Instance > Usage policy, and set the limit with the AWS > Neptune > DB Instance > Usage > Limit policy.