ahmedverbruggh
/
spm
1
0
Code Issues Packages Projects Wiki

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

Ahmed Verbrugghen 2025-04-12 05:43:11 +08:00
parent 35e71a636e
commit d75bd1091b
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](https://staff-pro.org)'s first-generation frontier model, DeepSeek-R1, along with the distilled versions varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative [AI](https://topbazz.com) concepts on AWS.<br>
<br>In this post, we show how to get begun with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to release the distilled versions of the models as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language design (LLM) developed by DeepSeek [AI](http://101.132.136.5:8030) that uses [support finding](https://git.fanwikis.org) out to improve thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential differentiating function is its reinforcement knowing (RL) step, which was utilized to refine the design's responses beyond the basic pre-training and fine-tuning procedure. By including RL, DeepSeek-R1 can adjust better to user feedback and goals, eventually enhancing both significance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, suggesting it's equipped to break down complex questions and reason through them in a detailed manner. This assisted thinking process permits the model to produce more precise, transparent, and detailed responses. This model combines RL-based fine-tuning with CoT capabilities, aiming to produce structured responses while concentrating on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has actually caught the industry's attention as a flexible text-generation model that can be integrated into different workflows such as agents, rational thinking and data interpretation tasks.<br>
<br>DeepSeek-R1 [utilizes](http://www.xn--1-2n1f41hm3fn0i3wcd3gi8ldhk.com) a Mix of Experts (MoE) architecture and is 671 billion [criteria](http://git.estoneinfo.com) in size. The MoE architecture enables activation of 37 billion parameters, enabling efficient inference by routing inquiries to the most pertinent professional "clusters." This [technique](https://git.obo.cash) allows the model to focus on different problem domains while maintaining general effectiveness. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge circumstances to release the model. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 model to more effective architectures based upon popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a [procedure](https://newtheories.info) of training smaller, more effective models to mimic the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as an instructor design.<br>
<br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest releasing this design with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent hazardous content, and assess designs against essential security criteria. At the time of writing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, [systemcheck-wiki.de](https://systemcheck-wiki.de/index.php?title=Benutzer:FernandoSimmonds) Bedrock Guardrails supports only the ApplyGuardrail API. You can create numerous guardrails tailored to various usage cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls across your generative [AI](https://ospitalierii.ro) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e instance. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and confirm 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 releasing. To ask for a limit boost, develop a limit boost request and reach out to your account group.<br>
<br>Because you will be [deploying](https://pittsburghpenguinsclub.com) this design with [Amazon Bedrock](https://source.coderefinery.org) Guardrails, make certain you have the right AWS Identity and [hb9lc.org](https://www.hb9lc.org/wiki/index.php/User:CindaFriday) Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For instructions, see Set up approvals to utilize guardrails for [genbecle.com](https://www.genbecle.com/index.php?title=Utilisateur:TerriPiper3180) material filtering.<br>
<br>Implementing guardrails with the [ApplyGuardrail](http://ev-gateway.com) API<br>
<br>Amazon Bedrock Guardrails permits you to introduce safeguards, [genbecle.com](https://www.genbecle.com/index.php?title=Utilisateur:ConstanceKimbell) prevent harmful material, and evaluate models against crucial safety requirements. You can execute precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11857434) model responses [deployed](https://gitlab-mirror.scale.sc) on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo.<br>
<br>The general circulation involves the following actions: 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. After receiving the design's output, another guardrail check is used. If the output passes this final check, it's returned as the result. However, if either the input or output is intervened by the guardrail, a message is returned indicating the nature of the intervention and whether it occurred at the input or output phase. The examples showcased in the following sections show reasoning utilizing 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 structure](https://lifeinsuranceacademy.org) models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:<br>
<br>1. On the Amazon Bedrock console, pick Model catalog under Foundation designs in the navigation pane.
At the time of writing this post, you can use the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and select the DeepSeek-R1 design.<br>
<br>The model detail page supplies vital details about the model's capabilities, pricing structure, and implementation guidelines. You can discover detailed use instructions, consisting of sample API calls and code snippets for integration. The design supports different [text generation](https://stepstage.fr) jobs, [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11857434) including material creation, code generation, and concern answering, utilizing its [support learning](https://jovita.com) optimization and CoT thinking abilities.
The page also consists of implementation options and licensing details to help you get begun with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, select Deploy.<br>
<br>You will be triggered to configure the release details for DeepSeek-R1. The design ID will be [pre-populated](https://www.towingdrivers.com).
4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters).
5. For Variety of circumstances, enter a variety of circumstances (in between 1-100).
6. For example type, choose your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up innovative security and facilities settings, including virtual personal cloud (VPC) networking, service function permissions, and file encryption settings. For many utilize cases, the default settings will work well. However, for production implementations, you may wish to examine these settings to line up with your organization's security and compliance requirements.
7. Choose Deploy to begin utilizing the model.<br>
<br>When the release is total, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
8. Choose Open in play ground to access an interactive user interface where you can experiment with various triggers and adjust design specifications like temperature level and maximum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimum results. For example, content for reasoning.<br>
<br>This is an outstanding way to explore the design's thinking and text generation capabilities before incorporating it into your applications. The play ground provides instant feedback, helping you comprehend how the design reacts to numerous inputs and letting you fine-tune your triggers for optimal outcomes.<br>
<br>You can rapidly check the design in the playground through the UI. However, to conjure up the [released model](http://82.157.77.1203000) programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run inference using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform reasoning utilizing a deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo. After you have actually developed the guardrail, use the following code to implement guardrails. The script [initializes](http://gitlab.ifsbank.com.cn) the bedrock_runtime client, configures inference criteria, and sends a demand to [generate text](https://nemoserver.iict.bas.bg) based upon a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, built-in algorithms, and prebuilt ML [options](https://1millionjobsmw.com) that you can deploy with just a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your data, and release them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart provides 2 practical approaches: using the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both approaches to help you pick the method that finest suits your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps to deploy DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the SageMaker console, choose Studio in the navigation pane.
2. First-time users will be [prompted](https://socialeconomy4ces-wiki.auth.gr) to create a domain.
3. On the SageMaker Studio console, select JumpStart in the [navigation pane](https://www.graysontalent.com).<br>
<br>The model web browser shows available models, 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 reveals crucial details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if suitable), showing that this design can be signed up with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to invoke the model<br>
<br>5. Choose the model card to see the design details page.<br>
<br>The design details page consists of the following details:<br>
<br>- The design name and provider details.
Deploy button to release the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of essential details, such as:<br>
<br>- Model description.
- License details.
- Technical specifications.
- Usage guidelines<br>
<br>Before you deploy the design, it's recommended to review the model details and license terms to validate compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with implementation.<br>
<br>7. For Endpoint name, use the automatically created name or develop a custom-made one.
8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the variety of instances (default: 1).
Selecting suitable instance types and counts is vital for cost and performance optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time inference is picked by default. This is optimized for sustained traffic and low latency.
10. Review all configurations for accuracy. For this model, we highly advise sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the design.<br>
<br>The release process can take [numerous](http://112.74.102.696688) minutes to complete.<br>
<br>When implementation is complete, your endpoint status will change to InService. At this point, the model is all set to accept inference requests through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the deployment is complete, you can conjure up the design using a SageMaker runtime customer and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SDK<br>
<br>To start with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the necessary AWS approvals and environment setup. The following is a detailed code example that shows how to deploy and use DeepSeek-R1 for [reasoning programmatically](https://tikness.com). The code for deploying the model is provided in the Github here. You can clone the notebook and range from SageMaker Studio.<br>
<br>You can run additional demands against the predictor:<br>
<br>Implement guardrails and run reasoning with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail utilizing the Amazon Bedrock console or the API, and [yewiki.org](https://www.yewiki.org/User:ReginaldOster32) implement it as shown in the following code:<br>
<br>Clean up<br>
<br>To [prevent undesirable](http://168.100.224.793000) charges, complete the actions in this area to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you released the model using Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace implementations.
2. In the [Managed releases](https://git.gumoio.com) area, locate the endpoint you desire to delete.
3. Select the endpoint, and on the Actions menu, [pick Delete](http://aat.or.tz).
4. Verify the endpoint details to make certain you're erasing the proper implementation: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you released will sustain expenses if you leave it running. Use the following code to erase the endpoint if you want to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we explored how you can access and deploy the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, refer to Use Amazon Bedrock tooling with [Amazon SageMaker](https://blogville.in.net) JumpStart models, SageMaker JumpStart 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://h2kelim.com) companies construct innovative options using AWS services and accelerated compute. Currently, he is focused on developing methods for fine-tuning and enhancing the reasoning efficiency of large language designs. In his free time, Vivek takes pleasure in treking, seeing films, and attempting various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://aiviu.app) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](https://boonbac.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](https://dyipniflix.com) with the Third-Party Model Science group at AWS.<br>
<br>[Banu Nagasundaram](https://www.flirtywoo.com) leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://git.chartsoft.cn) hub. She is passionate about developing solutions that help consumers accelerate their [AI](https://sparcle.cn) journey and unlock service value.<br>