@turbot/aws-glacier
The aws-glacier mod contains resource, control and policy definitions for AWS Glacier service.
- Setting Policies Tutorial
- Mods Overview
- Policies Overview
- Resources Overview
- Common Policies and Controls
Recommended Version
Resource Types
Control Types
- AWS > Glacier > Vault > Active
- AWS > Glacier > Vault > Approved
- AWS > Glacier > Vault > CMDB
- AWS > Glacier > Vault > Discovery
- AWS > Glacier > Vault > Policy
- AWS > Glacier > Vault > Policy > Trusted Access
- AWS > Glacier > Vault > Tags
- AWS > Glacier > Vault > Usage
Policy Types
- AWS > Glacier > API Enabled
- AWS > Glacier > Approved Regions [Default]
- AWS > Glacier > Enabled
- AWS > Glacier > Permissions
- AWS > Glacier > Permissions > Levels
- AWS > Glacier > Permissions > Levels > Modifiers
- AWS > Glacier > Permissions > Lockdown
- AWS > Glacier > Permissions > Lockdown > API Boundary
- AWS > Glacier > Regions
- AWS > Glacier > Tags Template [Default]
- AWS > Glacier > Trusted Accounts [Default]
- AWS > Glacier > Trusted Organizations [Default]
- AWS > Glacier > Vault > Active
- AWS > Glacier > Vault > Active > Age
- AWS > Glacier > Vault > Active > Last Modified
- AWS > Glacier > Vault > Approved
- AWS > Glacier > Vault > Approved > Custom
- AWS > Glacier > Vault > Approved > Regions
- AWS > Glacier > Vault > Approved > Usage
- AWS > Glacier > Vault > CMDB
- AWS > Glacier > Vault > Policy
- AWS > Glacier > Vault > Policy > Trusted Access
- AWS > Glacier > Vault > Policy > Trusted Access > Accounts
- AWS > Glacier > Vault > Policy > Trusted Access > Organization Restrictions
- AWS > Glacier > Vault > Regions
- AWS > Glacier > Vault > Tags
- AWS > Glacier > Vault > Tags > Template
- AWS > Glacier > Vault > Usage
- AWS > Glacier > Vault > Usage > Limit
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-glacier
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-glacier
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-glacier
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-glacier
Release Notes
5.6.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 > Glacier > Vault > Approved > Custom
Action Types
- AWS > Glacier > Vault > Delete from AWS
- AWS > Glacier > Vault > Set Tags
- AWS > Glacier > Vault > Skip alarm for Active control
- AWS > Glacier > Vault > Skip alarm for Active control [90 days]
- AWS > Glacier > Vault > Skip alarm for Approved control
- AWS > Glacier > Vault > Skip alarm for Approved control [90 days]
- AWS > Glacier > Vault > Skip alarm for Tags control
- AWS > Glacier > Vault > Skip alarm for Tags control [90 days]
5.5.1 (2020-12-17)
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.5.0 (2020-10-19)
What's new?
Cross-account trust is not only important for complex enterprise and application scenarios but is also a critical area for security controls. We now support controlling cross-account access for vaults to provide automatic protection against unexpected cross-account access.
A common set of trusted AWS account IDs can be defined in the
AWS > Account > Trusted Accounts [Default]
policy. Trusted accounts can also be defined at any level, even down to the specific vault resource.To get started with these new controls, please see the
AWS > Glacier > Vault > Policy > Trusted Access
policy.
Control Types
- AWS > Glacier > Vault > Policy
- AWS > Glacier > Vault > Policy > Trusted Access
Policy Types
- AWS > Glacier > Trusted Accounts [Default]
- AWS > Glacier > Trusted Organizations [Default]
- AWS > Glacier > Vault > Policy
- AWS > Glacier > Vault > Policy > Trusted Access
- AWS > Glacier > Vault > Policy > Trusted Access > Accounts
- AWS > Glacier > Vault > Policy > Trusted Access > Organization Restrictions
Action Types
- AWS > Glacier > Vault > Set Policy Trusted Access
5.4.1 (2020-09-21)
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.4.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.3.4 (2020-08-11)
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.3.3 (2020-07-22)
Bug fixes
AWS/Glacier/Admin
now includes vault lock management permissions.
5.3.2 (2020-07-06)
Bug fixes
- Updated various resource configurations to provide better compatibility with AWS China regions.
5.3.1 (2020-06-18)
Bug fixes
- The vault
Policy
property was not available for use in GraphQL queries. This has been fixed.
5.3.0 (2020-06-18)
What's new?
- Vault access policy information is now available in the
Policy
attribute.
5.2.1 (2020-06-11)
What's new?
- All resource Router actions now run even if Guardrails is outside of its allowed change window. This allows Guardrails to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Guardrails' ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.
5.2.0 (2020-05-14)
What's new?
- Updated
AWS > Glacier > Regions
policy default value to now includeaf-south-1
,ap-east-1
,eu-north-1
,eu-south-1
,me-south-1
.
Bug fixes
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.