Control types for @turbot/aws-elasticbeanstalk

• AWS > Elastic Beanstalk > Application > Active
• AWS > Elastic Beanstalk > Application > Approved
• AWS > Elastic Beanstalk > Application > CMDB
• AWS > Elastic Beanstalk > Application > Discovery
• AWS > Elastic Beanstalk > Application > Tags
• AWS > Elastic Beanstalk > Application > Usage
• AWS > Elastic Beanstalk > Environment > Active
• AWS > Elastic Beanstalk > Environment > Approved
• AWS > Elastic Beanstalk > Environment > CMDB
• AWS > Elastic Beanstalk > Environment > Discovery
• AWS > Elastic Beanstalk > Environment > Tags
• AWS > Elastic Beanstalk > Environment > Usage

AWS > Elastic Beanstalk > Application > Active

Take an action when an AWS Elastic Beanstalk application is not active based on the
AWS > Elastic Beanstalk > Application > 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 > Elastic Beanstalk > Application > 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 > Elastic Beanstalk > Application > Approved

Take an action when an AWS Elastic Beanstalk application is not approved based on AWS > Elastic Beanstalk > Application > 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 > Elastic Beanstalk > Application > CMDB

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

AWS > Elastic Beanstalk > Application > Discovery

Discover all AWS Elastic Beanstalk application 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 > Elastic Beanstalk > Application > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Elastic Beanstalk > Application > Tags

Take an action when an AWS Elastic Beanstalk application tags is not updated based on the AWS > Elastic Beanstalk > Application > Tags > * policies.

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

See Tags for more information.

AWS > Elastic Beanstalk > Application > Usage

The Usage control determines whether the number of AWS Elastic Beanstalk application resources exceeds the configured usage limit for this account.

You can configure the behavior of this control with the AWS > Elastic Beanstalk > Application > Usage policy, and set the limit with the AWS > Elastic Beanstalk > Application > Usage > Limit policy.

AWS > Elastic Beanstalk > Environment > Active

Configure the behavior of the
Active control for
the AWS Elastic Beanstalk environment,
based on the AWS > Elastic Beanstalk > Environment > 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 > Elastic Beanstalk > Environment > 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.

AWS > Elastic Beanstalk > Environment > Approved

Take an action when an AWS Elastic Beanstalk environment is not approved based on AWS > Elastic Beanstalk > Environment > 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 > Elastic Beanstalk > Environment > CMDB

Record and synchronize details for the AWS Elastic Beanstalk environment into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.

Note that if CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.

CMDB controls also use the Regions policy associated with the resource. If
region is not in AWS > Elastic Beanstalk > Environment > 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 > Elastic Beanstalk > Environment > Discovery

Discover all AWS Elastic Beanstalk environment 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 > Elastic Beanstalk > Environment > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Elastic Beanstalk > Environment > Tags

Set tags on AWS Elastic Beanstalk environment according to AWS > Elastic Beanstalk > Environment > Tags > Template.

AWS > Elastic Beanstalk > Environment > Usage

How many AWS Elastic Beanstalk environments can be used in this environment and what is the current consumption against the limit.