> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Obtaining Sentiment Analysis > Guide to performing sentiment analysis using Amazon Bedrock, designing prompts, and operational workflows to classify feedback as positive negative or neutral for analytics and automation In this lesson we'll cover how to perform sentiment analysis—automatically classifying text as positive, negative, or neutral—using Amazon Bedrock and a foundation model. We'll walk through the problem, a practical solution, and an operational workflow for reliable classification. Finally, we'll summarize expected results and key takeaways. A presentation slide titled "Lecture Flow" showing a three-step process: Problem → Solution → Workflow. The notes state manual customer sentiment is difficult, the solution is sentiment analysis, and the workflow focuses on classification, not generation. ## Problem: high volumes of customer feedback Companies collect feedback across many channels—customer reviews, support tickets, surveys, and social media—and that text contains early warning signs about product quality, service issues, and brand perception. Manually labeling thousands of entries is slow, inconsistent, and makes it difficult to spot trends or prioritize action quickly. A slide titled "Real-World Problem" showing a central "Feedback" icon surrounded by four blue tiles labeled Customer reviews, Support tickets, Social media comments, and Survey responses. A purple banner at the bottom states that feedback contains valuable insights about how customers feel about products, services, or experiences. The core requirement is simple: convert each feedback item into a discrete label (for example, "positive", "negative", or "neutral") so you can aggregate sentiment, detect changes, and take prioritized action at scale. A presentation slide titled "Real-World Problem" with two colored panels: a blue card labeled "Slow & time-consuming" (showing a stopwatch/browser icon) and an orange card labeled "Hard to identify trends" (showing a chart icon) describing issues with manual feedback analysis and trend/sentiment detection. ## Solution overview: classification with a foundation model Amazon Bedrock lets you call a foundation model to perform classification. For sentiment analysis you provide the feedback text plus an instruction prompt that constrains outputs to a small set of allowed labels. When the model is limited to those outputs, it returns a concise, consistent label that your application can parse and store. Typical pipeline: * Collect text inputs from reviews, tickets, or social channels. * Send each text (or a batch) to the foundation model through Bedrock with a strict classification prompt. * Parse and validate the single-label response and store it for dashboards, analytics, or automated ticket routing. Example prompt (sent to the model): ```text theme={null} Classify the following review as exactly one of: positive, negative, neutral. Return only the label on a single line with no additional text. Review: "The product works well but the battery life is terrible." ``` Expected response: ```text theme={null} negative ``` A three-step diagram showing sentiment analysis: input is a customer review saying "The product works well but the battery life is terrible." A foundation model processes the text and outputs a "Negative" sentiment label with a thumbs-down icon. Benefits of this approach: * Monitor satisfaction across thousands of items in near real time. * Detect product regressions by tracking rising negative volume. * Prioritize urgent tickets flagged with negative sentiment. * Correlate sentiment shifts with releases, incidents, or campaigns. ## Why sentiment analysis is a classification task (not generation) Sentiment analysis expects one of a small, predefined set of labels. This is different from generative tasks (summarization, open Q\&A, creative writing) where the model produces unconstrained text. For operational reliability, constrain the model to short, structured outputs—this improves consistency and simplifies downstream analytics. A slide titled "Solution: Not a Generative Task" explaining that sentiment analysis is a classification task, contrasting generative tasks (summarization, Q&A, writing) with classification (predefined labels, structured short responses). Make the prompt explicit: list allowed labels and require the model to return only that label (for example, `positive`, `negative`, or `neutral`). Constraining the output to a predictable format makes automated storage and aggregation reliable. ## Prompt design principles Well-designed prompts are essential for reliable classification. Use the three core principles below to reduce ambiguity and maximize repeatability. | Principle | What to do | Example or note | | - | -: | - | | Define allowed categories | List the exact labels the model may return (e.g., positive, negative, neutral). | Use domain-specific labels if needed (e.g., `bug`, `feature-request`, `compliment`). | | Specify output format | Require a single token or strict structure (single-line label, JSON object, or CSV). | Example JSON response: `{"label":"negative"}` — ensure the model returns precisely that. | | Prevent extra explanation | Instruct the model not to add commentary, punctuation, or extra lines. | Provide a negative example and a positive example in few-shot format if helpful. | Post-processing best practices: * Validate the returned label is in your allowed set; if not, map to a fallback or retry the request. * Normalize the label (lowercase, trim whitespace) before saving. * Use regex or deterministic mapping to enforce format (e.g., `^(positive|negative|neutral)$`). * For high-stakes use, consider a two-stage check: model + rule-based validator. An infographic titled "Workflow: Prompt Design for Sentiment" showing a colorful circular diagram that summarizes three key principles for sentiment classification prompts: define allowed categories, specify output format, and prevent extra explanation. Be cautious with sensitive content and personally identifiable information (PII). Mask or remove PII before sending data to a model if required by policy. Also, validate model outputs because occasional misclassifications can occur—use sampling and human review for quality monitoring. ## Example scenarios Here are sample reviews and their expected labels. These can be used as quick validation checks when designing prompts or testing model behavior. | Review | Expected label | | - | - | | "Product setup was easy and it works perfectly." | `positive` | | "Product is okay, but battery life is disappointing." | `negative` | | "Product arrived yesterday and I haven't started using it." | `neutral` | You can send these as individual prompts or batch them depending on throughput and Bedrock usage patterns. Always test a representative sample from each input channel (reviews, tickets, social posts) because language and tone vary by source. ## Expected results and operational benefits Using Bedrock for sentiment classification gives organizations the ability to: * Rapidly analyze very large volumes of feedback. * Produce consistent, structured labels suitable for dashboards and analytics. * Detect emerging negative trends faster and correlate them with product changes or incidents. * Automate prioritization rules (e.g., escalate tickets labeled `negative` with keywords like `refund` or `broken`). A presentation slide titled "Results" showing four numbered panels of organizational benefits. Each panel lists a short benefit with an icon: analyze large volumes of feedback; identify trends; improve products and customer experience; and detect emerging issues earlier. If you see a spike in negative labels, filter and inspect the underlying texts to find root causes and take corrective action quickly. ## Key takeaways * Treat sentiment analysis as a classification problem: restrict outputs to a fixed set of labels and enforce strict formatting. * Good prompt design (explicit allowed labels, exact output format, and prohibition of extra text) plus simple post-processing yields reliable labels for analytics and automation. * Validate outputs, monitor model quality, and handle sensitive data according to your compliance policies. * For more information on Bedrock and best practices, see the Amazon Bedrock documentation: [https://aws.amazon.com/bedrock/](https://aws.amazon.com/bedrock/) This concludes the lesson on sentiment analysis. A presentation slide titled "What's Next? Understanding Code Generation." On the right is a teal circular icon showing a stylized brain connected to circuit lines against a dark curved background. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.