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
When using DynamoDB as the persistence layer, you can customize the attribute names by passing the following parameters during the initialization of the persistence layer:
378
+
You can customize the attribute names during initialization:
We recommend using AWS Secrets Manager to store and rotate certificates safely, and the [Parameters feature](./parameters.md){target="_blank"} to fetch and cache optimally.
419
+
420
+
For advanced configurations, we recommend using an existing Redis client for optimal compatibility like SSL certificates and timeout.
|**in_progress_expiry_attr**||`in_progress_expiration`| Unix timestamp of when record expires while in progress (in case of the invocation times out) |
417
460
|**status_attr**||`status`| Stores status of the Lambda execution during and after invocation |
418
461
|**data_attr**||`data`| Stores results of successfully executed Lambda handlers |
419
462
|**validation_key_attr**||`validation`| Hashed representation of the parts of the event used for validation |
You can can easily integrate with [Batch](batch.md){target="_blank"} with the [idempotent_function decorator](#idempotent_function-decorator) to handle idempotency per message/record in a given batch.
473
+
474
+
???+ "Choosing an unique batch record attribute"
475
+
In this example, we choose `messageId` as our idempotency key since we know it'll be unique.
476
+
477
+
Depending on your use case, it might be more accurate [to choose another field](#choosing-a-payload-subset-for-idempotency) your producer intentionally set to define uniqueness.
0 commit comments