Control types for @turbot/aws-directconnect

• AWS > Direct Connect > Connection > Active
• AWS > Direct Connect > Connection > Approved
• AWS > Direct Connect > Connection > CMDB
• AWS > Direct Connect > Connection > Discovery
• AWS > Direct Connect > Connection > Tags
• AWS > Direct Connect > Connection > Usage
• AWS > Direct Connect > Direct Connect Gateway > Active
• AWS > Direct Connect > Direct Connect Gateway > Approved
• AWS > Direct Connect > Direct Connect Gateway > CMDB
• AWS > Direct Connect > Direct Connect Gateway > Discovery
• AWS > Direct Connect > Direct Connect Gateway > Usage
• AWS > Direct Connect > Lag > Active
• AWS > Direct Connect > Lag > Approved
• AWS > Direct Connect > Lag > CMDB
• AWS > Direct Connect > Lag > Discovery
• AWS > Direct Connect > Lag > Tags
• AWS > Direct Connect > Lag > Usage
• AWS > Direct Connect > Virtual Interface > Active
• AWS > Direct Connect > Virtual Interface > Approved
• AWS > Direct Connect > Virtual Interface > CMDB
• AWS > Direct Connect > Virtual Interface > Discovery
• AWS > Direct Connect > Virtual Interface > Tags
• AWS > Direct Connect > Virtual Interface > Usage

AWS > Direct Connect > Connection > Active

Take an action when an AWS Direct Connect connection is not active based on the
AWS > Direct Connect > Connection > 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 > Direct Connect > Connection > 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 > Direct Connect > Connection > Approved

Take an action when an AWS Direct Connect connection is not approved based on AWS > Direct Connect > Connection > 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 > Direct Connect > Connection > CMDB

Record and synchronize details for the AWS Direct Connect connection 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 > Direct Connect > Connection > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Direct Connect > Connection > Discovery

Discover all AWS Direct Connect connection 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 > Direct Connect > Connection > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Direct Connect > Connection > Tags

Take an action when an AWS Direct Connect connection tags is not updated based on the AWS > Direct Connect > Connection > Tags > * policies.

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

See Tags for more information.

AWS > Direct Connect > Connection > Usage

The Usage control determines whether the number of AWS Direct Connect connection resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Direct Connect > Connection > Usage policy, and set the limit with the AWS > Direct Connect > Connection > Usage > Limit policy.

AWS > Direct Connect > Direct Connect Gateway > Active

Take an action when an AWS Direct Connect direct connect gateway is not active based on the
AWS > Direct Connect > Direct Connect Gateway > 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 > Direct Connect > Direct Connect Gateway > 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 > Direct Connect > Direct Connect Gateway > Approved

Take an action when an AWS Direct Connect direct connect gateway is not approved based on AWS > Direct Connect > Direct Connect Gateway > 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 > Direct Connect > Direct Connect Gateway > CMDB

Record and synchronize details for the AWS Direct Connect direct connect gateway 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".

AWS > Direct Connect > Direct Connect Gateway > Discovery

Discover all AWS Direct Connect direct connect gateway 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.

AWS > Direct Connect > Direct Connect Gateway > Usage

The Usage control determines whether the number of AWS Direct Connect direct connect gateway resources exceeds the configured usage limit for this account.

You can configure the behavior of this control with the AWS > Direct Connect > Direct Connect Gateway > Usage policy, and set the limit with the AWS > Direct Connect > Direct Connect Gateway > Usage > Limit policy.

AWS > Direct Connect > Lag > Active

Take an action when an AWS Direct Connect lag is not active based on the
AWS > Direct Connect > Lag > 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 > Direct Connect > Lag > 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 > Direct Connect > Lag > Approved

Take an action when an AWS Direct Connect lag is not approved based on AWS > Direct Connect > Lag > 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 > Direct Connect > Lag > CMDB

Record and synchronize details for the AWS Direct Connect lag 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 > Direct Connect > Lag > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

AWS > Direct Connect > Lag > Discovery

Discover all AWS Direct Connect lag 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 > Direct Connect > Lag > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Direct Connect > Lag > Tags

Take an action when an AWS Direct Connect lag tags is not updated based on the AWS > Direct Connect > Lag > Tags > * policies.

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

See Tags for more information.

AWS > Direct Connect > Lag > Usage

The Usage control determines whether the number of AWS Direct Connect lag resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Direct Connect > Lag > Usage policy, and set the limit with the AWS > Direct Connect > Lag > Usage > Limit policy.

AWS > Direct Connect > Virtual Interface > Active

Take an action when an AWS Direct Connect virtual interface is not active based on the
AWS > Direct Connect > Virtual Interface > 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 > Direct Connect > Virtual Interface > 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 > Direct Connect > Virtual Interface > Approved

Take an action when an AWS Direct Connect virtual interface is not approved based on AWS > Direct Connect > Virtual Interface > 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 > Direct Connect > Virtual Interface > CMDB

Record and synchronize details for the AWS Direct Connect virtual interface 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 > Direct Connect > Virtual Interface > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)

This control will automatically re-run every 24 hours because AWS does not currently support real-time events for this resource type.

AWS > Direct Connect > Virtual Interface > Discovery

Discover all AWS Direct Connect virtual interface 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 > Direct Connect > Virtual Interface > Regions policy, the CMDB control will delete the resource from the CMDB.

This control will automatically re-run every 24 hours because AWS does not currently support real-time events for this resource type.

AWS > Direct Connect > Virtual Interface > Tags

Take an action when an AWS Direct Connect virtual interface tags is not updated based on the AWS > Direct Connect > Virtual Interface > Tags > * policies.

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

See Tags for more information.

AWS > Direct Connect > Virtual Interface > Usage

The Usage control determines whether the number of AWS Direct Connect virtual interface resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the AWS > Direct Connect > Virtual Interface > Usage policy, and set the limit with the AWS > Direct Connect > Virtual Interface > Usage > Limit policy.