aws.vpc-lattice-rule

VPC Lattice listener rule resource.

Rules are enumerated through listeners and require both serviceIdentifier and listenerIdentifier for direct API queries. This resource supports a custom query block with those keys to narrow enumeration before filters are applied.

If only serviceIdentifier is provided in the query, Custodian will enumerate listeners for that service and then list rules for each listener. If both identifiers are provided, Custodian queries the rule API directly. A query with listenerIdentifier alone is rejected because the VPC Lattice API also requires the parent service identifier.

example:

policies:
  - name: lattice-rule-by-service
    resource: aws.vpc-lattice-rule
    query:
      - serviceIdentifier: svc-0123456789abcdef0
    filters:
      - isDefault: false

  - name: lattice-rule-by-service-and-listener
    resource: aws.vpc-lattice-rule
    query:
      - serviceIdentifier: svc-0123456789abcdef0
      - listenerIdentifier: listener-0123456789abcdef0
    filters:
      - type: value
        key: priority
        value: 10

Filters

event

finding

list-item

marked-for-op

ops-item

reduce

value

Actions

auto-tag-user

copy-related-tag

invoke-lambda

invoke-sfn

mark-for-op

notify

post-finding

post-item

put-metric

remove-tag

rename-tag

tag

webhook

rename-tag

Rename an existing tag key to a new value.

example:

rename Application, and Bap to App, if a resource has both of the old keys then we’ll use the value specified by Application, which is based on the order of values of old_keys.

policies:
- name: rename-tags-example
  resource: aws.log-group
  filters:
    - or:
      - "tag:Bap": present
      - "tag:Application": present
  actions:
    - type: rename-tag
      old_keys: [Application, Bap]
      new_key: App

properties:
  new_key:
    type: string
  old_key:
    type: string
  old_keys:
    items:
      type: string
    type: array
  type:
    enum:
    - rename-tag
required:
- type

Permissions - tag:TagResources, tag:UntagResources