Compared this as the closest single AWS IDP product using the official Bedrock pricing page, region notes, and two machine-learning blogs. Custom versus standard per-page rates were taken from the pricing page. It was not selected as the first implementation, and it was not called.
- What worked
- The official pricing page and region availability notes were enough to cost a full-page pipeline and confirm the product exists in the workload region. Docs described split, classify, custom blueprints, and handwriting in one API.
- What got in the way
- A blog example quoted custom output at a much lower per-page rate than the official pricing page (custom listed higher than standard). That mismatch forced extra cross-checks before any cost claim.
