ContextIQ Essentials - Governed Knowledge for Cowork & AI Agents

Prerequisites:

• AWS account with Bedrock model access enabled for Anthropic Claude and Amazon Titan Embed Text V2 in your target region
• IAM permissions to deploy CloudFormation stacks (admin), or the included delegated deployment policy for non-admin users
• Supported regions: us-east-1, us-west-2, eu-west-1, ap-southeast-1

Step 1 - Deploy the Essentials Stack (~30-35 minutes):

1. After subscribing, launch the CloudFormation quickstart from the fulfillment page
2. Fill in AdminEmail (your email for the initial admin account) and AdminPassword (must include uppercase, lowercase, number, and special character)
3. All other parameters have sensible defaults - no changes needed
4. Check the IAM capabilities acknowledgment checkbox and click Create stack

What gets deployed: VPC with Application Load Balancer, Amazon Bedrock AgentCore agents, ECS-based MCP servers with tools, two Amazon Bedrock Knowledge Bases (OpenSearch and S3 Vectors), Amazon Cognito user pool with pre-created access groups, Amplify-hosted chat interface, and pre-loaded sample documents for immediate evaluation.

Step 2 - Verify with the Nexus Chat App:

1. Open the ChatApp URL from CloudFormation Outputs tab (ChatAppUrl)
2. Sign in with the AdminEmail and password you provided during deployment
3. Set a permanent password when prompted on first sign-in
4. Try a sample query: "What are our current capital ratios and how much buffer do we have under stress?"

Step 3 - Connect Cowork (Claude Desktop):

1. Download the Cowork setup package from the stack outputs: aws s3 cp s3://<DocsDistBucket>/cowork/contextiq-cowork.tar.gz . && tar xzf contextiq-cowork.tar.gz && cd contextiq-cowork
2. Run the setup script: ./contextiq-setup --username your@email.com 
3. The script auto-discovers your deployment, authenticates, and configures Claude Desktop
4. Restart Claude Desktop - the ContextIQ tool appears in MCP connectors
5. Set the ContextIQ connector to "Always Allow" for seamless experience
6. Start with: "Tell me about ContextIQ" to activate the MCP server

Step 4 - Onboard Your Team:

1. Create Cognito user accounts via the AWS Console (Cognito > User Pools) or the included contextiq-admin-setup script
2. Assign users to knowledge base access groups: contextiq-all-kb (both knowledge bases), contextiq-opensearch (regulatory/reference documents only), or contextiq-s3vectors (internal/proprietary content only)
3. Distribute Cowork access: ./contextiq-setup --export-config --publish - generates a shareable setup link. End users need only Python 3.10+, no AWS CLI or backend access required
4. First-time users must sign in via the Chat App once to set a permanent password before using the Cowork setup script

Step 5 - Add Your Own Documents:

Upload documents to the S3 document buckets shown in CloudFormation Outputs. Amazon Bedrock automatically ingests uploaded documents. Supported formats: PDF, TXT, MD, CSV, DOCX, HTML, JSON.

Monitoring:

• CloudFormation Console: Stack status, outputs, and resource list
• ECS Console: MCP server health, task status, and container logs
• CloudWatch Logs: Application logs under the /contextiq log group
• Cognito Console: User management, group assignments, sign-in activity
• Amazon Bedrock Console: Knowledge base sync status and ingestion history

Uninstall:

Delete the contextiq-essentials CloudFormation stack. All provisioned resources are removed. S3 document buckets containing customer-uploaded content are retained by default and must be deleted manually if desired.

Support:

Email hello@contextiq.us  for deployment, configuration, or upgrade questions. Target response time: 2 business days. For ContextIQ Enterprise Preview, contact hello@contextiq.us .

Product documentation: https://contextiq.us/readme