dify icon indicating copy to clipboard operation
dify copied to clipboard

can not save in the bedrock setting page.

Open freeword2020 opened this issue 2 years ago • 4 comments

Self Checks

  • [X] This is only for bug report, if you would like to ask a quesion, please head to Discussions.
  • [X] I have searched for existing issues search for existing issues, including closed ones.
  • [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [X] Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

error can not save

✔️ Expected Behavior

when I save after inputting the wrong content, there will be an error info. But when I input the right content, the save button can not work. Can not save the settings of bedrock.

❌ Actual Behavior

But when I input the right content, the save button can not work. Can not save the settings of bedrock.

freeword2020 avatar Apr 24 '24 16:04 freeword2020

It sounds like you're encountering an issue where the "Save" button on the Bedrock settings page isn't working even with the correct AWS configuration details entered. This could be due to a few reasons:

  1. Validation Checks: Ensure all required fields, including the dataset name and AWS configuration details (aws_access_key_id, aws_secret_access_key, and aws_region), are correctly filled out. The "Save" button may not activate if any required field is missing or incorrect.

  2. AWS Credentials and Permissions: The issue might stem from the AWS credentials provided. They need to have the necessary permissions for the operations Bedrock is attempting to perform. If the credentials are expired, incorrect, or lack permissions for the selected AWS region or services, this could prevent saving.

  3. Error Messages or Logs: If possible, share any error messages or logs you encounter when the "Save" button fails to work. This information can be crucial for diagnosing the problem more accurately.

Make sure to double-check the AWS region and ensure it's supported, and verify that all required fields are correctly filled and validated. If after these checks the problem persists, providing more detailed error information could help in identifying the root cause.

Details

Sources


About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

dosubot[bot] avatar Apr 24 '24 16:04 dosubot[bot]

can you try starting afresh? can't seem to reproduce this

guchenhe avatar Apr 25 '24 06:04 guchenhe

leave the model name empty. It works for me.

kerlion avatar Apr 26 '24 05:04 kerlion

wrong model id.

longzhihun avatar Apr 27 '24 12:04 longzhihun

Please upgrade to latest version to see if this issue persists. :)

crazywoola avatar May 28 '24 07:05 crazywoola