Lambda delete event source mapping

Last updated on Jun 10, 2026

Lambda delete event source mapping is an AWS chaos fault that deletes one or more event source mappings (identified by UUIDs in EVENT_UUIDS) on a target Lambda function (FUNCTION_NAME in REGION) for TOTAL_CHAOS_DURATION seconds, then recreates the mappings with the original configuration.

Use this fault to test how an event-driven Lambda workload behaves when its event source (SQS queue, Kinesis stream, DynamoDB Stream, Kafka topic, MSK cluster, MQ broker) is disconnected: whether events back up in the source, whether dead-letter and retry policies behave correctly, and whether monitoring detects the disconnection within the SLA.

Run your first experiment

If you have not configured the chaos infrastructure yet, go to Quickstart to install the chaos infrastructure and run an experiment end to end.

Use cases

Run this fault when you want to answer concrete questions like:

Event backlog handling: When the mapping is deleted, do events accumulate in the source (SQS queue depth grows, Kinesis records age) without loss?
Recovery on reattach: When the mapping is recreated, does the function drain the backlog within the expected window?
Monitoring fidelity: Do CloudWatch alarms on iterator age, queue depth, or "no invocations" fire within the SLA?
Downstream impact: Do consumers downstream of the Lambda function detect the gap and degrade gracefully?
Idempotency: When the function eventually processes the backlog, are messages handled idempotently?

Prerequisites

Kubernetes version: 1.21 or later for the chaos infrastructure cluster. Go to What's supported to confirm distribution support.
Target Lambda function: FUNCTION_NAME exists in REGION and is in the Active state.
Event source mappings: Each UUID in EVENT_UUIDS is currently attached to the function and in the Enabled state.
AWS credentials available: Either an AWS credentials file uploaded as a File Secret in Harness Secret Manager (see Authentication below) or an IAM role for service accounts (IRSA) bound to the chaos infrastructure service account.
IAM permissions granted: The credentials or role include the permissions listed below.

Supported environments

Platform	Support status
Lambda event sources: SQS, Kinesis, DynamoDB Streams, MSK, self-managed Kafka, MQ	Supported
API Gateway, EventBridge rule, S3 notification triggers	Not applicable (these use invocations, not event source mappings)
AWS regions	Supported in every commercial region; pass the region in `REGION`

Permissions required

The IAM principal that the chaos pod uses (the credentials mounted from the Harness Secret Manager file secret, the IRSA role on the chaos service account, or the role assumed via ASSUME_ROLE_ARN) needs the following AWS actions.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "lambda:GetFunction",
        "lambda:GetEventSourceMapping",
        "lambda:ListEventSourceMappings",
        "lambda:CreateEventSourceMapping",
        "lambda:DeleteEventSourceMapping",
        "lambda:UpdateEventSourceMapping"
      ],
      "Resource": "*"
    }
  ]
}

Go to common policy for all AWS faults to use a single superset IAM policy across every AWS fault.

Authentication

The fault supports three credential delivery models. Pick one based on how your chaos infrastructure is deployed.

Method	When to use it	How to configure
Harness Secret Manager file secret	Chaos infrastructure runs outside EKS, or you want explicit static credentials	Upload the AWS credentials file as a File Secret in Harness Secret Manager and reference its identifier via `AWS_AUTHENTICATION_SECRET`
IAM Roles for Service Accounts (IRSA)	Chaos infrastructure runs in EKS and uses an OIDC-bound service account	No tunable changes; the chaos pod inherits the role automatically. Go to AWS IAM integration to set it up
Assume role	The fault needs to act in a different account or with elevated permissions	Set `ASSUME_ROLE_ARN` to the role ARN; the chaos pod assumes the role on top of its base credentials

When using the Harness Secret Manager method, the contents of the File Secret should be the AWS credentials file in the standard ~/.aws/credentials format:

[default]
aws_access_key_id = REPLACE_WITH_ACCESS_KEY_ID
aws_secret_access_key = REPLACE_WITH_SECRET_ACCESS_KEY

Upload this file as a File Secret in Harness Secret Manager (Project Setup → Secrets → New File Secret), and pass the secret identifier in AWS_AUTHENTICATION_SECRET when configuring the fault.

Fault tunables

Configure the following fault parameters when you add Lambda delete event source mapping to an experiment in Chaos Studio. Defaults are shown for reference.

Required parameters

Tunable	Description	Default
`FUNCTION_NAME`	Name of the target Lambda function.	(required)
`REGION`	AWS region where the Lambda function is deployed.	(required)
`EVENT_UUIDS`	Comma-separated list of event source mapping UUIDs to delete. Use `aws lambda list-event-source-mappings` to enumerate them.	(required)

Chaos parameters

Tunable	Description	Default
`TOTAL_CHAOS_DURATION`	Duration of the fault in seconds.	`30`
`SEQUENCE`	Order in which multiple mappings are deleted: `parallel` deletes them all at once; `serial` deletes them one at a time.	`parallel`
`RAMP_TIME`	Wait period in seconds before and after the fault. Go to ramp time to read how it is applied.	`0`

Authentication

Tunable	Description	Default
`ASSUME_ROLE_ARN`	ARN of an IAM role to assume on top of the base credentials. Leave empty to use the base credentials directly.	`""`
`AWS_AUTHENTICATION_SECRET`	Identifier of the File Secret in Harness Secret Manager that contains the AWS credentials file. Not required when using IRSA.	`""`

Tunables that apply to every fault are documented in common tunables for all faults.

Fault execution in brief

Reads the current configuration of each event source mapping in EVENT_UUIDS, deletes the mappings, waits for TOTAL_CHAOS_DURATION seconds, then recreates the mappings with their original configuration.

Expected behavior during fault execution

The Lambda function stops receiving new events from the deleted mappings.
Events accumulate in the source: SQS queue depth grows, Kinesis records age increases, DynamoDB Stream iterator age rises.
CloudWatch Lambda invocation metrics drop to zero for the affected event source.
Downstream consumers of the Lambda output see a gap or backlog.

When the fault ends

The chaos pod recreates each mapping with the original configuration. The function resumes consuming events; the source backlog drains over the next several minutes depending on throughput.

Signals to watch

Attach resilience probes to assert each layer:

Source queue depth: Use a Prometheus probe on aws_sqs_approximate_number_of_messages_visible (SQS) or equivalent.
Iterator age: Use a Prometheus probe on aws_kinesis_get_records_iterator_age_milliseconds (Kinesis/DynamoDB Streams).
Lambda invocation rate: Use a Prometheus probe on aws_lambda_invocations_sum and assert it drops during the chaos window.
Downstream availability: Use an HTTP probe on the user-visible endpoint.

Verify the fault execution effect

While the experiment is running, confirm the mapping is deleted and then recreated:

List event source mappings.
```
aws lambda list-event-source-mappings \
  --region <region> \
  --function-name <name>
```
During the fault the deleted UUIDs should not be listed; after recovery they should be back with the original configuration.

Check source backlog.

For SQS:

aws sqs get-queue-attributes --region <region> --queue-url <url> \
  --attribute-names ApproximateNumberOfMessages

The depth should grow during the chaos window.

Verify recovery.

After the chaos window, queue depth should drain back toward baseline; iterator age should fall.

Recovery and cleanup

End of duration: The chaos pod recreates each deleted mapping with the original configuration.
Abort the experiment: Stopping the experiment from Chaos Studio also triggers the recreate call.
Manual recovery: If the fault exits before recreate, recreate each mapping with aws lambda create-event-source-mapping --function-name <name> --event-source-arn <arn> ... using the original parameters (recorded in the chaos pod logs).
Workload recovery: Backlog drains at the function's normal throughput rate; consider scaling up after a long chaos window.

Limitations

UUIDs change on recreate: When the chaos pod recreates a mapping, AWS assigns a new UUID. Automation that pins to the original UUID needs to refresh.
Concurrency and batch settings preserved: The fault captures and restores the original configuration, but custom changes made externally during the chaos window are overwritten.
Source-side TTL: Sources with a retention window shorter than the chaos duration (for example Kinesis streams with a low retention) may drop events permanently.
Cross-region targeting: A single experiment targets one region (the value of REGION).

Troubleshooting

Lambda delete event source mapping fails with AccessDeniedException in Harness Chaos Engineering

The credentials supplied to the chaos pod do not have the required Lambda permissions. Confirm the IAM policy attached to the user, role, or IRSA service account includes lambda:GetEventSourceMapping, lambda:CreateEventSourceMapping, lambda:DeleteEventSourceMapping, and lambda:UpdateEventSourceMapping.

EVENT_UUIDS not found

The UUIDs in EVENT_UUIDS must belong to the function specified in FUNCTION_NAME and exist in REGION. Enumerate the current mappings with 'aws lambda list-event-source-mappings --function-name <name> --region <region>' and copy the UUID values into EVENT_UUIDS.

Recreated mapping has different settings

The fault captures the original mapping configuration before deletion and restores it. If a setting like batch size, maximum batching window, or filter criteria was changed externally during the chaos window, the restore overwrites it. Coordinate the experiment with any other automation that may modify event source mappings.

Function does not drain the backlog after recovery

Lambda concurrency limits or reserved concurrency may cap drain throughput. Check the function's concurrency configuration, raise reserved concurrency temporarily, or accept a longer drain window.

Lambda toggle event mapping state: Disable mappings without deleting them.
Lambda update function memory: Test function behaviour under tightened memory.
Lambda update function timeout: Test function behaviour under tightened timeout.
Common AWS fault tunables: Shared environment variables for AWS faults.

Use cases​

Prerequisites​

Supported environments​

Permissions required​

Authentication​

Fault tunables​

Fault execution in brief​

Expected behavior during fault execution​

Signals to watch​

Verify the fault execution effect​

Recovery and cleanup​

Limitations​

Troubleshooting​

Related faults​