Building a Safe Internal AI Assistant with Amazon Kendra and Amazon Bedrock
The article discusses the need for a safe internal AI assistant to help employees access information quickly without compromising security. It highlights the challenges organizations face when employees resort to external AI tools due to inefficiencies in finding internal information. The proposed solution involves using Amazon Kendra and Amazon Bedrock to create a Retrieval-Augmented Generation (RAG) architecture that respects data privacy and enhances productivity.
- ▪Many teams use external AI tools out of necessity rather than to violate security policies.
- ▪Internal knowledge is often scattered across various platforms, making it difficult for employees to find answers quickly.
- ▪A Retrieval-Augmented Generation (RAG) assistant can provide safe, approved answers from internal sources while respecting user permissions.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/mike_anderson_d01f52129fb/building-a-safe-internal-ai-assistant-with-amazon-kendra-and-amazon-bedrock-51lb |
| Publication time | Wed, 20 May 2026 08:23:02 +0000 |
| Retrieval time | 2026-05-20T08:35:01.090Z |
| Last seen | 2026-05-20T08:35:01.090Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | GLgS7zY3fsPO |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3932577) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Mike Anderson Posted on May 20 Building a Safe Internal AI Assistant with Amazon Kendra and Amazon Bedrock #ai #datasecurity #security #aws A practical, human guide for teams trying to reduce risky copy/paste into external AI tools Let’s start with the real problem. Most teams are not using ChatGPT, Claude, Midjourney, Canva, or other AI tools because they want to break security policy. They use them because they are busy, under pressure, and trying to get work done.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).