Product logo
DocsBlogPricing

@turbot/aws-ecr

The aws-ecr mod contains resource, control and policy definitions for AWS ECR service.

Version
5.13.0
Released On
Mar 19, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.13.0 (2024-03-19)

Control Types

  • AWS > ECR > Repository > Policy
  • AWS > ECR > Repository > Policy > Required

Policy Types

  • AWS > ECR > Repository > Policy
  • AWS > ECR > Repository > Policy > Required
  • AWS > ECR > Repository > Policy > Required > Items

Action Types

  • AWS > ECR > Repository > Update Repository policy

5.12.0 (2023-09-01)

What's new?

  • Rebranded to a Turbot Guardrails Mod. To maintain compatibility, none of the existing resource types, control types or policy types have changed, your existing configurations and settings will continue to work as before.

5.11.0 (2023-07-12)

What's new?

  • README.md file is now available for users to check details about the resource types and service permissions that the mod covers.

Bug fixes

  • 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.

Control Types

  • AWS > ECR > Private Registry > Scanning Configuration

Policy Types

  • AWS > ECR > Private Registry > Scanning Configuration
  • AWS > ECR > Private Registry > Scanning Configuration > Continuous Filters
  • AWS > ECR > Private Registry > Scanning Configuration > Scan on Push Filters

Action Types

  • AWS > ECR > Private Registry > Update Scanning Configuration

5.10.0 (2023-05-17)

Resource Types

  • AWS > ECR > Private Registry

Control Types

  • AWS > ECR > Private Registry > CMDB
  • AWS > ECR > Private Registry > Discovery

Policy Types

  • AWS > ECR > Private Registry > CMDB
  • AWS > ECR > Private Registry > Regions

Action Types

  • AWS > ECR > Private Registry > Router

5.9.2 (2023-02-15)

Bug fixes

  • The AWS > ECR > Public Repository > Discovery control will now be skipped for China cloud accounts because Public Repositories are not supported in China cloud.

5.9.1 (2023-02-13)

Bug fixes

  • The AWS > ECR > Public Repository > Discovery control would go into an error state for US Government cloud and China cloud accounts due to incorrect endpoints being used to fetch Public Repository metadata. The China cloud endpoint is fixed and the control will now work as expected. For US Gov cloud accounts, the control will be set to skipped because Public Repositories are not supported in US Gov cloud.

5.9.0 (2023-01-06)

Resource Types

  • AWS > ECR > Public Repository

Control Types

  • AWS > ECR > Public Repository > Active
  • AWS > ECR > Public Repository > Approved
  • AWS > ECR > Public Repository > CMDB
  • AWS > ECR > Public Repository > Discovery
  • AWS > ECR > Public Repository > Tags
  • AWS > ECR > Public Repository > Usage

Policy Types

  • AWS > ECR > Public Repository > Active
  • AWS > ECR > Public Repository > Active > Age
  • AWS > ECR > Public Repository > Active > Budget
  • AWS > ECR > Public Repository > Active > Last Modified
  • AWS > ECR > Public Repository > Approved
  • AWS > ECR > Public Repository > Approved > Budget
  • AWS > ECR > Public Repository > Approved > Custom
  • AWS > ECR > Public Repository > Approved > Usage
  • AWS > ECR > Public Repository > CMDB
  • AWS > ECR > Public Repository > Tags
  • AWS > ECR > Public Repository > Tags > Template
  • AWS > ECR > Public Repository > Usage
  • AWS > ECR > Public Repository > Usage > Limit

Action Types

  • AWS > ECR > Image > Skip alarm for approved control
  • AWS > ECR > Image > Skip alarm for approved control [90 days]
  • AWS > ECR > Public Repository > Delete
  • AWS > ECR > Public Repository > Delete from AWS
  • AWS > ECR > Public Repository > Router
  • AWS > ECR > Public Repository > Set Tags
  • AWS > ECR > Public Repository > Skip alarm for Active control
  • AWS > ECR > Public Repository > Skip alarm for Active control [90 days]
  • AWS > ECR > Public Repository > Skip alarm for Approved control
  • AWS > ECR > Public Repository > Skip alarm for Approved control [90 days]
  • AWS > ECR > Public Repository > Skip alarm for Tags control
  • AWS > ECR > Public Repository > Skip alarm for Tags control [90 days]
  • AWS > ECR > Public Repository > Update Tags
  • AWS > ECR > Repository > Skip alarm for approved control
  • AWS > ECR > Repository > Skip alarm for approved control [90 days]

5.8.0 (2022-03-02)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • Repository policy details on a Repository did not update automatically in Guardrails CMDB via real-time event handling. This is now fixed.
  • We've improved the process of deleting resources from Guardrails if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Guardrails' IAM role while deleting resources from Guardrails. This will allow the CMDB controls to process resource deletions from Guardrails more reliably than before.

Policy Types

  • AWS > ECR > Image > Approved > Custom
  • AWS > ECR > Repository > Approved > Custom

5.7.0 (2021-07-07)

What's new?

  • We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an 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.

5.6.0 (2021-06-23)

Control Types

  • AWS > ECR > Repository > Scan on Push

Policy Types

  • AWS > ECR > Repository > Scan on Push

Action Types

  • AWS > ECR > Repository > Update Scan on Push

5.5.0 (2021-06-07)

Policy Types

  • AWS > ECR > Repository > Approved > Encryption at Rest
  • AWS > ECR > Repository > Approved > Encryption at Rest > Customer Managed Key

5.4.1 (2021-04-19)

Bug fixes

  • The AWS > ECR > Image > CMDB control would go into an error state if there were no imageTags on the image. This is now fixed.

5.4.0 (2021-04-12)

Resource Types

  • AWS > ECR > Image

Control Types

  • AWS > ECR > Image > Active
  • AWS > ECR > Image > Approved
  • AWS > ECR > Image > CMDB
  • AWS > ECR > Image > Discovery
  • AWS > ECR > Image > Usage

Policy Types

  • AWS > ECR > Image > Active
  • AWS > ECR > Image > Active > Age
  • AWS > ECR > Image > Active > Last Modified
  • AWS > ECR > Image > Approved
  • AWS > ECR > Image > Approved > Regions
  • AWS > ECR > Image > Approved > Usage
  • AWS > ECR > Image > CMDB
  • AWS > ECR > Image > Regions
  • AWS > ECR > Image > Usage
  • AWS > ECR > Image > Usage > Limit

Action Types

  • AWS > ECR > Image > Delete
  • AWS > ECR > Image > Router

5.3.3 (2020-12-24)

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.3.2 (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.3.1 (2020-09-04)

Bug fixes

  • The policyText and lifecyclePolicyText field for repository resources are now properly and consistently sorted.

5.3.0 (2020-09-01)

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] to Regions to be consistent with our other regions policies.

5.2.1 (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.2.0 (2020-08-06)

What's new?

  • We've improved our event handling configuration and now filter which AWS events Guardrails listens for based on resources' CMDB policies. If a resource's CMDB policy is not set to Enforce: Enabled, the EventBridge rules will be configured to not send any events for that resource. This will greatly reduce the number of unnecessary events that Guardrails listens for and handles today.

Policy Types

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-ecr

Removed

  • AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-ecr

5.1.2 (2020-07-01)

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.1.1 (2020-06-12)

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.1.0 (2020-05-15)

What's new?

  • Updated AWS > ECR > Regions policy default value to now include af-south-1, eu-south-1 .

Bug fixes

  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.