langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Models imported in AWS Bedrock #8235

New Issue
Closed
opened 2026-02-21 18:24:37 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:24:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @hedongxin on GitHub (Feb 13, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I imported the DeepSeek-R1-Distill-Llama-8B model into AWS Bedrock, but upon attempting to integrate it with Dify, I discovered that Dify is unable to recognize the model I imported. I would like to inquire whether Dify supports models imported into AWS Bedrock?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @hedongxin on GitHub (Feb 13, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I imported the DeepSeek-R1-Distill-Llama-8B model into AWS Bedrock, but upon attempting to integrate it with Dify, I discovered that Dify is unable to recognize the model I imported. I would like to inquire whether Dify supports models imported into AWS Bedrock? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo closed this issue 2026-02-21 18:24:37 -05:00
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 13, 2025):

Hello @hedongxin! I'm here to help you with any bugs, questions, or contributions you might have regarding the AWS Bedrock and Dify integration. I'm a bot designed to assist you while you wait for a human maintainer. Let me know how I can assist you!

Yes, Dify supports models imported into AWS Bedrock, such as the DeepSeek-R1-Distill-Llama-8B model. The integration process involves deploying the DeepSeek model on the Bedrock Marketplace platform and then connecting it to the Dify platform. This is done by obtaining the SageMaker endpoint from Bedrock and configuring it in Dify [1][2].

If Dify fails to recognize the model, you can try the following troubleshooting steps:

  1. Ensure that the instance is correctly configured and that the AWS permissions are set properly.
  2. Verify that the Endpoint parameter is correctly obtained and entered. This parameter can be found on the AWS Bedrock Marketplace's Endpoint page.
  3. If the Endpoint parameter is not visible or there are issues, try redeploying the model.
  4. If problems persist, consider consulting AWS customer support for further assistance [3].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report

@dosubot[bot] commented on GitHub (Feb 13, 2025): <!-- Greeting --> Hello @hedongxin! I'm here to help you with any bugs, questions, or contributions you might have regarding the AWS Bedrock and Dify integration. I'm a bot designed to assist you while you wait for a human maintainer. Let me know how I can assist you! <!-- Answer --> Yes, Dify supports models imported into AWS Bedrock, such as the DeepSeek-R1-Distill-Llama-8B model. The integration process involves deploying the DeepSeek model on the Bedrock Marketplace platform and then connecting it to the Dify platform. This is done by obtaining the SageMaker endpoint from Bedrock and configuring it in Dify <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/development/models-integration/aws-bedrock-deepseek.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/development/models-integration/aws-bedrock-deepseek.md)</sup>. If Dify fails to recognize the model, you can try the following troubleshooting steps: 1. Ensure that the instance is correctly configured and that the AWS permissions are set properly. 2. Verify that the Endpoint parameter is correctly obtained and entered. This parameter can be found on the AWS Bedrock Marketplace's Endpoint page. 3. If the Endpoint parameter is not visible or there are issues, try redeploying the model. 4. If problems persist, consider consulting AWS customer support for further assistance <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/development/models-integration/aws-bedrock-deepseek.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/2aadda1b-1ddb-4eb4-8aa8-833f7e45fd45?feedback_type=bug_report)</sup>
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@hedongxin commented on GitHub (Feb 13, 2025):

"I imported the DeepSeek-R1-Distill-Llama-8B model into AWS Bedrock (not from the AWS Marketplace). However, when trying to integrate it with Dify, I found that Dify cannot recognize the model I imported. Does Dify support models that are imported into AWS Bedrock?"

@hedongxin commented on GitHub (Feb 13, 2025): "I imported the DeepSeek-R1-Distill-Llama-8B model into AWS Bedrock (not from the AWS Marketplace). However, when trying to integrate it with Dify, I found that Dify cannot recognize the model I imported. Does Dify support models that are imported into AWS Bedrock?"
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 13, 2025):

Dify does support models imported into AWS Bedrock. However, specific configuration settings are required for Dify to recognize these models. You need to ensure that the SageMaker endpoint is correctly configured in Dify. This involves setting up the sagemaker_endpoint in the configuration file, along with optional AWS credentials and region settings if needed [1].

If the model is not recognized, double-check the endpoint and configuration settings. Ensure that the endpoint is correctly obtained from AWS Bedrock and entered into Dify. If issues persist, verify your AWS permissions and consider redeploying the model.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report

@dosubot[bot] commented on GitHub (Feb 13, 2025): <!-- Answer --> Dify does support models imported into AWS Bedrock. However, specific configuration settings are required for Dify to recognize these models. You need to ensure that the SageMaker endpoint is correctly configured in Dify. This involves setting up the `sagemaker_endpoint` in the configuration file, along with optional AWS credentials and region settings if needed <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/model_runtime/model_providers/sagemaker/sagemaker.yaml)</sup>. If the model is not recognized, double-check the endpoint and configuration settings. Ensure that the endpoint is correctly obtained from AWS Bedrock and entered into Dify. If issues persist, verify your AWS permissions and consider redeploying the model. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/0bf494d9-310b-4b94-a92b-1a3ce8a7bb30?feedback_type=bug_report)</sup>
yindo commented 2026-02-21 18:24:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 13, 2025):

Well, you need to use Sagemaker instead for now, afaik, we have already report this to AWS side as well, the problem is they do not have a deployed MaaS service for DeepSeek series.

@crazywoola commented on GitHub (Feb 13, 2025): Well, you need to use Sagemaker instead for now, afaik, we have already report this to AWS side as well, the problem is they do not have a deployed MaaS service for DeepSeek series.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8235
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?