Control types for @turbot/aws-lightsail

• AWS > Lightsail > Instance > Active
• AWS > Lightsail > Instance > Approved
• AWS > Lightsail > Instance > CMDB
• AWS > Lightsail > Instance > Discovery
• AWS > Lightsail > Instance > Tags
• AWS > Lightsail > Instance > Usage
• AWS > Lightsail > Load Balancer > Active
• AWS > Lightsail > Load Balancer > Approved
• AWS > Lightsail > Load Balancer > CMDB
• AWS > Lightsail > Load Balancer > Discovery
• AWS > Lightsail > Load Balancer > Tags
• AWS > Lightsail > Load Balancer > Usage
• AWS > Lightsail > Relational Database > Active
• AWS > Lightsail > Relational Database > Approved
• AWS > Lightsail > Relational Database > CMDB
• AWS > Lightsail > Relational Database > Discovery
• AWS > Lightsail > Relational Database > Tags
• AWS > Lightsail > Relational Database > Usage

AWS > Lightsail > Instance > Active

Take an action when an AWS Lightsail instance is not active based on the
AWS > Lightsail > 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 > Lightsail > 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 > Lightsail > Instance > Approved

Take an action when an AWS Lightsail instance is not approved based on AWS > Lightsail > 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.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

AWS > Lightsail > Instance > CMDB

Record and synchronize details for the AWS Lightsail instance into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails 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 > Lightsail > Instance > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Lightsail > Instance > Discovery

Discover all AWS Lightsail 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 > Lightsail > Instance > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Lightsail > Instance > Tags

Take an action when an AWS Lightsail instance tags is not updated based on the AWS > Lightsail > Instance > Tags > * policies.

If the resource is not updated with the tags defined in AWS > Lightsail > Instance > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > Lightsail > Instance > Usage

The Usage control determines whether the number of AWS Lightsail instance resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Lightsail > Instance > Usage policy, and set the limit with the AWS > Lightsail > Instance > Usage > Limit policy.

AWS > Lightsail > Load Balancer > Active

Take an action when an AWS Lightsail load balancer is not active based on the
AWS > Lightsail > Load Balancer > 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 > Lightsail > Load Balancer > 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 > Lightsail > Load Balancer > Approved

Take an action when an AWS Lightsail load balancer is not approved based on AWS > Lightsail > Load Balancer > 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.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

AWS > Lightsail > Load Balancer > CMDB

Record and synchronize details for the AWS Lightsail load balancer into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails 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 > Lightsail > Load Balancer > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Lightsail > Load Balancer > Discovery

Discover all AWS Lightsail load balancer 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 > Lightsail > Load Balancer > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Lightsail > Load Balancer > Tags

Take an action when an AWS Lightsail load balancer tags is not updated based on the AWS > Lightsail > Load Balancer > Tags > * policies.

If the resource is not updated with the tags defined in AWS > Lightsail > Load Balancer > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > Lightsail > Load Balancer > Usage

The Usage control determines whether the number of AWS Lightsail load balancer resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Lightsail > Load Balancer > Usage policy, and set the limit with the AWS > Lightsail > Load Balancer > Usage > Limit policy.

AWS > Lightsail > Relational Database > Active

Take an action when an AWS Lightsail relational database is not active based on the
AWS > Lightsail > Relational Database > 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 > Lightsail > Relational Database > 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 > Lightsail > Relational Database > Approved

Take an action when an AWS Lightsail relational database is not approved based on AWS > Lightsail > Relational Database > 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.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

AWS > Lightsail > Relational Database > CMDB

Record and synchronize details for the AWS Lightsail relational database into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails 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 > Lightsail > Relational Database > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Lightsail > Relational Database > Discovery

Discover all AWS Lightsail relational database 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 > Lightsail > Relational Database > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Lightsail > Relational Database > Tags

Take an action when an AWS Lightsail relational database tags is not updated based on the AWS > Lightsail > Relational Database > Tags > * policies.

If the resource is not updated with the tags defined in AWS > Lightsail > Relational Database > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.

AWS > Lightsail > Relational Database > Usage

The Usage control determines whether the number of AWS Lightsail relational database resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Lightsail > Relational Database > Usage policy, and set the limit with the AWS > Lightsail > Relational Database > Usage > Limit policy.