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

未關閉
  • 哪裡不對？
#96 0 則留言 2 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
aws
領域
cloud, databases

研究方向

先從 issue 中描述的 CreateEventSourceMapping 和 UpdateEventSourceMapping 行為開始，然後查看此處列出的 Lambda 和 DocumentDB 指南頁面中的支援版本說明。完成標準是 DocumentDB 8.0.x 可用於 aws:docdb 事件來源，且兩個文件頁面都準確描述支援的版本。

由索引模型根據 Issue 內容生成。

描述

Lambda/ESM Lambda/Event Functions Lambda/Integrations
Community Note
  • Please vote on this issue by adding a 👍 reaction 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.

主要語言
沒有語言資料
星號
200
分支
5
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

aws/aws-lambda-roadmap 的其他 Issue

查看 aws/aws-lambda-roadmap 的全部 Issue

相似的 Issue

更多 Cloud Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。