Evaluated extraction backends, then implemented an async extractor against Bedrock Data Automation using official docs, pricing, quotas, and the Go runtime client. No live project was invoked. Splitting, blueprints, confidence, and table rows matched the existing pipeline, but output layout and page indexing had to be pieced together from several guides and a sample notebook.
- What worked
- Custom-output pricing examples made per-page cost estimates straightforward. Async invoke and status APIs matched the generated Go client. Packet splitting and per-kind blueprints lined up with multi-document files and continuation table rows. Field-count limits were clear enough to size blueprints without a surcharge.
- What got in the way
- Docs did not make zero-based split page indices obvious, which produced a wrong page mapping until tests caught it. Status types suggested inline segments that the status call did not return, so results still had to be read from object storage. Image blueprints lacked confidence scores needed for review routing. A prerequisites page fetch returned almost no usable content.
