You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* <p>The following error handling options are available only for stream sources (DynamoDB and Kinesis):</p>
77
+
* <p>The following error handling options are available only for DynamoDB and Kinesis event sources:</p>
78
78
* <ul>
79
79
* <li>
80
80
* <p>
81
81
* <code>BisectBatchOnFunctionError</code> – If the function returns an error, split the batch in two and retry.</p>
82
82
* </li>
83
83
* <li>
84
84
* <p>
85
-
* <code>DestinationConfig</code> – Send discarded records to an Amazon SQS queue or Amazon SNS topic.</p>
86
-
* </li>
87
-
* <li>
88
-
* <p>
89
85
* <code>MaximumRecordAgeInSeconds</code> – Discard records older than the specified age. The default value is infinite (-1). When set to infinite (-1), failed records are retried until the record expires</p>
* events in a queue for up to six hours. When an event fails all processing attempts or stays in the asynchronous
40
40
* invocation queue for too long, Lambda discards it. To retain discarded events, configure a dead-letter queue with
41
41
* <a>UpdateFunctionConfiguration</a>.</p>
42
-
* <p>To send an invocation record to a queue, topic, function, or event bus, specify a <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations">destination</a>. You can configure separate destinations for successful invocations (on-success) and events
42
+
* <p>To send an invocation record to a queue, topic, S3 bucket, function, or event bus, specify a <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations">destination</a>. You can configure separate destinations for successful invocations (on-success) and events
43
43
* that fail all processing attempts (on-failure). You can configure destinations in addition to or instead of a
44
44
* dead-letter queue.</p>
45
+
* <note>
46
+
* <p>S3 buckets are supported only for on-failure destinations. To retain records of successful invocations, use another destination type.</p>
47
+
* </note>
45
48
* @example
46
49
* Use a bare-bones client and the command you need to make an API call.
* <p>The following error handling options are available only for stream sources (DynamoDB and Kinesis):</p>
78
+
* <p>The following error handling options are available only for DynamoDB and Kinesis event sources:</p>
79
79
* <ul>
80
80
* <li>
81
81
* <p>
82
82
* <code>BisectBatchOnFunctionError</code> – If the function returns an error, split the batch in two and retry.</p>
83
83
* </li>
84
84
* <li>
85
85
* <p>
86
-
* <code>DestinationConfig</code> – Send discarded records to an Amazon SQS queue or Amazon SNS topic.</p>
87
-
* </li>
88
-
* <li>
89
-
* <p>
90
86
* <code>MaximumRecordAgeInSeconds</code> – Discard records older than the specified age. The default value is infinite (-1). When set to infinite (-1), failed records are retried until the record expires</p>
* <p>The Amazon Resource Name (ARN) of the destination resource.</p>
758
-
* <p>To retain records of <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations">asynchronous invocations</a>,
759
-
* you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function,
758
+
* <p>To retain records of unsuccessful <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations">asynchronous invocations</a>,
759
+
* you can configure an Amazon SNS topic, Amazon SQS queue, Amazon S3 bucket, Lambda function,
760
760
* or Amazon EventBridge event bus as the destination.</p>
761
-
* <p>To retain records of failed invocations from <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventsourcemapping.html#event-source-mapping-destinations">Kinesis and
762
-
* DynamoDB event sources</a>, you can configure an Amazon SNS topic or
763
-
* Amazon SQS queue as the destination.</p>
764
-
* <p>To retain records of failed invocations from <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kafka.html#services-smaa-onfailure-destination">self-managed Kafka</a> or
761
+
* <p>To retain records of failed invocations from <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html">Kinesis</a>,
762
+
* <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-ddb.html">DynamoDB</a>, <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kafka.html#services-smaa-onfailure-destination">self-managed Kafka</a> or
* you can configure an Amazon SNS topic, Amazon SQS queue, or Amazon S3 bucket as the destination.</p>
767
765
* @public
@@ -771,6 +769,9 @@ export interface OnFailure {
771
769
772
770
/**
773
771
* <p>A destination for events that were processed successfully.</p>
772
+
* <p>To retain records of successful <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations">asynchronous invocations</a>,
773
+
* you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function,
774
+
* or Amazon EventBridge event bus as the destination.</p>
* <p>The metrics configuration for your event source. For more information, see <a href="https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics-types.html#event-source-mapping-metrics">Event source mapping metrics</a>.</p>
* <p>The metrics configuration for your event source. For more information, see <a href="https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics-types.html#event-source-mapping-metrics">Event source mapping metrics</a>.</p>
* <p>The metrics configuration for your event source. For more information, see <a href="https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics-types.html#event-source-mapping-metrics">Event source mapping metrics</a>.</p>
0 commit comments