RATATOSK
← All releases

Cloud Custodian0.9.48.0

Breaking changes 13Important fixes 9Enhancements 47Dependency updates 6Other changes 12

Get Cloud Custodian alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Breaking changes13

Firehose delete action now attempts deletion of suspended streams

AffectsAWS Firehose delivery streams in SUSPENDED status

Previously, the action skipped suspended streams; only streams in ACTIVE status passed its status check for deletion.

Show release-note lines
 - aws - firehose - delete action add support for suspended streams (#10397)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

GuardDuty administrator-account lookup uses Administrator

AffectsAWS GuardDuty policies using administrator-account attributes in the guard-duty filter(Inferred)

When the filter fetched administrator-account data, the API returned Administrator while the old lookup queried Master, so the data was not retrieved under the expected key. The filter now reads Administrator and stores it under that key in the c7n:guard-duty annotation.

Evidence“The `get_administrator_account` API returns an `Administrator` key, not `Master`.” cloud-custodian/cloud-custodian/pull/10376 ↗
Show release-note lines
 - fix(guardduty): use correct key for administrator account (#10376)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

TencentCloud loads credentials from the selected profile

AffectsTencentCloud setups using --profile with profiles in ~/.tencentcloud/credentials(Inferred)

If the credentials file is absent or the requested profile is not found, the release raises an exception.

Evidence“+ raise TencentCloudSDKException( + "Credentials file not found: %s" % config_path + )” cloud-custodian/cloud-custodian/pull/10337 ↗
Show release-note lines
 - tencentcloud: fix metrics service name, enforce batching limits, and annotate resources with metrics (#10337)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

Directory queries use list_directories-style key-value pairs

AffectsAWS Directory policies with server-side query parameters

Queries using the old Name, Values list format were sent under Filters and raised a boto3 ParamValidationError. The name and directoryArn query parameters are no longer supported.

Evidence“For Directories, name and directoryArn are not valid query parameters. They're from the API response, so they were removed. Additionally, directory queries are bugged in their current implementation as they are placed under a 'Filters' key which causes boto3 to throw `botocore.exceptions.ParamValidationError: Parameter validation failed: Unknown parameter in input: "Filters", must be one of: NextToken, MaxResults, state`, so the current version of directory queries as a list of "Name", "Values" dictionaries will no longer be supported in favor of key value pairs to mirror the list_directories API structure.” cloud-custodian/cloud-custodian/pull/10388 ↗
Show release-note lines
 - aws - core - consolidated query parsing (#10388)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

EBS Volume query parameters now use string enums

AffectsAWS EBS Volume policies with server-side boolean query parameters

Previously, these parameters were treated as booleans; their accepted values are now the strings true and false.

Evidence“Integrated recent implementation for EBS Volume queries which use the same format as EBS Snapshots. Small breaking change to correct the type of the boolean query params. They are not true booleans. They are string enums with values or 'true' or 'false'” cloud-custodian/cloud-custodian/pull/10388 ↗
Show release-note lines
 - aws - core - consolidated query parsing (#10388)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

FSx delete actions now propagate deletion errors

AffectsFSx delete actions

When a deletion call raised BadRequest, the action previously logged a warning and suppressed the exception, so it could finish without surfacing the failure. Now any deletion exception, including BadRequest, is logged as an error and propagated.

Evidence“except Exception as e:” cloud-custodian/cloud-custodian/pull/10391 ↗
Show release-note lines
 - aws - fsx - delete-file-system support other fsx types (#10391)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

Schedule-mode Lambda target ARNs no longer retain version or alias qualifiers

AffectsAWS schedule-mode policies with version- or alias-qualified Lambda function ARNs(Inferred)

Previously, a schedule target ARN could include the Lambda version at the end.

Evidence“When running `custodian run` with a policy that is a schedule, the resulting schedule target ARN can be fully qualified with the version at the end” cloud-custodian/cloud-custodian/pull/10407 ↗
Show release-note lines
 - aws - schedule mode - strip version from eventbridge schedule target arn (#10407)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

Azure workload identity authentication support added

AffectsAzure setups configured with AZURE_FEDERATED_TOKEN_FILE
Action requiredThe azure-identity dependency must be at least 1.13.0 and below 2.0.0 before upgrading.

Previously, Azure sessions did not include federated-token-file authentication.

Show release-note lines
 - azure - AKS / ACI Azure Container Host Enhancements (#10395)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

opswork-stack lookup and actions disabled

Affectspolicies using the opswork-stack resource(Inferred)

Previously, the resource queried OpsWorks stacks, and its delete and stop actions called the OpsWorks API to delete or stop them.

Evidence“"""OpsWorks Stack is no longer an available service. This resource” cloud-custodian/cloud-custodian/pull/10383 ↗
Show release-note lines
 - releng - 2025/10 increment versions and update dependencies (#10383)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

opswork-cm returns no resources and delete has no effect

Affectspolicies using the opswork-cm resource or its delete action(Inferred)

Previously, the resource queried OpsWorks CM servers, and delete called the OpsWorks CM API to delete them.

Evidence“"""OpsWorks CM is no longer an available service. This resource” cloud-custodian/cloud-custodian/pull/10383 ↗
Show release-note lines
 - releng - 2025/10 increment versions and update dependencies (#10383)
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

metrics filter removed from the gcp.spanner-database-instance schema

Affectssetups using the gcp.spanner-database-instance schema, especially configurations or validators that reference metrics(Inferred)
Show release-note lines
- `gcp.spanner-database-instance`
  - removed filters: `metrics`
github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

Important fixes9

  • EBS volume retrieval pagination fixed
    AffectsAWS EBS volume retrieval using DescribeVolumes

    When policies ran in accounts with many EBS volumes, client-side filtering could cause timeouts; DescribeVolumes also did not paginate unless maxResults was explicitly passed. Retrieval now passes MaxResults 1000 to fetch volumes across multiple API calls.

     - aws - ebs - add Server-Side Query Filtering  (#10393)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • AWS SSM document cross-account filter honors everyone_only
    AffectsAWS SSM document cross-account filter with everyone_only: true

    Previously, the filter considered shared-account entries without applying this restriction. Now only documents shared with all are selected as cross-account violations; the default-false behavior is unchanged.

     - aws - ssm-document - support everyone-only in cross-account filter (#10413)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • Artifact domain cross-account filter name lookup fixed
    AffectsPolicies using the cross-account filter on aws.artifact-domain resources(Inferred)

    When evaluating the filter, it looked for the domain name under domainName, although the name is in name. It now uses name to retrieve the domain permissions policy for evaluation.

     - aws - artifact-domain - fix cross account filter (#10446)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • Comprehend cross-account filter skips resources without policies
    AffectsAWS Comprehend cross-account filters for entity recognizers or document classifiers

    Previously, scanning these resources without policies could raise KeyError: 'ResourcePolicy' and stop execution. Now, scanning can continue past resources without a ResourcePolicy key.

     - Fixing KeyError in Comprehend cross-account filter when resource has no policy (#10355)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • azure.keyvault-key policy filter fixed
    Affectspolicies using the azure.keyvault-key filter(Inferred)

    An incompatible SDK update affected the filter. The test changed its property path from attributes.enabled to attributes.data.enabled.

     - azure - azure.keyvault-key: fix policy filter due to incompatible sdk update (#10368)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • GCP Spanner metrics filtering support added
    AffectsGCP Spanner instance resources using the metrics filter(Inferred)

    Previously, the metrics filter could error because get_metric_resource_name was not universally available.

     - gcp - update metric support for spanner resources (#10374)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • Kubernetes PatchAction handles deleted-resource 404s gracefully
    AffectsKubernetes PatchAction patch operations

    When a resource is deleted during policy execution and a patch operation encounters a 404, the error is handled gracefully.

     - kubernetes - enhanced PatchAction with save/restore functionality and improved error handling (#10288)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • TencentCloud metrics filter Monitor client service name corrected
    Affectssetups using the TencentCloud metrics filter(Inferred)

    Requests through its Monitor API client used the incorrect service name service, resulting in request failures. The client now uses monitor, reducing those failures.

     - tencentcloud: fix metrics service name, enforce batching limits, and annotate resources with metrics (#10337)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0
  • TencentCloud metrics request batching limits fixed
    AffectsTencentCloud metrics filters(Inferred)

    Previously, batch size was calculated from the 1,440-data-point limit alone, without enforcing the separate 10-instance limit.

     - tencentcloud: fix metrics service name, enforce batching limits, and annotate resources with metrics (#10337)
    github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0

Enhancements47

Dependency updates6

    6 more, none mentioning security
    • - azure - update azure mgmt keyvault version (#10352)
    • - azure - update azure mgmt security version (#10351)
    • - releng - 2025/10 increment versions and update dependencies (#10383)
    • - releng - :seedling: bump github-actions group across 4 directories with 12 updates (#10410)
    • - releng - azure - update azure-mgmt-sql to 3.x (#10421)
    • - releng - update dependencies 2025/11 (#10417)
    Other changes12

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.