madeleinebond1
/
afrixis
1
0
Code Issues Packages Projects Wiki

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

Madeleine Bond 2025-02-13 03:01:39 +08:00
commit d2f1e70c39
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](https://video.spacenets.ru) are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://gl.ignite-vision.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions varying from 1.5 to 70 billion criteria to develop, experiment, and properly scale your generative [AI](http://www.hnyqy.net:3000) ideas 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 comparable steps to release the distilled variations of the designs as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://git.eisenwiener.com) that utilizes reinforcement learning to improve thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. A crucial identifying feature is its reinforcement learning (RL) step, which was utilized to improve the model's responses beyond the basic pre-training and tweak procedure. By including RL, DeepSeek-R1 can adapt more successfully to user feedback and goals, ultimately enhancing both significance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, implying it's equipped to break down complicated queries and factor through them in a [detailed manner](http://motojic.com). This guided reasoning procedure permits the design to produce more precise, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT capabilities, aiming to create structured reactions while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually caught the industry's attention as a flexible text-generation design that can be incorporated into various workflows such as agents, sensible thinking and data analysis tasks.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture enables activation of 37 billion criteria, enabling effective inference by routing questions to the most pertinent professional "clusters." This technique allows the model to focus on various issue domains while maintaining total efficiency. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 [distilled designs](https://x-like.ir) bring the reasoning abilities of the main R1 model to more effective architectures based upon popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller sized, more efficient models to simulate the behavior and reasoning patterns of the bigger DeepSeek-R1 design, utilizing it as a teacher design.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest deploying this model with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid damaging content, and evaluate designs against crucial security requirements. At the time of writing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop several [guardrails tailored](http://git.indep.gob.mx) to different usage cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative [AI](https://www.hyxjzh.cn:13000) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, [pick Amazon](https://jobs.alibeyk.com) 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](https://ravadasolutions.com) in the AWS Region you are releasing. To ask for a limit increase, produce a limitation increase request and reach out to your account group.<br>
<br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) [approvals](http://git.ningdatech.com) to utilize Amazon Bedrock Guardrails. For directions, see Establish consents to use [guardrails](https://academy.theunemployedceo.org) for content [filtering](http://61.174.243.2815863).<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to present safeguards, avoid hazardous material, and assess models against essential safety requirements. You can carry out precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to [examine](https://tiktokbeans.com) user inputs and model actions deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to [produce](http://113.177.27.2002033) the guardrail, see the GitHub repo.<br>
<br>The basic circulation [involves](https://git.lmh5.com) the following steps: First, the system gets an input for the model. 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 getting the model's output, another guardrail check is used. If the output passes this last check, it's returned as the outcome. However, if either the input or output is stepped in by the guardrail, a message is returned indicating the nature of the [intervention](https://ces-emprego.com) and whether it occurred at the input or output phase. The examples showcased in the following sections show inference 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 designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, pick Model brochure under Foundation models in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for [DeepSeek](http://39.108.86.523000) as a supplier and pick the DeepSeek-R1 model.<br>
<br>The design detail page offers vital details about the model's capabilities, pricing structure, and implementation guidelines. You can discover detailed use guidelines, consisting of [sample API](https://git.tbaer.de) calls and code snippets for integration. The design supports different text [generation](https://955x.com) jobs, including material creation, code generation, and question answering, utilizing its [support finding](http://krasnoselka.od.ua) out optimization and CoT thinking abilities.
The page also includes implementation alternatives and licensing details to help you get going with DeepSeek-R1 in your applications.
3. To begin utilizing DeepSeek-R1, select Deploy.<br>
<br>You will be prompted to set up the [implementation details](http://82.156.184.993000) for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters).
5. For Number of circumstances, get in a variety of instances (in between 1-100).
6. For Instance type, select your circumstances type. For optimum performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
Optionally, you can set up innovative security and infrastructure settings, consisting of virtual private cloud (VPC) networking, [service role](https://titikaka.unap.edu.pe) permissions, and file encryption settings. For many utilize cases, the default settings will work well. However, for production releases, you might wish to examine these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to begin using the model.<br>
<br>When the release is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
8. Choose Open in play ground to access an interactive interface where you can experiment with different prompts and change design specifications like temperature and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For example, material for reasoning.<br>
<br>This is an excellent method to explore the design's reasoning and text generation abilities before incorporating it into your applications. The play ground provides instant feedback, [helping](http://122.51.51.353000) you understand how the design reacts to [numerous](https://lovn1world.com) inputs and letting you fine-tune your prompts for optimum outcomes.<br>
<br>You can [rapidly](https://dev.nebulun.com) test the design in the play ground through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference utilizing guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to carry out reasoning using a [released](http://120.55.59.896023) DeepSeek-R1 design through Amazon Bedrock utilizing 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 created the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures inference parameters, and sends out a to [generate text](https://wiki.fablabbcn.org) based on a user prompt.<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 solutions that you can deploy with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained models 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 offers 2 practical approaches: utilizing the user-friendly SageMaker JumpStart UI or [engel-und-waisen.de](http://www.engel-und-waisen.de/index.php/Benutzer:RoxanneRawson) carrying out programmatically through the SageMaker Python SDK. Let's explore both methods to assist you select the technique that best matches your requirements.<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 triggered to develop a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
<br>The model web browser shows available models, with details like the supplier name and model abilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each design card shows crucial details, including:<br>
<br>- Model name
- Provider name
- Task [category](http://8.140.229.2103000) (for example, Text Generation).
Bedrock Ready badge (if appropriate), suggesting 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 [design details](https://animployment.com) page consists of the following details:<br>
<br>- The model name and company details.
Deploy button to deploy the model.
About and [Notebooks tabs](https://careers.tu-varna.bg) with detailed details<br>
<br>The About tab includes crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical requirements.
- Usage guidelines<br>
<br>Before you deploy the model, it's recommended to review the model details and license terms to verify compatibility with your use case.<br>
<br>6. Choose Deploy to continue with deployment.<br>
<br>7. For Endpoint name, use the immediately produced name or create a customized one.
8. For Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance 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 [yewiki.org](https://www.yewiki.org/User:JefferyGoudie23) low latency.
10. Review all configurations for precision. For this model, we strongly suggest sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to release the model.<br>
<br>The deployment procedure can take a number of minutes to finish.<br>
<br>When deployment is total, your endpoint status will change to InService. At this moment, the model is all set to accept inference [requests](https://giftconnect.in) through the endpoint. You can monitor the release progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is total, you can invoke the model using a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To get going with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS permissions 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 deploying the design is offered in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
<br>You can run additional requests against the predictor:<br>
<br>Implement guardrails and run inference 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 using the Amazon Bedrock console or the API, and implement it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To prevent undesirable charges, finish the actions in this section to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you deployed the design utilizing Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace implementations.
2. In the Managed releases area, locate the endpoint you wish to delete.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you're erasing the proper release: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart design you released will sustain expenses if you leave it running. Use the following code to erase the endpoint if you wish to stop [sustaining charges](https://gogolive.biz). For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we checked out how you can access and release the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker [JumpStart](https://tikplenty.com) in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, [pipewiki.org](https://pipewiki.org/wiki/index.php/User:Alfie04M080) refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon [Bedrock](http://47.112.200.2063000) Marketplace, and Starting with Amazon SageMaker JumpStart.<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging generative [AI](http://8.134.38.106:3000) business develop ingenious services utilizing AWS services and sped up calculate. Currently, he is focused on developing strategies for fine-tuning and [enhancing](http://120.237.152.2188888) the inference performance of large language models. In his leisure time, Vivek enjoys hiking, viewing motion pictures, and attempting various cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://gitea.robertops.com) Specialist Solutions [Architect](https://soucial.net) with the Third-Party Model Science team at AWS. His location of focus is AWS [AI](https://samisg.eu:8443) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and [Bioinformatics](http://jobpanda.co.uk).<br>
<br>Jonathan Evans is a Professional Solutions Architect dealing with generative [AI](http://47.108.78.218:28999) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://git.gz.internal.jumaiyx.cn) hub. She is passionate about constructing options that assist clients accelerate their [AI](https://abadeez.com) journey and unlock organization value.<br>