Integrate Atlassian Confluence Cloud with Amazon Quick

TL;DR

• Amazon Quick now supports direct integration with Atlassian Confluence Cloud, allowing users to search and manage documentation via natural language queries without switching applications.
• The integration utilizes two primary methods: Knowledge Bases for pre-indexed semantic search of unstructured content and Actions for real-time read, write, and automation tasks.
• Setup for the knowledge base integration requires no administrator involvement or API keys; any user can connect via OAuth 2.0 using only their base Confluence URL.
• Three distinct methods exist for configuring Actions: built-in connectors (pre-configured for tools like Confluence and Jira), custom REST APIs via OpenAPI specifications, and Model Context Protocol (MCP) servers for dynamic tool discovery.
• The architecture is tiered by subscription level: Quick Enterprise is required to create new integrations, while Quick Professional users can utilize pre-existing integrations.

Why It Matters

This integration reduces operational friction by eliminating the need to context-switch between documentation hubs and data analysis interfaces, thereby accelerating decision-making processes. By enabling non-technical users to connect enterprise documentation without IT intervention, it democratizes access to institutional knowledge and lowers the barrier to entry for deploying enterprise AI assistants.

Key Data

• Subscription Requirements: Quick Enterprise is required for creating integrations; Quick Professional is sufficient for using them.
• Authentication Type: The integration relies on OAuth 2.0 applications and API scopes.
• Integration Categories: The system supports three specific categories: Actions (task execution), Knowledge Bases (unstructured content indexing), and Topics/Datasets (structured data querying via Amazon Redshift).
• URL Format: Confluence Cloud connections require a base URL ending in .atlassian.net (e.g., yourinstance.atlassian.net).
• ACL Requirement: Enabling Document-level Access Controls (ACLs) requires specific Atlassian admin credentials: API key, Organization ID, and Directory ID.

Technical Details

• Knowledge Base Architecture: Quick connects to external systems to retrieve documents and wikis, building a pre-built searchable index. This allows generative AI-powered retrieval and question answering without real-time connection to the external system for every query.
• Action Integration Paths: Developers and users can configure Actions through three mechanisms: built-in configuration-driven connectors for popular tools, custom REST APIs defined by OpenAPI specifications, and Model Context Protocol (MCP) servers which allow for dynamic tool discovery.
• Security Model: The integration follows the AWS shared responsibility model. AWS manages infrastructure security and ensures data encryption at rest and in transit, while the user is responsible for configuring OAuth permissions, managing API scopes, and enforcing data governance policies.
• Access Control List (ACL) Feature: An optional advanced feature allows Quick to enforce per-user Confluence permissions. This ensures that generated answers are derived only from content the specific user is already authorized to access, though this feature requires administrator-level credentials to enable.

Industry Insight

• The introduction of Model Context Protocol (MCP) support in Amazon Quick signals a shift toward standardized, interoperable interfaces for connecting AI agents to enterprise tools, reducing the need for bespoke, one-off API integrations.
• The removal of administrative barriers for knowledge base setup indicates a strategic move toward self-service enterprise AI, where end-users can independently augment AI assistants with their own team’s documentation, scaling AI adoption across the organization without IT bottlenecks.
• The distinction between "Enterprise" and "Professional" tiers regarding creation vs. usage suggests a monetization strategy where large organizations pay for the flexibility of custom integrations, while smaller teams gain value through pre-built, standard connectors.

zations ensure that users only see documentation they are authorized to access?
A: Organizations can enable Document-level access controls (ACLs), an optional advanced feature. This ensures Quick enforces per-user Confluence permissions. Enabling this feature requires Atlassian admin credentials, including an API key, Organization ID, and Directory ID.