Control types for @turbot/aws-vpc-core
- AWS > VPC > DHCP Options > Active
- AWS > VPC > DHCP Options > Approved
- AWS > VPC > DHCP Options > CMDB
- AWS > VPC > DHCP Options > Configured
- AWS > VPC > DHCP Options > Discovery
- AWS > VPC > DHCP Options > Tags
- AWS > VPC > DHCP Options > Usage
- AWS > VPC > Default VPC
- AWS > VPC > Default VPC > Approved
- AWS > VPC > Route > CMDB
- AWS > VPC > Route > Configured
- AWS > VPC > Route > Discovery
- AWS > VPC > Route Table > Active
- AWS > VPC > Route Table > Approved
- AWS > VPC > Route Table > CMDB
- AWS > VPC > Route Table > Configured
- AWS > VPC > Route Table > Discovery
- AWS > VPC > Route Table > Tags
- AWS > VPC > Route Table > Usage
- AWS > VPC > Stack
- AWS > VPC > Subnet > Active
- AWS > VPC > Subnet > Approved
- AWS > VPC > Subnet > Auto Assign Public IP
- AWS > VPC > Subnet > CMDB
- AWS > VPC > Subnet > Configured
- AWS > VPC > Subnet > Discovery
- AWS > VPC > Subnet > Tags
- AWS > VPC > Subnet > Usage
- AWS > VPC > VPC > Active
- AWS > VPC > VPC > Approved
- AWS > VPC > VPC > CMDB
- AWS > VPC > VPC > Configured
- AWS > VPC > VPC > DNS Hostnames
- AWS > VPC > VPC > DNS Resolution
- AWS > VPC > VPC > Discovery
- AWS > VPC > VPC > Flow Logging
- AWS > VPC > VPC > Stack
- AWS > VPC > VPC > Tags
- AWS > VPC > VPC > Usage
AWS > VPC > DHCP Options > Active
Take an action when an AWS VPC dhcp options is not active based on the
AWS > VPC > DHCP Options > 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 > VPC > DHCP Options > 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 > VPC > DHCP Options > Approved
Take an action when an AWS VPC dhcp options is not approved based on AWS > VPC > DHCP Options > 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 > VPC > DHCP Options > CMDB
Record and synchronize details for the AWS VPC dhcp options 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 > VPC > DHCP Options > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > VPC > DHCP Options > Configured
Maintain AWS > VPC > DHCP Options configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored and inherit from the stack that owns it
AWS > VPC > DHCP Options > Discovery
Discover all AWS VPC dhcp options 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 > VPC > DHCP Options > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > VPC > DHCP Options > Tags
Take an action when an AWS VPC dhcp options tags is not updated based on the AWS > VPC > DHCP Options > Tags > * policies.
If the resource is not updated with the tags defined in AWS > VPC > DHCP Options > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > VPC > DHCP Options > Usage
The Usage control determines whether the number of AWS VPC dhcp options resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > VPC > DHCP Options > Usage policy, and set the limit with the AWS > VPC > DHCP Options > Usage > Limit policy.
AWS > VPC > Default VPC
AWS > VPC > Default VPC > Approved
Raise an alarm if the default VPC exists in the region.
AWS > VPC > Route > CMDB
Record and synchronize details for the AWS VPC route table route 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".
Note: Setting CMDB to Skip will also pause these changes.
AWS > VPC > Route > Configured
Maintain AWS > VPC > Route configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored and inherit from the stack that owns it
AWS > VPC > Route > Discovery
Discover all AWS VPC route table route 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 > VPC > Route Table > Active
Take an action when an AWS VPC route table is not active based on the
AWS > VPC > Route Table > 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 > VPC > Route Table > 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 > VPC > Route Table > Approved
Take an action when an AWS VPC route table is not approved based on AWS > VPC > Route Table > 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 > VPC > Route Table > CMDB
Record and synchronize details for the AWS VPC route table 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 > VPC > Route Table > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > VPC > Route Table > Configured
Maintain AWS > VPC > Route Table configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored and inherit from the stack that owns it
AWS > VPC > Route Table > Discovery
Discover all AWS VPC route table 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 > VPC > Route Table > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > VPC > Route Table > Tags
Take an action when an AWS VPC route table tags is not updated based on the AWS > VPC > Route Table > Tags > * policies.
If the resource is not updated with the tags defined in AWS > VPC > Route Table > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > VPC > Route Table > Usage
The Usage control determines whether the number of AWS VPC route table resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > VPC > Route Table > Usage policy, and set the limit with the AWS > VPC > Route Table > Usage > Limit policy.
AWS > VPC > Stack
Configure a custom stack on AWS, per the custom Stack > Source.
A Turbot Stack is a set of resources configured by Turbot, as specified
via Terraform source. Stacks are responsible for the creation and deletion
of multiple resources. Once created, stack resources are responsible for
configuring themselves from the stack source via their Configured control.
AWS > VPC > Subnet > Active
Take an action when an AWS VPC subnet is not active based on the
AWS > VPC > Subnet > 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 > VPC > Subnet > 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 > VPC > Subnet > Approved
Take an action when an AWS VPC subnet is not approved based on AWS > VPC > Subnet > 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 > VPC > Subnet > Auto Assign Public IP
Check if Subnet's Auto-assign Public IP property is enabled for Subnet types in AWS > VPC > Subnet Auto Assign Public IP Types. Subnet types that are not in the AWS > VPC > Subnet Auto Assign Public IP Types will be checked if the Auto-assign Public IP property is disabled.
AWS > VPC > Subnet > CMDB
Record and synchronize details for the AWS VPC subnet 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 > VPC > Subnet > 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 all properties of this resource type.
AWS > VPC > Subnet > Configured
Maintain AWS > VPC > Subnet configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored and inherit from the stack that owns it
AWS > VPC > Subnet > Discovery
Discover all AWS VPC subnet 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 > VPC > Subnet > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > VPC > Subnet > Tags
Take an action when an AWS VPC subnet tags is not updated based on the AWS > VPC > Subnet > Tags > * policies.
If the resource is not updated with the tags defined in AWS > VPC > Subnet > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > VPC > Subnet > Usage
The Usage control determines whether the number of AWS VPC subnet resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > VPC > Subnet > Usage policy, and set the limit with the AWS > VPC > Subnet > Usage > Limit policy.
AWS > VPC > VPC > Active
Take an action when an AWS VPC vpc is not active based on the
AWS > VPC > VPC > 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 > VPC > VPC > 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 > VPC > VPC > Approved
Take an action when an AWS VPC vpc is not approved based on AWS > VPC > VPC > 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 > VPC > VPC > CMDB
Record and synchronize details for the AWS VPC vpc 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 > VPC > VPC > Regions policy, the CMDB control will delete the resource from the CMDB. (Note: Setting CMDB to Skip will also pause these changes.)
AWS > VPC > VPC > Configured
Maintain AWS > VPC > VPC configuration
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored and inherit from the stack that owns it
AWS > VPC > VPC > DNS Hostnames
Check if the AWS VPC DNS Hostnames configuration is set correctly.
AWS > VPC > VPC > DNS Resolution
Check if the AWS VPC DNS Resolution configuration is set correctly.
AWS > VPC > VPC > Discovery
Discover all AWS VPC vpc 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 > VPC > VPC > Regions policy, the CMDB control will delete the resource from the CMDB.
AWS > VPC > VPC > Flow Logging
Configure a custom stack on the AWS Account, per the Custom Stack > Source.
A Turbot Stack is a set of resources configured by Turbot, as specified
via Terraform source. Stacks are responsible for the creation and deletion
of multiple resources. Once created, stack resources are responsible for
configuring themselves from the stack source via their Configured control.
AWS > VPC > VPC > Stack
Configure a custom stack on AWS, per the custom Stack > Source.
A Turbot Stack is a set of resources configured by Turbot, as specified
via Terraform source. Stacks are responsible for the creation and deletion
of multiple resources. Once created, stack resources are responsible for
configuring themselves from the stack source via their Configured control.
AWS > VPC > VPC > Tags
Take an action when an AWS VPC vpc tags is not updated based on the AWS > VPC > VPC > Tags > * policies.
If the resource is not updated with the tags defined in AWS > VPC > VPC > Tags > Template, this control raises an alarm and takes the defined enforcement action.
See Tags for more information.
AWS > VPC > VPC > Usage
The Usage control determines whether the number of AWS VPC vpc resources exceeds the configured usage limit for this region.
You can configure the behavior of this control with the AWS > VPC > VPC > Usage policy, and set the limit with the AWS > VPC > VPC > Usage > Limit policy.