Managed AI APIs, foundation models and the custom ML platform on AWS, and how to choose between them.
|
|
|
AWS groups its machine learning offerings into three layers. Task-specific AI services expose pre-trained models behind simple APIs: send a document to Textract and get text, forms and tables back; send text to Comprehend and get entities, sentiment or redacted PII. Amazon Bedrock provides managed access to foundation models from several providers through one API, along with Knowledge Bases for retrieval-augmented generation, Agents for tool use and Guardrails for content and PII filtering. Amazon SageMaker is the platform for teams that build, train, tune and host their own models, including open-weight models deployed from JumpStart.
The layers are complementary rather than competing. A document pipeline might use Textract to extract text from scanned forms, Comprehend to detect and redact personal data, a Bedrock model to summarise the result, and a SageMaker endpoint hosting a custom classifier trained on the company's own labels. Choose the highest-level service that meets accuracy, cost and compliance needs, because it carries the least operational burden.
| Option | You provide | Best for | Pages |
|---|---|---|---|
| AI services | input data | OCR, NLP and vision tasks with standard outputs | overview, Comprehend, Textract, Rekognition |
| Amazon Bedrock | prompts, documents, tools | chat, summarisation, RAG, agents | overview, Knowledge Bases, Agents, Guardrails |
| Amazon SageMaker | data, code, model choice | custom training, fine-tuning, hosting | overview, JumpStart |
| QuickSight Q | a dataset | natural-language questions over BI data | QuickSight |
Cost models differ too: AI services and Bedrock charge per request, page, character or token, while SageMaker charges for the instances you run, so steady high-volume inference can be cheaper on SageMaker and spiky or low-volume use cheaper on the per-call services.