adolph6507920
/
azure
1
0
Code Issues Packages Projects Wiki

Add DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart

Adolph Alonzo 2025-04-10 18:15:32 +08:00
parent ff175ede6b
commit 2c88b3f55d
1 changed files with 93 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart.-.md Normal file

@ -0,0 +1,93 @@
<br>Today, we are thrilled to announce that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://hmind.kr)'s first-generation frontier design, DeepSeek-R1, along with the distilled versions varying from 1.5 to 70 billion [parameters](http://git.zhongjie51.com) to construct, [yewiki.org](https://www.yewiki.org/User:AntjeLantz30) experiment, and properly scale your [generative](http://git.acdts.top3000) [AI](https://video.chops.com) ideas on AWS.<br>
<br>In this post, we show how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to release the [distilled variations](https://gitlab.innive.com) of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](https://24frameshub.com) that uses reinforcement discovering to enhance reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key differentiating feature is its support learning (RL) step, which was utilized to improve the model's responses beyond the standard pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adapt better to user feedback and objectives, ultimately boosting both significance and [clarity](http://code.hzqykeji.com). In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, indicating it's geared up to break down intricate questions and reason through them in a detailed manner. This directed thinking process allows the model to produce more accurate, transparent, and detailed responses. This design combines RL-based fine-tuning with CoT abilities, aiming to generate structured responses while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has captured the market's attention as a versatile text-generation model that can be incorporated into different workflows such as agents, rational thinking and data interpretation tasks.<br>
<br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion specifications, enabling efficient inference by routing questions to the most appropriate specialist "clusters." This approach enables the design to specialize in different problem domains while maintaining total performance. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge circumstances to release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 model to more [efficient architectures](http://47.103.91.16050903) based on popular open designs like Qwen (1.5 B, [gratisafhalen.be](https://gratisafhalen.be/author/caryencarna/) 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more efficient designs to mimic the habits and thinking patterns of the bigger DeepSeek-R1 model, utilizing it as an instructor design.<br>
<br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend deploying this design with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid [harmful](https://cn.wejob.info) content, and assess models against key security criteria. At the time of composing this blog site, for DeepSeek-R1 [releases](https://social-lancer.com) on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create numerous guardrails tailored to different usage cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing security controls throughout your generative [AI](https://firefish.dev) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, you need access to an ml.p5e circumstances. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, [select Amazon](http://106.55.61.1283000) SageMaker, and verify you're utilizing ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To request a limit increase, create a limitation boost demand and connect to your account group.<br>
<br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) authorizations to utilize Amazon Bedrock Guardrails. For guidelines, see Establish consents to use guardrails for content [filtering](http://gbtk.com).<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>[Amazon Bedrock](http://154.64.253.773000) Guardrails allows you to present safeguards, avoid hazardous material, and evaluate models against essential security criteria. You can execute precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to assess user inputs and model actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail utilizing the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
<br>The general flow involves the following steps: First, the system receives an input for the design. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the design for [reasoning](https://service.lanzainc.xyz10281). After getting the model's output, another guardrail check is used. If the output passes this final check, it's returned as the outcome. However, if either the input or output is intervened by the guardrail, a message is returned suggesting the nature of the intervention and whether it happened at the input or output stage. The examples showcased in the following sections demonstrate reasoning using this API.<br>
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
<br>Amazon Bedrock Marketplace gives you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can use the InvokeModel API to conjure up the design. It does not support Converse APIs and other Amazon Bedrock [tooling](https://sharingopportunities.com).
2. Filter for DeepSeek as a supplier and select the DeepSeek-R1 design.<br>
<br>The design detail page offers important details about the model's capabilities, pricing structure, and application standards. You can find detailed usage instructions, consisting of sample API calls and code bits for integration. The design supports different text generation tasks, consisting of content development, code generation, and concern answering, using its reinforcement finding out optimization and CoT thinking capabilities.
The page also consists of deployment options and licensing details to help you get going with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, pick Deploy.<br>
<br>You will be triggered to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
5. For Number of instances, go into a variety of circumstances (between 1-100).
6. For example type, pick your instance type. For [larsaluarna.se](http://www.larsaluarna.se/index.php/User:DZEKathryn) optimum efficiency with DeepSeek-R1, [kousokuwiki.org](http://kousokuwiki.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:JaniceProeschel) a GPU-based instance type like ml.p5e.48 xlarge is suggested.
Optionally, you can configure innovative security and infrastructure settings, including virtual personal cloud (VPC) networking, service function authorizations, and file encryption settings. For many utilize cases, the default settings will work well. However, for production releases, you might wish to evaluate these settings to align with your organization's security and [systemcheck-wiki.de](https://systemcheck-wiki.de/index.php?title=Benutzer:RaymonQ0833) compliance requirements.
7. Choose Deploy to begin utilizing the design.<br>
<br>When the deployment is complete, you can evaluate DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
8. Choose Open in play area to access an interactive interface where you can experiment with various prompts and adjust model criteria like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal results. For example, content for reasoning.<br>
<br>This is an excellent method to check out the [design's reasoning](https://git.rggn.org) and text generation abilities before incorporating it into your applications. The playground provides instant feedback, helping you understand how the design reacts to various inputs and you tweak your prompts for optimal outcomes.<br>
<br>You can rapidly test the design in the play area through the UI. However, to invoke the deployed model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform reasoning utilizing a deployed DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have created the guardrail, utilize the following code to carry out guardrails. The script initializes the bedrock_runtime client, configures inference parameters, and sends a request to create text based on a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and prebuilt ML options that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can [tailor pre-trained](https://eschoolgates.com) designs to your usage case, with your information, and release them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart uses 2 convenient approaches: utilizing the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's [explore](https://git.lona-development.org) both approaches to assist you choose the method that best suits your requirements.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following actions to deploy DeepSeek-R1 utilizing SageMaker JumpStart:<br>
<br>1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be prompted to produce a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The model web browser displays available designs, with details like the supplier name and model capabilities.<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card.
Each model card shows key details, including:<br>
<br>- Model name
- Provider name
- Task [classification](http://famedoot.in) (for instance, Text Generation).
Bedrock Ready badge (if appropriate), showing that this model can be registered with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the design<br>
<br>5. Choose the model card to see the model details page.<br>
<br>The model details page includes the following details:<br>
<br>- The design name and provider details.
Deploy button to release the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of important details, such as:<br>
<br>- Model description.
- License details.
- Technical specs.
- Usage standards<br>
<br>Before you release the model, it's recommended to examine the [model details](http://47.116.115.15610081) and license terms to verify compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with [deployment](https://social.stssconstruction.com).<br>
<br>7. For Endpoint name, use the automatically produced name or develop a custom one.
8. For example type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the number of circumstances (default: 1).
Selecting proper circumstances types and counts is important for cost and performance optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time inference is picked by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for accuracy. For this design, we strongly recommend adhering to SageMaker JumpStart [default](http://dndplacement.com) settings and making certain that network isolation remains in place.
11. Choose Deploy to release the design.<br>
<br>The implementation process can take numerous minutes to complete.<br>
<br>When implementation is total, your endpoint status will change to InService. At this point, the design is prepared to accept inference requests through the endpoint. You can keep an eye on the implementation progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is total, you can conjure up the design utilizing a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To get begun with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the needed AWS authorizations and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for inference programmatically. The code for [it-viking.ch](http://it-viking.ch/index.php/User:SherryWur1) deploying the design is offered in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
<br>You can run extra requests against the predictor:<br>
<br>Implement guardrails and run inference with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can likewise utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the [Amazon Bedrock](http://182.92.202.1133000) console or the API, and implement it as displayed in the following code:<br>
<br>Clean up<br>
<br>To prevent unwanted charges, complete the actions in this section to tidy up your [resources](http://bolsatrabajo.cusur.udg.mx).<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you deployed the model using Amazon Bedrock Marketplace, complete the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, choose Marketplace implementations.
2. In the Managed implementations area, find the endpoint you desire to delete.
3. Select the endpoint, and on the Actions menu, pick Delete.
4. Verify the endpoint details to make certain you're deleting the appropriate implementation: 1. [Endpoint](https://www.opad.biz) name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you released will sustain costs if you leave it running. Use the following code to erase the endpoint if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we checked out how you can access and deploy the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get begun. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, [SageMaker JumpStart](http://103.235.16.813000) pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going with Amazon SageMaker JumpStart.<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative [AI](http://secretour.xyz) business build innovative services using AWS services and sped up [calculate](http://120.48.7.2503000). Currently, he is focused on developing techniques for fine-tuning and optimizing the [inference efficiency](http://94.110.125.2503000) of large language designs. In his spare time, Vivek delights in treking, [enjoying](https://git.gocasts.ir) movies, and trying various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://git.cloudtui.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](http://xn--ok0b850bc3bx9c.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](http://ptube.site) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://www.vadio.com) hub. She is passionate about building solutions that help clients accelerate their [AI](https://i10audio.com) journey and unlock service value.<br>