Policy types for @turbot/aws-elasticbeanstalk
- AWS > Elastic Beanstalk > API Enabled
- AWS > Elastic Beanstalk > Application > Active
- AWS > Elastic Beanstalk > Application > Active > Age
- AWS > Elastic Beanstalk > Application > Active > Budget
- AWS > Elastic Beanstalk > Application > Active > Last Modified
- AWS > Elastic Beanstalk > Application > Approved
- AWS > Elastic Beanstalk > Application > Approved > Budget
- AWS > Elastic Beanstalk > Application > Approved > Regions
- AWS > Elastic Beanstalk > Application > Approved > Usage
- AWS > Elastic Beanstalk > Application > CMDB
- AWS > Elastic Beanstalk > Application > Regions
- AWS > Elastic Beanstalk > Application > Tags
- AWS > Elastic Beanstalk > Application > Tags > Template
- AWS > Elastic Beanstalk > Application > Usage
- AWS > Elastic Beanstalk > Application > Usage > Limit
- AWS > Elastic Beanstalk > Approved Regions [Default]
- AWS > Elastic Beanstalk > Enabled
- AWS > Elastic Beanstalk > Environment > Active
- AWS > Elastic Beanstalk > Environment > Active > Age
- AWS > Elastic Beanstalk > Environment > Active > Last Modified
- AWS > Elastic Beanstalk > Environment > Active > Status
- AWS > Elastic Beanstalk > Environment > Approved
- AWS > Elastic Beanstalk > Environment > Approved > Regions
- AWS > Elastic Beanstalk > Environment > Approved > Usage
- AWS > Elastic Beanstalk > Environment > CMDB
- AWS > Elastic Beanstalk > Environment > Regions
- AWS > Elastic Beanstalk > Environment > Tags
- AWS > Elastic Beanstalk > Environment > Tags > Template
- AWS > Elastic Beanstalk > Environment > Usage
- AWS > Elastic Beanstalk > Environment > Usage > Limit
- AWS > Elastic Beanstalk > Permissions
- AWS > Elastic Beanstalk > Permissions > Levels
- AWS > Elastic Beanstalk > Permissions > Levels > Modifiers
- AWS > Elastic Beanstalk > Permissions > Lockdown
- AWS > Elastic Beanstalk > Permissions > Lockdown > API Boundary
- AWS > Elastic Beanstalk > Regions
- AWS > Elastic Beanstalk > Tags Template [Default]
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-elasticbeanstalk
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-elasticbeanstalk
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-elasticbeanstalk
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-elasticbeanstalk
AWS > Elastic Beanstalk > API Enabled
Configure whether the AWS Elastic Beanstalk API is enabled.
Note: Disabling the service disables the API for ALL users and roles, and Turbot will have no access to the API.
[ "Enabled", "Disabled", "Enabled if AWS > Elastic Beanstalk > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Elastic Beanstalk > Enabled" ], "default": "Enabled"}
AWS > Elastic Beanstalk > Application > Active
Determine the action to take when an AWS Elastic Beanstalk application, based on the AWS > Elastic Beanstalk > Application > Active > *
policies.
The 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.
[ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning"]
{ "type": "string", "enum": [ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning" ], "example": [ "Check: Active" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Active > Age
The age after which the AWS Elastic Beanstalk application is no longer considered active. If a create time is unavailable, the time Turbot discovered the resource is used.
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.
[ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days"]
{ "type": "string", "enum": [ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days" ], "example": [ "Force inactive if age > 90 days" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Active > Budget
The impact of the budget state on the active control. This policy allows you to force
applications to inactive based on the current budget state, as reflected in
AWS > Account > Budget > State
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.
[ "Skip", "Force inactive if Budget > State is Over or higher", "Force inactive if Budget > State is Critical or higher", "Force inactive if Budget > State is Shutdown"]
{ "type": "string", "enum": [ "Skip", "Force inactive if Budget > State is Over or higher", "Force inactive if Budget > State is Critical or higher", "Force inactive if Budget > State is Shutdown" ], "example": [ "Skip" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Active > Last Modified
The number of days since the AWS Elastic Beanstalk application was last modified before it is considered inactive.
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.
[ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days"]
{ "type": "string", "enum": [ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days" ], "example": [ "Active if last modified <= 90 days" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Approved
Determine the action to take 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.
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Approved > Budget
The policy allows you to set applications to unapproved based on the current budget state, as reflected in AWS > Account > Budget > State
This policy will be evaluated by the Approved control. If an AWS Elastic Beanstalk application is not matched by the approved list, it will be subject to the action specified in the AWS > Elastic Beanstalk > Application > Approved
policy.
See Approved for more information.
[ "Skip", "Unapproved if Budget > State is Over or higher", "Unapproved if Budget > State is Critical or higher", "Unapproved if Budget > State is Shutdown"]
{ "type": "string", "enum": [ "Skip", "Unapproved if Budget > State is Over or higher", "Unapproved if Budget > State is Critical or higher", "Unapproved if Budget > State is Shutdown" ], "example": [ "Unapproved if Budget > State is Shutdown" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Approved > Regions
A list of AWS regions in which AWS Elastic Beanstalk applications are approved for use.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
This policy will be evaluated by the Approved control. If an AWS Elastic Beanstalk application is created in a region that is not in the approved list, it will be subject to the action specified in the AWS > Elastic Beanstalk > Application > Approved
policy.
See Approved for more information.
"{\n regions: policy(uri: \"tmod:@turbot/aws-elasticbeanstalk#/policy/types/elasticBeanstalkApprovedRegionsDefault\")\n}\n"
"{% if $.regions | length == 0 %} [] {% endif %}{% for item in $.regions %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Application > Approved > Usage
Determine whether the AWS Elastic Beanstalk application is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Elastic Beanstalk application is not approved, it will be subject to the action specified in the AWS > Elastic Beanstalk > Application > Approved
policy.
See Approved for more information.
[ "Not approved", "Approved", "Approved if AWS > Elastic Beanstalk > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if AWS > Elastic Beanstalk > Enabled" ], "example": [ "Not approved" ], "default": "Approved if AWS > Elastic Beanstalk > Enabled"}
AWS > Elastic Beanstalk > Application > CMDB
Configure whether to 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 Turbot CMDB. All policies and controls in Turbot are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
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.)
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Elastic Beanstalk > Application > Regions
A list of AWS regions in which AWS Elastic Beanstalk applications are supported for use.
Any applications in a region not listed here will not be recorded in CMDB.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
"{\n regions: policyValue(uri:\"tmod:@turbot/aws-elasticbeanstalk#/policy/types/elasticBeanstalkRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Application > Tags
Determine the action to take when an AWS Elastic Beanstalk application tags are not updated based on the AWS > Elastic Beanstalk > Application > Tags > *
policies.
The control ensure AWS Elastic Beanstalk application tags include tags defined in AWS > Elastic Beanstalk > Application > Tags > Template
.
Tags not defined in Application Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Tags > Template
The template is used to generate the keys and values for AWS Elastic Beanstalk application.
Tags not defined in Application Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
[ "{\n account {\n turbot {\n id\n }\n }\n}\n", "{\n defaultTags: policyValue(uri:\"tmod:@turbot/aws-elasticbeanstalk#/policy/types/elasticBeanstalkTagsTemplate\" resourceId: \"{{ $.account.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
AWS > Elastic Beanstalk > Application > Usage
Configure the number of AWS Elastic Beanstalk applications that can be used for this account and the current consumption against the limit.
You can configure the behavior of the control with this AWS > Elastic Beanstalk > Application > Usage
policy.
[ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit"]
{ "type": "string", "enum": [ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit" ], "example": [ "Check: Usage <= 85% of Limit" ], "default": "Skip"}
AWS > Elastic Beanstalk > Application > Usage > Limit
Maximum number of items that can be created for this account.
{ "type": "integer", "minimum": 0, "default": 75}
AWS > Elastic Beanstalk > Approved Regions [Default]
A list of AWS regions in which AWS Elastic Beanstalk resources are approved for use.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
This policy is the default value for all AWS Elastic Beanstalk resources' Approved > Regions policies.
"{\n regions: policyValue(uri:\"tmod:@turbot/aws#/policy/types/approvedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Enabled
Configure whether the AWS Elastic Beanstalk service is enabled. This will only affect Turbot managed User Roles and will allow the Turbot managed user to access AWS Elastic Beanstalk service.
Enabled
policy allows Turbot managed users to perform all the actions for the serviceEnabled: Metadata Only
policy allows Turbot managed users to perform only the metadata level actions for the service (likedescribe*
,list*
)
Note:
Disabled
policy disables the service but does NOT disable the API for Turbot or SuperUsers- All the resource data stored in the Turbot CMDB is considered to be metadata
- For more information related to permissions and grant levels, please check the documentation
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
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.
[ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning"]
{ "type": "string", "enum": [ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning" ], "example": [ "Check: Active" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Active > Age
The age after which the AWS Elastic Beanstalk environment is no longer considered active. If a create time is unavailable, the time Turbot discovered the resource is used.
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.
[ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days"]
{ "type": "string", "enum": [ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days" ], "example": [ "Force inactive if age > 90 days" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Active > Last Modified
The number of days since the AWS Elastic Beanstalk environment was last modified before it is considered inactive.
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.
[ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days"]
{ "type": "string", "enum": [ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days" ], "example": [ "Active if last modified <= 90 days" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Active > Status
The impact of the status of the AWS Elastic Beanstalk environment on the active control. This policy allows you to check which status determines if the AWS Elastic Beanstalk environment is active.
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.
[ "Skip", "Active if status is Ready", "Force active if status is Ready"]
{ "type": "string", "enum": [ "Skip", "Active if status is Ready", "Force active if status is Ready" ], "example": [ "Skip" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Approved
Determine the action to take 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.
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Approved > Regions
A list of AWS regions in which AWS Elastic Beanstalk environments are approved for use.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
This policy will be evaluated by the Approved control. If an AWS Elastic Beanstalk environment is created in a region that is NOT in the approved list, it will be subject to the action specified in the AWS > Elastic Beanstalk > Environment > Approved policy.
See Approved for more information.
"{\n regions: policyValue(uri:\"tmod:@turbot/aws-elasticbeanstalk#/policy/types/elasticBeanstalkApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Environment > Approved > Usage
Determine whether the AWS Elastic Beanstalk environment is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Elastic Beanstalk environment is not approved, it will be subject to the action specified in the AWS > Elastic Beanstalk > Environment > Approved policy.
See Approved for more information.
[ "Not approved", "Approved", "Approved if AWS > Elastic Beanstalk > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if AWS > Elastic Beanstalk > Enabled" ], "example": [ "Not approved" ], "default": "Approved if AWS > Elastic Beanstalk > Enabled"}
AWS > Elastic Beanstalk > Environment > CMDB
Configure whether to 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 Turbot CMDB. All policies and controls in Turbot are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
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 > Environment > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Elastic Beanstalk > Environment > Regions
A list of AWS regions in which AWS Elastic Beanstalk environments are supported for use.
Any environments in a region not listed here will not be recorded in CMDB.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
"{\n regions: policyValue(uri:\"tmod:@turbot/aws-elasticbeanstalk#/policy/types/elasticBeanstalkRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Environment > Tags
Ensure AWS Elastic Beanstalk environment tags include tags defined in Environment Tags Template. Tags not defined in Environment Tags Template will not be modified or deleted. Setting a tag value to undefined will result in the tag being deleted.
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Tags > Template
This template is used to generate the keys and values for AWS Elastic Beanstalk environment tags.
"{\n item: environment {\n turbot {\n tags\n }\n }\n}\n"
"{}"
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.
[ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit"]
{ "type": "string", "enum": [ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit" ], "example": [ "Check: Usage <= 85% of Limit" ], "default": "Skip"}
AWS > Elastic Beanstalk > Environment > Usage > Limit
Maximum number of items that can be created.
{ "type": "integer", "minimum": 0, "default": 200}
AWS > Elastic Beanstalk > Permissions
Configure whether permissions policies are in effect for AWS Elastic Beanstalk.
This setting does not affect account level permissions (AWS/Admin, AWS/Owner, etc)
Note: The behavior of this policy depends on the value of AWS > Permissions.
[ "Enabled", "Disabled", "Enabled if AWS > Elastic Beanstalk > Enabled & AWS > Elastic Beanstalk > API Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Elastic Beanstalk > Enabled & AWS > Elastic Beanstalk > API Enabled" ], "example": [ "Enabled" ], "default": "Enabled if AWS > Elastic Beanstalk > Enabled & AWS > Elastic Beanstalk > API Enabled"}
AWS > Elastic Beanstalk > Permissions > Levels
Define the permissions levels that can be used to grant access to an AWS account. Permissions levels defined will appear in the UI to assign access to Turbot users. This policy provides a default for Permissions > Levels in each service, however you can explicitly override the setting for each service if desired
[ "{\n item: account {\n turbot{\n id\n }\n }\n}\n", "{\n availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyType:'tmod:@turbot/aws-iam#/policy/types/permissionsLevelsDefault'\") {\n items {\n value\n }\n }\n}\n"]
"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"
{ "type": "array", "items": { "type": "string", "enum": [ "Metadata", "ReadOnly", "Operator", "Admin", "Owner" ] }}
AWS > Elastic Beanstalk > Permissions > Levels > Modifiers
A map of AWS API to Turbot Permission Level used to customize Turbot's standard permissions. You can add, remove or redefine the mapping of AWS API operations to Turbot permissions levels here.
Note: Modifiers are cumulative - if you add a permission to the Metadata level, it is also added to ReadOnly, Operator and Admin. Modifier policies set here apply ONLY to the AWS level
example: - "glacier:createvault": admin - "glacier:ListVaults": metadata - "s3:DeleteBucket": none
AWS > Elastic Beanstalk > Permissions > Lockdown
AWS > Elastic Beanstalk > Permissions > Lockdown > API Boundary
Configure whether the AWS elasticBeanstalk API is enabled for all users and roles in turbot-managed boundary policies.
Note: Disabling the service disables the API for ALL users and roles, and Turbot will have no access to the API.
[ "Enabled if AWS > Elastic Beanstalk > API Enabled"]
{ "type": "string", "enum": [ "Enabled if AWS > Elastic Beanstalk > API Enabled" ], "example": [ "Enabled if AWS > Elastic Beanstalk > API Enabled" ], "default": "Enabled if AWS > Elastic Beanstalk > API Enabled"}
AWS > Elastic Beanstalk > Regions
A list of AWS regions in which AWS Elastic Beanstalk resources are supported for use.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
This policy is the default value for all AWS Elastic Beanstalk resources' Regions policies.
"{\n regions: policyValue(uri:\"tmod:@turbot/aws#/policy/types/regionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Elastic Beanstalk > Tags Template [Default]
A template used to generate the keys and values for AWS resources.
By default, all resource Tags > Template policies will use this value.
"{\n defaultTags: policyValue(uri:\"tmod:@turbot/aws#/policy/types/defaultTagsTemplate\") {\n value\n }\n}\n"
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-elasticbeanstalk
AWS CloudWatch Events event sources for the Turbot Event Handlers.
{ "type": "array", "items": { "type": "string" }, "default": [ "aws.elasticbeanstalk" ]}
AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-elasticbeanstalk
A read-only policy generated by Turbot that lists the APIs that
should be added to the turbot-managed (hard) boundary policy,
thereby enabling them to be assigned to users and roles.
This value will change depending on the value of the value of the
AWS > Elastic Beanstalk > Permissions > Lockdown > API Boundary
policy
{ "type": "array"}
AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-elasticbeanstalk
A calculated policy that Turbot uses to create a compiled list of ALL permissions for AWS Elastic Beanstalk that is used as input to the stack that manages the Turbot IAM permissions objects.
AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-elasticbeanstalk
A calculated policy that Turbot uses to create a compiled list of ALL permissions for AWS Elastic Beanstalk that is used as input to the control that manages the IAM stack.