Frequently Asked Questions

Common questions about Control Hub, agent deployment, and API access.

Q: How long does agentic system generation take? Initial generation takes 30-60 seconds. The system analyzes your use case and generates 3-7 specialized agents depending on complexity.

Q: Can I modify the generated agents? Yes. Change models, add/remove tools, adjust memory settings, edit system prompts, or add new agents using the visual configuration or natural language chat.

Q: How do I connect my company documents to agents? Use the RAG (Knowledge Base) tool. Upload documents directly or connect to S3, Confluence, SharePoint, or Google Drive. Supported formats include PDF, DOCX, XLSX, CSV, TXT, and MD.

Q: What happens if my tests fail in the Test Bed? Review the execution traces to understand why, then adjust configurations in the Agentic System tab. Common fixes include refining system prompts, adding missing tools, or adjusting memory settings.

Q: How long does deployment take? Code generation takes 3-5 minutes, and full deployment completes in 3-6 minutes total. Monitor progress in real-time during deployment.

Q: How many API keys can I generate? Each project supports a maximum of 2 API keys. Keys are shown only once at generation — store them securely.

Q: Can multiple users interact with the same deployed agent? Yes. Use the actor_id parameter in API requests to isolate conversations per user. Each user gets separate conversation history and preferences.

Q: What AWS services does Control Hub deploy to? Amazon Bedrock, AgentCore, SageMaker, Amplify, and Lambda. The infrastructure is fully managed — no manual AWS configuration required.

Q: Can I update my agents after deployment? Yes. Make changes in the Agentic System tab, test in the Test Bed, and redeploy. The deployment process updates your existing application.

Q: How do I maintain conversation context across API calls? Use the same session_id in your requests. The agent remembers the full conversation history for that session. Generate a new session_id to start fresh.

Q: How do I connect to an internal tool that isn't listed? Use Custom Connectors with MCP. Provide your endpoint URL and OAuth credentials to connect any custom API or internal tool.