Control types for @turbot/aws-lambda

• AWS > Lambda > Function > Active
• AWS > Lambda > Function > Allowed Runtime
• AWS > Lambda > Function > Approved
• AWS > Lambda > Function > CMDB
• AWS > Lambda > Function > Discovery
• AWS > Lambda > Function > Encryption at Rest
• AWS > Lambda > Function > Policy
• AWS > Lambda > Function > Policy > Trusted Access
• AWS > Lambda > Function > Tags
• AWS > Lambda > Function > Usage
• AWS > Lambda > Function Alias > Active
• AWS > Lambda > Function Alias > Approved
• AWS > Lambda > Function Alias > CMDB
• AWS > Lambda > Function Alias > Configured
• AWS > Lambda > Function Alias > Discovery
• AWS > Lambda > Function Version > Active
• AWS > Lambda > Function Version > Approved
• AWS > Lambda > Function Version > CMDB
• AWS > Lambda > Function Version > Discovery
• AWS > Lambda > Function Version > Policy
• AWS > Lambda > Function Version > Policy > Trusted Access
• AWS > Lambda > Layer > Approved
• AWS > Lambda > Layer > CMDB
• AWS > Lambda > Layer > Discovery

AWS > Lambda > Function > Active

Take an action when an AWS Lambda function is not active based on the
AWS > Lambda > Function > 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 > Lambda > Function > 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 > Lambda > Function > Allowed Runtime

Check if the AWS > Lambda > Function Runtime is allowed to be used per the AWS > Lambda > Function > Allowed Runtime > Values policy.

AWS > Lambda > Function > Approved

Take an action when an AWS Lambda function is not approved based on AWS > Lambda > Function > 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 > Lambda > Function > CMDB

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

AWS > Lambda > Function > Discovery

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

AWS > Lambda > Function > Encryption at Rest

Define the Encryption at Rest settings required for AWS > Lambda > Function.

Encryption at Rest refers specifically to the encryption of data when written
to an underlying storage system. This control determines whether the resource
is encrypted at rest, and sets encryption to your desired level.

The Encryption at Rest
control compares the encryption settings against the encryption policies for the resource
(AWS > Lambda > Function > Encryption at Rest > *),
raises an alarm, and takes the defined enforcement action.

AWS > Lambda > Function > Policy

AWS > Lambda > Function > Policy > Trusted Access

Take an action when AWS Lambda function policy is not trusted based on the
AWS > Lambda > Function > Policy > Trusted Access > * policies.

The Trusted Access control evaluates the function policy against the list of allowed
members in each of the Trusted Access sub-policies (Trusted Access > Accounts,
Trusted Access > Services etc.), this control raises an alarm and takes the
defined enforcement action.

If set to Enforce: Revoke untrusted access, access to non-trusted
members will be removed.

AWS > Lambda > Function > Tags

Take an action when an AWS Lambda function tags is not updated based on the AWS > Lambda > Function > Tags > * policies.

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

See Tags for more information.

AWS > Lambda > Function > Usage

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

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

AWS > Lambda > Function Alias > Active

Take an action when an AWS Lambda function alias is not active based on the
AWS > Lambda > Function Alias > 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 > Lambda > Function Alias > 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 > Lambda > Function Alias > Approved

Take an action when an AWS Lambda function alias is not approved based on AWS > Lambda > Function Alias > 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 > Lambda > Function Alias > CMDB

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

AWS > Lambda > Function Alias > Configured

Maintain AWS > Lambda > Function Alias 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 > Lambda > Function Alias > Discovery

Discover all AWS Lambda function alias 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 > Lambda > Function Alias > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Lambda > Function Version > Active

Take an action when an AWS Lambda function version is not active based on the
AWS > Lambda > Function Version > 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 > Lambda > Function Version > 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 > Lambda > Function Version > Approved

Take an action when an AWS Lambda function version is not approved based on AWS > Lambda > Function Version > 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 > Lambda > Function Version > CMDB

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

AWS > Lambda > Function Version > Discovery

Discover all AWS Lambda function version 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 > Lambda > Function Version > Regions policy, the CMDB control will delete the resource from the CMDB.

AWS > Lambda > Function Version > Policy

AWS > Lambda > Function Version > Policy > Trusted Access

Take an action when AWS Lambda function version policy is not trusted based on the
AWS > Lambda > Function Version > Policy > Trusted Access > * policies.

The Trusted Access control evaluates the function version policy against the list of allowed
members in each of the Trusted Access sub-policies (Trusted Access > Accounts,
Trusted Access > Services etc.), this control raises an alarm and takes the
defined enforcement action.

If set to Enforce: Revoke untrusted access, access to non-trusted
members will be removed.

AWS > Lambda > Layer > Approved

Take an action when an AWS Lambda layer is not approved based on AWS > Lambda > Layer > 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.

See Approved for more information.

AWS > Lambda > Layer > CMDB

Record and synchronize details for the AWS Lambda layer 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 > Lambda > Layer > 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 > Lambda > Layer > Discovery

Discover all AWS Lambda layer 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 > Lambda > Layer > 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.