aws.cache-snapshot

Filters

• age

• event

• finding

• list-item

• marked-for-op

• ops-item

• reduce

• tag-count

• value

age

Filters elasticache snapshots based on their age (in days)

example:

policies:
  - name: elasticache-stale-snapshots
    resource: cache-snapshot
    filters:
      - type: age
        days: 30
        op: ge

properties:
  days:
    type: number
  op:
    enum:
    - eq
    - equal
    - ne
    - not-equal
    - gt
    - greater-than
    - ge
    - gte
    - le
    - lte
    - lt
    - less-than
    - glob
    - regex
    - regex-case
    - in
    - ni
    - not-in
    - contains
    - difference
    - intersect
    - mod
  type:
    enum:
    - age
required:
- type

Actions

• auto-tag-user

• copy-cluster-tags

• copy-related-tag

• delete

• invoke-lambda

• invoke-sfn

• mark-for-op

• notify

• post-finding

• post-item

• put-metric

• remove-tag

• rename-tag

• tag

• webhook

copy-cluster-tags

Copy specified tags from Elasticache cluster to Snapshot :example:

- name: elasticache-test
  resource: cache-snapshot
  filters:
     - type: value
       key: SnapshotName
       op: in
       value:
        - test-tags-backup
  actions:
    - type: copy-cluster-tags
      tags:
        - tag1
        - tag2

properties:
  tags:
    items:
      type: string
    minItems: 1
    type: array
  type:
    enum:
    - copy-cluster-tags
required:
- tags

Permissions - elasticache:DescribeCacheClusters, tag:GetResources, elasticache:ListTagsForResource, elasticache:ListTagsForResource, elasticache:AddTagsToResource

delete

Action to delete elasticache snapshots

To prevent unwanted deletion of elasticache snapshots, it is recommended to apply a filter

example:

policies:
  - name: delete-elasticache-stale-snapshots
    resource: cache-snapshot
    filters:
      - type: age
        days: 30
        op: ge
    actions:
      - delete

properties:
  type:
    enum:
    - delete
required:
- type

Permissions - elasticache:DeleteSnapshot

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