@turbot/aws-elasticbeanstalk
The aws-elasticbeanstalk mod contains resource, control and policy definitions for AWS Elastic Beanstalk service.
- Setting Policies Tutorial
- Mods Overview
- Policies Overview
- Resources Overview
- Common Policies and Controls
Recommended Version
Resource Types
Control Types
- 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
Policy Types
- 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 > Custom
- 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
Release Notes
5.3.0 (2023-11-03)
What's new?
We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.
Resource's metadata will now also include
createdBy
details in Turbot CMDB.Users can now perform quick actions on resources to remediate cloud configuration issues or skip Turbot alarms for issues that they want to come back to later. To get started, click on the
Actions
button, which will reveal a dropdown menu with available actions, and select one. See Quick Actions for more information.
Policy Types
- AWS > Elastic Beanstalk > Application > Approved > Custom
Action Types
- AWS > Elastic Beanstalk > Application > Delete from AWS
- AWS > Elastic Beanstalk > Application > Set Tags
- AWS > Elastic Beanstalk > Application > Skip alarm for Active control
- AWS > Elastic Beanstalk > Application > Skip alarm for Active control [90 days]
- AWS > Elastic Beanstalk > Application > Skip alarm for Approved control
- AWS > Elastic Beanstalk > Application > Skip alarm for Approved control [90 days]
- AWS > Elastic Beanstalk > Application > Skip alarm for Tags control
- AWS > Elastic Beanstalk > Application > Skip alarm for Tags control [90 days]
5.2.0 (2021-04-16)
What's new?
- We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.
Bug fixes
The
AWS > Elastic Beanstalk > Environment > Approved
control will now not attempt to delete an environment if the environment'sStatus
is notReady
.For an application that had a version deployed to a running environment, the
AWS > Elastic Beanstalk > Application > Approved
control would incorrectly try to delete that application if theAWS > Elastic Beanstalk > Application > Approved
policy was set toEnforce: Delete unapproved if new
. This is now fixed.
5.1.2 (2021-01-13)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
states thanks to the new Guardrails Precheck feature (not to be confused with TSA PreCheck). With Guardrails Precheck, controls avoid running GraphQL input queries when intbd
andskipped
, resulting in faster and lighter control runs.
5.1.1 (2020-10-16)
Bug fixes
- We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.
5.1.0 (2020-09-02)
What's new?
- Discovery controls now have their own control category,
CMDB > Discovery
, to allow for easier filtering separately from other CMDB controls. - We've renamed the service's default regions policy from
Regions [Default]
toRegions
to be consistent with our other regions policies.
5.0.4 (2020-08-13)
Bug fixes
- In various Active controls, we were outputting log messages that did not properly show how many days were left until we'd delete the inactive resources (we were still deleting them after the correct number of days). These log messages have been fixed and now contain the correct number of days.
5.0.3 (2020-07-07)
Bug fixes
- Sometimes when updating CMDB for resources with tags that have empty string values, e.g.,
[{Key: "Empty", Value: ""}, {Key: "Turbot is great", Value: "true"}]
, we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.
5.0.2 (2020-05-29)
Bug fixes
- Deleting an Elastic Beanstalk application from the AWS console did not remove it from the CMDB. This issue has now been fixed.
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.