wickr-bedrock-bot
Version:
AWS Wickr's own Bedrock Bot
46 lines (36 loc) • 2.1 kB
YAML
# The AWS account ID where resources will be deployed
account: "480844863715"
# The AWS region where resources will be deployed
region: "us-east-1"
# Set the below to true if you are on govcloud
isGovCloud: false
# The ARN of the AWS Secrets Manager Secret containing the bot username and password
credentialsArn: "arn:aws:secretsmanager:us-east-1:480844863715:secret:test/bedrockbot-p7U9M2"
# The S3 bucket and the folder where the bedrock integration will be uploaded. Please craete the bucket and the folder(if you have not already)
deployment:
bucketName: wickriobedrockbotint
folder: artifacts
# Uncomment below line to deploy in preprod envs - not to be included during release
# env_type: "beta"
# The following is the configuration which will be used by the bedrock bot integration
config:
# This is the number of messages saved for each chat history to use as context. Please consider Bedrock's token and throttling limits.
maxHistory: 100
# aws:
# region: 'us-east-1'
# accountId: 'random'
# Uncomment the below section and provide the knowledge base and guidelines to use your knowledge base with bedrock.
# knowledgeBase:
# id: 'HYSL6DQKQB'
# guidelines: |
# - IMPORTANT: Only make ONE knowledge base query per user message to avoid rate limits
# - Do not make follow-up queries to verify or double-check information you've already received
# - If your first query doesn't return all the information you need, respond with what you know rather than querying again
# - Synthesize information from your first query instead of making multiple queries
# - Never enter a loop of repeatedly querying the knowledge base for the same information
# Example of GOOD knowledge base usage:
# User: "What's our security policy?"
# Assistant: [Makes ONE knowledge base query, then synthesizes a complete response]
# Example of BAD knowledge base usage:
# User: "What's our security policy?"
# Assistant: [Makes initial query about security policy, then makes additional queries to verify details]