Atlassian Confluence Cloud と Amazon Quick の統合を発表

Teams can integrate Atlassian Confluence Cloud with Amazon Quick to search and manage documentation without switching between multiple systems. When documentation lives in Confluence, but related data sits in other systems, teams waste time switching tools, re-searching for context, and manually gathering information. These interruptions slow decisions and create gaps between available knowledge and actionable insights. The direct integration with Confluence Cloud reduces context switching by making your Confluence content searchable through natural language queries directly from the Quick interface. Teams can query Confluence pages, retrieve documentation, and update content while accessing data from other integrated systems such as Amazon Simple Storage Service (Amazon S3), Atlassian JIRA, or other business applications.

In this post, you will learn how to set up the Confluence Cloud integration with Quick. This includes creating a knowledge base for semantic search, setting up Actions to query and manage Confluence pages, and organizing resources in Quick Spaces. Quick integrates with your current enterprise technology stack, from internal knowledge repositories and corporate intranets to business-critical applications and AWS data services. These integrations span three categories: Actions for executing tasks across connected applications, knowledge bases for indexing unstructured content like documents and wikis, and Topics and Datasets for natural language querying over structured data sources like Amazon Redshift. This post focuses on setting up Knowledge bases and Actions.

*Actions* connect Quick to external systems at the time of prompt or query. You can read, write, and automate tasks directly within Quick. There are three ways to set up an Action integration:

• Through a built-in connector (a pre-built, configuration-driven integration for popular tools like Confluence Cloud, Jira, and Salesforce)

• Using a custom REST API using an OpenAPI specification (for connecting your own or third-party APIs)

• Through an Model Context Protocol server (MCP) (a flexible, standards-based approach that allows dynamic tool discovery from custom or third-party MCP servers).

Some services, like Confluence Cloud, support multiple integration paths. This post will focus on setting up an action integration using the built-in connector.

*Knowledge bases* index content before users query it. When you create a knowledge base, Quick connects to external systems like Confluence Cloud or JIRA, retrieves your documents and wikis, and builds a searchable index. When users ask questions, Quick retrieves relevant information from this pre-built index rather than connecting to the external system in real time. This approach makes unstructured content instantly searchable through natural language queries.

Together, Actions and knowledge bases give you flexible, complementary ways to bring your enterprise data and workflows into Quick.

Prerequisites

Before you set up Confluence integration, make sure that you have the following:

• Atlassian Confluence Cloud and developer account with administrator permissions to create OAuth 2.0 applications and manage API scopes

• Amazon Quick subscription: Quick Enterprise (to create integrations) or Quick Professional (to use existing integrations)

• AWS account with appropriate AWS Identity and Access Management (IAM) permissions to access Quick and create integrations

The integration in this post follows the AWS shared responsibility model: AWS manages the security of the infrastructure and underlying services, while you’re responsible for configuring OAuth permissions, managing API scopes, controlling access to your Confluence content through the permission settings, and verifying alignment with your organization’s data governance policies.

Amazon Quick maintains security of data throughout this integration with encryption at rest and in transit. For more information, see AWS security in Quick.

Solution overview

Now that you understand the benefits, you will now create the Confluence Cloud integration in Quick, create knowledge bases and actions to sync your Confluence content, configure permissions, and interact with your Confluence cloud space through natural language queries. By the end, you can use the content in your Confluence wiki pages to create meaningful insights.

Creating the Atlassian Confluence Cloud knowledge base

A knowledge base in Quick is an organized, indexed collection of documents or content from data sources that Quick improves on for generative AI-powered retrieval and question answering. You can use Knowledge base integrations to create searchable repositories of information from external sources.

In the Quick Console, choose the Knowledge button to set up a new integration. In the Set up new knowledge base section, select the plus (+) icon in the Atlassian Confluence Cloud card. The Atlassian Confluence Cloud card is displayed alongside other available knowledge base integrations such as Amazon S3 and Atlassian Jira Cloud.

In the Create Confluence Knowledge base page, choose the My Data Access Integration dropdown menu and select Add account to connect your Confluence Cloud instance.

In the Authentication Method screen, enter your base Confluence URL in the Confluence URL text box. The URL for Confluence Cloud must be the base URL, ending with .atlassian.net (for example, yourinstance.atlassian.net).

Connecting Confluence Cloud to a Quick knowledge base requires no administrator involvement. Enter your Confluence URL and accept the OAuth permission prompt. Quick handles the authentication for you. Any user can set this up independently, without needing API keys, admin console access, or IT involvement.

Document-level access controls (ACLs) is an optional advanced feature for organizations that need Quick to enforce per-user Confluence permissions — ensuring users only see answers from content they’re already authorized to access. Enabling ACLs requires Atlassian admin credentials (API key, Organization ID, and Directory ID).

For more information, see Document-level access controls. If you do not enable ACLs, access is controlled at the knowledge base level. Anyone who has access to the knowledge base can get insights from all the content within it.

This blog post uses the ACL-enabled connection.

To enable document-level access controls, check the Use Atlassian admin credential check box under ACL Management and fill in the API Key, Organization ID and Directory ID fields. Please see here on how to obtain these Atlassian admin credentials.

When enabled, Amazon Quick verifies a user’s access in real time and crawls the following Confluence ACL resources:

• Spaces – Space permissions apply to all documents in the space by default.

• Pages – Pages can be restricted to specific users and groups. Nested pages inherit restrictions from the parent page and can have their own restrictions.

• Blogs – Blog posts can be restricted to specific users and groups in the space.

• Attachments – Files attached to pages or blog posts inherit the access controls of their parent document.

When the Amazon Quick requesting access to your Atlassian account pop-up window appears, review the permissions listed and choose Accept to complete the authorization and sign-in process.

After you’re signed in, enter a descriptive name for your knowledge base and provide the Confluence URL including the space key (for example, yourinstance.atlassian.net/wiki/spaces/SPACEKEY).

Choose Add and then Next: Additional settings to complete the knowledge base setup.

After you successfully create the knowledge base, it appears in the Existing Knowledge bases section. The Status column shows the current sync state of your knowledge base.

A successfully created knowledge base in Quick syncs with the available content in Confluence Cloud. After the sync is complete, the Status field changes to Available.

You can view more details about the knowledge base by choosing the ellipsis (…) button in the Action column and selecting View knowledge base.

In the knowledge base details page, you can view the Summary, Sync Schedules, Sync Reports, and Permissions for that knowledge base.

The Summary tab of the knowledge base details page displays the knowledge base status, its last refresh timestamp, and the content URL that Quick crawled. You can choose Sync now to trigger a manual refresh or Edit to modify the knowledge base configuration, such as adding additional content URLs and other advanced indexing settings.

The Sync Schedules tab displays the current sync schedules and the history of refreshes. You can change the current schedule by choosing Add new Schedule or run an on-demand refresh by selecting Sync now.

The Sync Reports tab gives you an overview of items that Quick synced or refreshed along with items that skipped or failed. Here, you can also download a detailed CSV report for further analysis of sync results.