Where AI/ML adds value
The guide names three kinds of value. Recognise them in a scenario and you can usually eliminate half the options.
- Assisting human decisions. The model narrows, ranks or flags; a person decides. Fraud alerts for an analyst, a shortlist of likely diagnoses for a clinician to review.
- Scalability. The task is easy for a person but impossible at volume: reading every product review, tagging every uploaded image, translating every support article.
- Automation. A repetitive judgement — extracting fields from invoices, transcribing calls — done without a person in the loop for the routine cases.
When AI/ML is not appropriate
Should this be an ML problem at all?
- An exact, deterministic result that must be right every timeUse rules or ordinary code
- The cost of building and running the model exceeds the value of better predictionsDon't build it yet
- Too little relevant data, or no way to tell right from wrongCollect data first
- A useful prediction or generated draft at scaleAI/ML is a candidate
Matching the technique to the problem
| Technique | Output | Example | Learning type |
|---|---|---|---|
| Regression | A number | Predict next month's sales; estimate a house price | Supervised |
| Classification | A category | Spam or not; which product line a ticket belongs to | Supervised |
| Clustering | Groups the data forms on its own | Segment customers by behaviour with no predefined segments | Unsupervised |
Real-world applications the guide names
| Application | What it does | Typical AWS fit |
|---|---|---|
| Computer vision | Detects objects, faces, text and activity in images and video | Amazon Rekognition |
| NLP | Finds sentiment, entities, key phrases and topics in text | Amazon Comprehend |
| Speech recognition | Turns speech into text | Amazon Transcribe |
| Recommendation systems | Suggests items based on behaviour | Amazon Personalize |
| Fraud detection | Flags likely fraudulent activity | Amazon Fraud Detector, or a custom model in SageMaker AI |
| Forecasting | Predicts future values from time-series history | Amazon Forecast, or a custom model in SageMaker AI |
| Knowledge bases | Answers questions from an organisation's documents | Amazon Kendra for search; Amazon Bedrock Knowledge Bases for generative answers |
| Agentic AI | Pursues a goal across steps, calling tools | Agents built on Amazon Bedrock |
The managed services named in the objective
The AWS decision guide describes three tiers. Pre-built AI services solve a specific task with no ML expertise. Amazon SageMaker AI is for building, training and deploying custom models. Specialised infrastructure (for example AWS Trainium and Inferentia chips) is for teams that want to manage the underlying resources themselves. AIF-C01 lives almost entirely in the first two tiers.
| Service | Input → output | Pick it when the scenario says… |
|---|---|---|
| Amazon Transcribe | Audio → text | “transcribe calls”, “captions”, “speech to text” |
| Amazon Polly | Text → lifelike speech | “read aloud”, “voice for an app”, “text to speech” |
| Amazon Translate | Text → text in another language | “localise”, “translate support articles” |
| Amazon Comprehend | Text → sentiment, entities, key phrases, topics | “analyse reviews”, “extract entities”, “detect sentiment” |
| Amazon Lex | Builds conversational bots (voice and text) | “chatbot”, “IVR”, “conversational interface” |
| Amazon SageMaker AI | Your data → your own trained model | “custom model”, “our own algorithm”, “full control over training” |
Traditional ML or a foundation model?
The guide asks you to choose based on regulatory concerns, explainability requirements and operational constraints. Foundation models are flexible and need no task-specific training, but they are large, their reasoning is hard to inspect, and their output can vary from run to run. Traditional models are narrow but small, cheap to run, and — for model types like linear models and decision trees — far easier to explain.
Choosing between the two
Lean towards traditional ML
- A regulator or customer must be told why a decision was made
- A narrow, well-defined prediction on tabular data
- Tight latency or cost per prediction
- Results must be consistent run to run
Lean towards a foundation model
- Open-ended language, images or conversation
- Many different tasks from one model
- Little or no labelled data for the task
- Generating drafts, summaries or answers
Traps the wrong answers are built from
| Tempting but wrong | Do this instead |
|---|---|
| Using ML where a fixed rule gives the exact answer. | If the outcome must be deterministic and correct every time, write the rule. |
| Building a custom SageMaker AI model for a task a managed service already does. | Check the pre-built services first: Transcribe, Translate, Comprehend, Rekognition, Polly, Lex. |
| Choosing an LLM for a regulated decision that must be explained. | Prefer an interpretable traditional model when explainability is a requirement. |
| Calling customer segmentation “classification”. | With no predefined labels it is clustering — unsupervised. |
You should now be able to
- Recognise when AI/ML adds value through assisted decisions, scale or automation.
- Recognise when AI/ML is inappropriate: exact outcomes required, or costs outweigh benefits.
- Choose regression, classification or clustering from a problem description.
- Match real-world applications to the right kind of AI.
- Pick the right managed service: SageMaker AI, Transcribe, Translate, Comprehend, Lex, Polly.
- Choose between a traditional ML model and a foundation model using regulatory, explainability and operational constraints.