Update the solution
If you have previously deployed the solution, follow this procedure to update the QnABot on AWS CloudFormation stack to get the latest version of the solution’s framework.
-
Sign in to the AWS CloudFormation console
, select your existing QnABot on AWS CloudFormation stack, and choose Update. -
Select Replace current template.
-
Enter the appropriate Amazon S3 URL:
-
If using the default main template: https://solutions-reference.s3.amazonaws.com/qnabot-on-aws/latest/qnabot-on-aws-main.template
-
If using the VPC template: https://solutions-reference.s3.amazonaws.com/qnabot-on-aws/latest/qnabot-on-aws-vpc.template
-
-
Under Parameters, review the parameters for the template and modify them as necessary. Refer to Step 1: Launch the stack for details about the parameters.
-
Choose Next.
-
On the Configure stack options page, choose Next.
-
On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template might create AWS Identity and Access Management (IAM) resources.
-
Choose View change set and verify the changes.
-
Choose Update stack to deploy the stack.
Note
For those upgrading from v5.4.X
If you are upgrading from a deployment with LLMApi set to
SAGEMAKER then set this value to DISABLED before
upgrading. After upgrading, return this value back to SAGEMAKER.
You can view the status of the stack in the AWS CloudFormation console in the Status column. You should receive a UPDATE_COMPLETE status in approximately 30
minutes.
Note
If you have previously deployed the solution but do not want to perform in-place upgrade
or encountered issues during in-place upgrade or in case of a breaking change which does not
allow you to upgrade in-place, please refer to migration section in this README.md
Note
For those upgrading to v6.1.X and above
You might not see your previous executions on the Import, Export, and Test All pages
disappear. To restore them, go to the respective S3 buckets and copy all the folders
containing the data or status for each function (Import, Export, Test All) to the
ContentDesignerOutputBucket. Rename them as ‘data-{function}’ or
‘status-{function}’. Omitting this step doesn't effect your QandAs and only
impacts these specific pages.
