aws / aws/aws-lambda-roadmap

[Lambda] [DocumentDB] Support Amazon DocumentDB 8.0.x as a Lambda event source

Aperta
#96 0 commenti 1 reazione 0 assegnatari Vedi su GitHub
Lingua principale
Nessun dato sulla lingua
Stelle
196
Fork
5
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

Add Amazon DocumentDB 8.0.x to the engine versions accepted by Lambda's `CreateEventSourceMapping` (and `UpdateEventSourceMapping`) for `aws:docdb` event sources. Today only DocumentDB 4.0 and 5.0 are accepted.

**Which service(s) is this request for?**

Lambda/DocumentDB

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

We use DocumentDB change streams as a native trigger for Lambda (event-driven processing of document changes). Our clusters run 8.0.1, and creating the trigger fails at the API:

```
operation error Lambda: CreateEventSourceMapping,
https response error StatusCode: 400,
InvalidParameterValueException: Engine version 8.0.1 is not supported.
```

This looks like a create-time version allowlist rather than a functional limitation. If we create the mapping while the cluster is on 5.0.0 and then upgrade the cluster in place to 8.0.1, the existing trigger keeps working — events continue flowing to the function with no changes. So the 8.0 engine is already compatible with the change-stream / event-source-mapping mechanism at runtime; only `CreateEventSourceMapping` rejects 8.0.x up front.

Impact: we can't run clusters on the current engine version and use the fully managed native trigger at the same time. That blocks us from upgrading, or forces extra infrastructure.

**Are you currently working around this issue?**

Create the event source mapping on a 5.0.0 cluster, then upgrade the cluster in place to 8.0.1 - the trigger survives the upgrade. Unfortunately you will be unable to add new triggers in future, which is blocker for us.

**Additional context**

The supported-versions notes in "Process Amazon DocumentDB events with Lambda" (Lambda dev guide) and "Using AWS Lambda with change streams" (DocumentDB dev guide) currently list only 4.0 and 5.0 and don't mention 8.0, so the error is ambiguous with a misconfiguration. Until 8.0 is supported, explicitly calling it out in both docs pages (and ideally the error message) would help. Cluster type is instance-based / regional (not elastic or global), with change streams enabled.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia dal comportamento di CreateEventSourceMapping e UpdateEventSourceMapping descritto nell'issue, quindi esamina le note sulle versioni supportate nelle pagine delle guide di Lambda e DocumentDB indicate qui. Il lavoro sarà completato quando DocumentDB 8.0.x sarà accettato per le origini evento aws:docdb ed entrambe le pagine della documentazione descriveranno accuratamente le versioni supportate.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
aws
Ambito
cloud, databases
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.