待翻译：Governed reports with Amazon Quick Desktop and Amazon FSx for NetApp ONTAP

AI 服务暂时不可用，以下为来源正文，待恢复后补全翻译。

Amazon Quick Desktop brings governed, AI-assisted reporting to the files your team already manages on Amazon FSx for NetApp ONTAP (FSx for ONTAP), cutting weekly report preparation from hours to minutes. Today, producing those reports takes hours of manual effort each week. Teams re-read the same documents, reformat metrics, and copy summaries into Slack. Leaders need those updates quickly, but they also need to trust the source behind each metric, risk, and recommendation. In this post, you build a governed weekly reporting workflow with Amazon Quick Desktop, Amazon Quick skills, Amazon FSx for NetApp ONTAP, Amazon Simple Storage Service (Amazon S3) access points, and Slack. Amazon Quick Desktop is a native desktop application that extends Amazon Quick from the browser to the user’s computer. It provides the AI-powered capabilities of the web experience together with desktop-specific capabilities such as Local file access. Background processing. A personal knowledge graph. In Amazon Quick Desktop, you create a skill called Weekly Business Reporting Assistant. A skill is a reusable workflow that gives Amazon Quick task-specific instructions, so users can start the same reporting process each week with a trigger phrase. The workflow connects a governed set of business files to a guided reporting experience. It keeps source documents under existing storage and access controls, gives Amazon Quick access only to the selected reporting content, and keeps human review in place before artifacts or Slack summaries are shared. The examples use fictitious business data, but the pattern applies to operating reviews, forecast updates, risk reporting, executive briefings, and weekly business reviews. Solution overview This solution makes Amazon Quick Desktop the main workspace for weekly reporting. Business users open Quick Desktop, activate the Weekly Business Reporting Assistant skill, and ask questions such as “What changed since last week’s operating review?” or “Create a one-page weekly report for leadership.” The skill makes the workflow repeatable. It gives Amazon Quick task-specific instructions that cover the source collection, output formatting, citation behavior, and when to ask for clarification. This lets users start from a guided reporting process instead of a blank conversation. The source files remain in FSx for ONTAP. In this walkthrough, FSx for ONTAP stores the documents that support weekly reporting, such as final weekly reviews, operating plans, forecast summaries, risk registers, and executive templates. Keeping the files in FSx for ONTAP lets storage and business teams continue using their existing file access and governance processes. You choose one reporting folder for the assistant to use. This folder contains the files business owners approve for the workflow. Drafts, outdated files, restricted documents, and unrelated content stay outside this folder. The S3 access point gives Amazon Quick controlled read access to that selected folder. AWS Identity and Access Management (IAM) permissions limit what Amazon Quick can list and read. Amazon Quick uses the selected files to create a searchable source collection called a knowledge base. In this walkthrough, the knowledge base is named Business Reporting Archive. The Weekly Business Reporting Assistant skill uses it to answer questions, cite source documents, create reports, generate decks and PDFs, build visuals, and draft Slack-ready summaries. After the report is ready to share, you use Slack integration in Amazon Quick to draft a channel summary. You review and approve the message before posting. Figure 1 shows the workflow. Business files stay in FSx for ONTAP. The S3 access point gives Amazon Quick controlled access to the selected reporting folder. Amazon Quick prepares that content as the Business Reporting Archive knowledge base. Users work in Quick Desktop with the Weekly Business Reporting Assistant skill to create cited reporting artifacts and Slack summaries for approval. Figure 1: Governed weekly reporting workflow with Amazon Quick Desktop, Amazon Quick skills, Amazon FSx for NetApp ONTAP, Amazon S3 access points, and Slack Amazon Quick Desktop also builds a personal knowledge graph in My context, connecting people, projects, events, actions, and documents. For example, while preparing a weekly report, a user can identify related people, action items, documents, and Slack channels from connected sources. The Business Reporting Archive remains the governed source for report facts and citations. Figure 2: Example personal knowledge graph in the My context view of Amazon Quick Desktop Prerequisites This walkthrough assumes your storage and identity foundation already exists. You configure the access path, Amazon Quick knowledge base, reporting assistant, Slack action connector, and validation workflow. You don’t create the FSx for ONTAP file system itself. AWS account and Amazon Quick requirements An AWS account with access to a Region where Amazon Quick, Amazon FSx for NetApp ONTAP, and Amazon S3 access points for FSx for ONTAP are supported. An Amazon Quick Enterprise subscription with permissions to create Amazon S3 integrations, knowledge bases, and spaces. The Amazon Quick desktop application installed for the users who run the reporting workflow. Review enterprise setup requirements before a production rollout. FSx for ONTAP requirements An FSx for ONTAP file system running NetApp ONTAP 9.17.1 or later. An FSx for ONTAP volume that is mounted and has a junction path, such as /business-reporting. An S3 access point attached to the FSx for ONTAP volume, or permissions to create one. The S3 access point and the FSx for ONTAP volume must be in the same AWS Region and owned by the same AWS account. AWS Identity and Access Management (IAM) permissions to grant Amazon Quick least-privilege read access to the S3 access point and approved object prefix. An Amazon S3 path in the same AWS Region as your Amazon Quick application. Slack and testing requirements A Slack workspace, an approved channel for reviewed summaries, and permissions to configure the Slack action connector. A focused set of fictitious or approved business files for testing, such as weekly reviews, operating plans, forecast summaries, risk registers, and executive templates. Implementation The implementation has seven steps. The following sections walk through each one: prepare the source folder, create the S3 access point, grant Amazon Quick read access, create the Amazon S3 integration and knowledge base, configure Slack, create the reporting assistant, and test the workflow. Step 1: Prepare source content Start with a narrow folder scope so business users can verify citations against a known set of source files. For this walkthrough, use a mounted FSx for ONTAP volume and create or choose an approved folder such as /business-reporting. Within that folder, organize files around the reporting process. Add the last 8–12 weekly business reviews, the current operating plan, the current forecast summary, and the current risk register. Also add the standard report template that guides the output style. Remove draft, obsolete, archived, and restricted files before indexing, and confirm that file owners agree with the source scope. /business-reporting/ weekly-reviews/ operating-plans/ forecasts/ risk-registers/ executive-templates/ Figure 3: Example approved reporting folder structure on a mounted FSx for ONTAP volume Step 2: Create an S3 access point Attach an S3 access point to the FSx for ONTAP volume. Amazon Quick can then read the approved content through an S3-compatible path. Work with your storage or cloud administrator if you don’t own the FSx for ONTAP configuration. Open the Amazon FSx console in the Region that contains the FSx for ONTAP volume. In the navigation pane, choose Volumes. Select the mounted FSx for ONTAP volume that contains the approved reporting folder. From Actions, choose Create S3 access point. Enter an access point name that follows your naming standard, such as business-reporting-ap. Configure the access point user and network settings according to your governance model. Select a virtual private cloud restriction if your workload requires private network access. Create the access point, and then record the access point alias and Amazon Resource Name (ARN). Use the alias in the S3 URI and the ARN in IAM policies. Figure 4: S3 access point overview for an FSx for ONTAP data source Step 3: Grant Amazon Quick read access Grant only the access Amazon Quick requires to list and read the approved prefix. The following policy is a starting point. Replace the placeholders with your Region, account ID, access point name, and prefix. { "Version": "2012-10-17", "Statement": [ { "Sid": "ListApprovedReportingPrefix", "Effect": "Allow", "Action": ["s3:ListBucket", "s3:GetBucketLocation"], "Resource": "" }, { "Sid": "ReadApprovedReportingObjects", "Effect": "Allow", "Action": "s3:GetObject", "Resource": "" } ] } Set to arn:aws:s3:::accesspoint/. Set to arn:aws:s3:::accesspoint//object/business-reporting/*. Identify the IAM role or service role that Amazon Quick uses for the Amazon S3 integration in your account. Attach the policy to that role, and grant read access to document-level access control list (ACL) or metadata files that the Amazon S3 integration requires. Before you configure the Amazon S3 integration, validate the access point alias and prefix. Verify that the role cannot read folders outside the approved reporting prefix. Figure 5: Example IAM policy editor with S3 access point permissions Step 4: Create the Amazon S3 integration Create an Amazon S3 integration in Amazon Quick and use it to create a knowledge base from the approved prefix. The console might label the path as a bucket URL even when you use an S3 access point alias. Validate the alias path in your account before you publish the assistant. Open the Amazon Quick console. Choose Knowledge. Under Amazon S3, choose Add. Choose an existing Amazon S3 data source, or choose + Add account to connect a new source. For Name, enter FSx ONTAP Business Reports. For the S3 location, enter the access point alias path, such as s3:///amzn-s3-demo-business-reporting/. On the knowledge base page, enter FSx ONTAP Business Reports as the knowledge base name. Select only the approved prefix. After the knowledge base sync, open Spaces in the Amazon Quick console. Create a new space called Business Reporting Archive. Add the FSx ONTAP Business Reports knowledge base to this space. If your reporting files require per-user or per-group permissions, configure document-level ACL and metadata settings first. Amazon Quick requires you to make the ACL decision during knowledge base creation. After you choose Create, wait for the first sync to finish. Figure 6: Amazon Quick knowledge base created from the approved S3 access point path Step 5: Configure Slack Configure Slack so the assistant can stage business summaries for review and posting to the approved channel. Choose the authentication method that matches your organization’s security requirements. In the Amazon Quick console, choose Connectors. In the Amazon Quick desktop application, choose Settings, choose Capabilities, choose Connections, and then choose Browse Connections. This opens the Amazon Quick web console to complete the connection. On the Available tab, find Slack and choose Connect. For a team-managed app or token-based setup, use the Create for your team tab. Complete the Slack sign-in or token flow and grant only the required permissions. Use the minimum required Slack OAuth scopes (for example, chat:write scoped to the approved channel), and rotate credentials on a defined schedule. If your organization requires connector approval, work with your Amazon Quick administrator to publish the Slack connect [truncated for AI cost control]