# Cloud Custodian 0.9.48.0

2025-12-01 · [Original release notes](https://github.com/cloud-custodian/cloud-custodian/releases/tag/0.9.48.0) · [Full summary](https://ratatosk.io/en/releases/cloud-custodian/0.9.48.0)

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

## Breaking changes (13)

### Firehose delete action now attempts deletion of suspended streams

- Affects: AWS Firehose delivery streams in `SUSPENDED` status

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

>  - aws - firehose - delete action add support for suspended streams (#10397)

### GuardDuty administrator-account lookup uses `Administrator`

- Affects: AWS 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`.” https://github.com/cloud-custodian/cloud-custodian/pull/10376

>  - fix(guardduty): use correct key for administrator account (#10376)

### TencentCloud loads credentials from the selected profile

- Affects: TencentCloud 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 + )” https://github.com/cloud-custodian/cloud-custodian/pull/10337

>  - tencentcloud: fix metrics service name, enforce batching limits, and annotate resources with metrics (#10337)

### Directory queries use `list_directories`-style key-value pairs

- Affects: AWS 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.” https://github.com/cloud-custodian/cloud-custodian/pull/10388

>  - aws - core - consolidated query parsing (#10388)

### EBS Volume query parameters now use string enums

- Affects: AWS 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'” https://github.com/cloud-custodian/cloud-custodian/pull/10388

>  - aws - core - consolidated query parsing (#10388)

### FSx delete actions now propagate deletion errors

- Affects: FSx 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:” https://github.com/cloud-custodian/cloud-custodian/pull/10391

>  - aws - fsx - delete-file-system support other fsx types (#10391)

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

- Affects: AWS 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” https://github.com/cloud-custodian/cloud-custodian/pull/10407

>  - aws - schedule mode - strip version from eventbridge schedule target arn (#10407)

### Azure workload identity authentication support added

- Affects: Azure setups configured with `AZURE_FEDERATED_TOKEN_FILE`
- Action required: The `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.

>  - azure - AKS / ACI Azure Container Host Enhancements (#10395)

### `opswork-stack` lookup and actions disabled

- Affects: policies 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” https://github.com/cloud-custodian/cloud-custodian/pull/10383

>  - releng - 2025/10 increment versions and update dependencies (#10383)

### `opswork-cm` returns no resources and `delete` has no effect

- Affects: policies 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” https://github.com/cloud-custodian/cloud-custodian/pull/10383

>  - releng - 2025/10 increment versions and update dependencies (#10383)

### `metrics` filter removed from `aws.opswork-stack`

- Affects: policies using the `metrics` filter with the `aws.opswork-stack` resource

> - `aws.opswork-stack`
>   - removed filters: `metrics`

### `metrics` filter removed from `gcp.spanner-backup` schema

- Affects: configurations or validators that check the `metrics` filter in the `gcp.spanner-backup` schema (Inferred)

> - `gcp.spanner-backup`
>   - removed filters: `metrics`

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

- Affects: setups using the `gcp.spanner-database-instance` schema, especially configurations or validators that reference `metrics` (Inferred)

> - `gcp.spanner-database-instance`
>   - removed filters: `metrics`

## Important fixes (9)

### EBS volume retrieval pagination fixed

- Affects: AWS 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)

### AWS SSM document `cross-account` filter honors `everyone_only`

- Affects: AWS 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)

### Artifact domain cross-account filter name lookup fixed

- Affects: Policies 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)

### Comprehend cross-account filter skips resources without policies

- Affects: AWS 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)

### `azure.keyvault-key` policy filter fixed

- Affects: policies 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)

### GCP Spanner metrics filtering support added

- Affects: GCP 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)

### Kubernetes `PatchAction` handles deleted-resource 404s gracefully

- Affects: Kubernetes `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)

### TencentCloud metrics filter Monitor client service name corrected

- Affects: setups 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)

### TencentCloud metrics request batching limits fixed

- Affects: TencentCloud 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)

## Enhancements (47)

- Account-wide AMI Block Public Access filtering
- Global AWS `iam-access-key` resource added
- Replica attribute filtering for AWS Secrets Manager
- `delete` action for AWS subnets
- ElastiCache `cache-cluster` upgrade-availability filter (To use: `elasticache:DescribeServiceUpdates` permission)
- Expanded AWS server-side query support
- Server-side query filtering for EBS volumes (To use: A `query` on the EBS (`ebs`) resource)
- FSx delete action adds force handling for dependencies and unavailable Lustre Scratch backups (To use: `force: True` on the FSx delete action)
- Configurable retry settings for FSx deletion (To use: Specify `retry-delay` and/or `retry-max-attempts` to override the defaults.)
- AWS Kafka `cross-account` resource-policy filter
- AWS Kafka compatible-version upgrade filter added
- AWS KMS `last-rotation` policy filter
- `lambda-event-source-mapping` resource added
- KMS key filtering for Lambda event source mappings
- Secrets Manager `current-version` filter
- Optional hard-limit support for service-quota usage metrics (To use: Configure the optional `hard_limit` parameter in the `usage-metric` filter.)
- WAFv2 `set-logging` action added (To use: A `destination` is required for the `set-logging` action.)
- VPC resolver query logging filter added
- Analytics association filter for Connect instances (To use: `analytics-association` filter in a `connect-instance` policy)
- AWS VPC Lattice resource and filter support
- `delete-listener` action for Application Load Balancers
- New `aws.elasticache-reserved` resource for querying reserved cache nodes
- Microsoft Graph support for the `azure.entraid-user` resource
- Azure Key Vault key property update action
- GCP Certificate Manager certificate resource added
- Kubernetes `PatchAction` state save and restore options (To use: `save-options-tag` and/or `restore-options-tag` parameters)
- TencentCloud metrics filter adds collected metrics to resources
- `aws.elasticache-reserved` resource schema added
- `aws.iam-access-key` resource schema added
- `aws.lambda-event-source-mapping` resource schema added
- `aws.vpc-lattice-service` resource schema added
- `aws.vpc-lattice-service-network` resource schema added
- VPC Lattice target group resource schema added
- EntraID user resource schema added
- `gcp.certmanager-certificate` resource schema added
- New `terraform._` resource schema
- `ami-block-public-access` filter added for AWS accounts
- ElastiCache `upgrade-available` filter added
- `analytics-association` filter added to `aws.connect-instance`
- Kafka cross-account permission filter
- Kafka `upgrade-available` filter added
- The `current-version` filter for `aws.secrets-manager`
- `aws.secrets-manager` `replica-attribute` filter added
- The `delete` action for `aws.subnet`
- VPC `resolver-query-logging` filter added
- WAFv2 Web ACL logging action added
- `update` action added for `azure.keyvault-key`

## Dependency updates (6)

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 changes (12)

- FSx delete action uses type-specific configuration
- Route 53 domain test fixtures use placeholder billing-contact details
- Detail spec added for the AWS Route 53 domain resource
- Azure container-host templates switch Python runtimes
- Project governance structure documented
- GCP Secret Manager resource documentation link updated
- Dependabot scans reusable workflow directories
- CI cache checks avoid spurious dependency installs
- CI install workflow saves cache after environment recreation
- GitHub Actions virtual-environment cache clearing command added
- AWSCC build script reports aggregate build statistics
- Consistent c7n_mailer template archive checksums

---

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