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

2025-02-09 06:12:15 +08:00 · 2025-02-09 06:12:15 +08:00 · 7ec7e6b5b0
commit 7ec7e6b5b0
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are delighted to reveal that DeepSeek R1 distilled Llama and Qwen designs are available through [Amazon Bedrock](http://funnydollar.ru) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](https://codes.tools.asitavsen.com)'s [first-generation frontier](https://www.jobsition.com) design, DeepSeek-R1, along with the distilled variations ranging from 1.5 to 70 billion criteria to construct, experiment, and responsibly scale your generative [AI](http://tv.houseslands.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 comparable steps to [release](https://turizm.md) the distilled variations of the models too.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) established by DeepSeek [AI](https://fondnauk.ru) that uses support learning to improve reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key identifying function is its support knowing (RL) action, which was used to improve the model's actions beyond the standard pre-training and fine-tuning procedure. By integrating RL, DeepSeek-R1 can adjust better to user feedback and objectives, eventually enhancing both relevance and  [engel-und-waisen.de](http://www.engel-und-waisen.de/index.php/Benutzer:TabithaWithers0) clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) approach, meaning it's geared up to break down complicated queries and factor through them in a detailed way. This directed thinking process allows the model to produce more accurate, transparent,  [wiki.myamens.com](http://wiki.myamens.com/index.php/User:Aurora61O13036) and detailed responses. This model combines RL-based fine-tuning with CoT abilities, aiming to generate structured actions while focusing on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually captured the industry's attention as a flexible text-generation design that can be integrated into numerous workflows such as agents, sensible reasoning 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 parameters, enabling effective reasoning by routing questions to the most pertinent expert "clusters." This method enables the model to focus on various problem domains while maintaining overall effectiveness. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 [xlarge circumstances](https://foris.gr) to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the thinking [abilities](https://gitlab.liangzhicn.com) of the main R1 design to more efficient architectures based on [popular](https://saek-kerkiras.edu.gr) open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller sized, more efficient models to mimic the behavior and thinking patterns of the bigger DeepSeek-R1 design, using it as an instructor model.<br>
 <br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest deploying this design with guardrails in location. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging content, and examine models against crucial security criteria. At the time of composing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create several guardrails tailored to different use cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing safety controls throughout your generative [AI](https://cl-system.jp) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you need access to an ml.p5e instance. To inspect if you have quotas for P5e, open the  console and under AWS Services, choose Amazon SageMaker, and validate you're using 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 ask for a limit increase, create a limit boost demand and reach out to your account team.<br>
 <br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To [Management](http://git.chilidoginteractive.com3000) (IAM) permissions to utilize Amazon Bedrock Guardrails. For guidelines, see Establish consents to use guardrails for material filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails enables you to introduce safeguards, avoid hazardous content, and assess designs against essential safety criteria. You can implement precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and [model reactions](http://101.231.37.1708087) released 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 develop the guardrail, see the [GitHub repo](https://gitlab-mirror.scale.sc).<br>
 <br>The basic circulation involves the following steps: First, the system receives 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 [design's](http://tv.houseslands.com) output, another guardrail check is used. If the output passes this final check, it's returned as the last outcome. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the intervention and whether it occurred at the input or output phase. The examples showcased in the following sections show [inference utilizing](http://appleacademy.kr) this API.<br>
 <br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
 <br>Amazon [Bedrock Marketplace](http://41.111.206.1753000) provides you access to over 100 popular, emerging, and specialized structure designs (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 models in the navigation pane.
 At the time of writing this post, you can [utilize](https://hub.tkgamestudios.com) the InvokeModel API to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a service provider and pick the DeepSeek-R1 model.<br>
 <br>The design detail page supplies important details about the design's capabilities, rates structure, and execution guidelines. You can find [detailed usage](http://106.227.68.1873000) directions, consisting of sample API calls and code snippets for [integration](https://git.xedus.ru). The model supports different text generation jobs, including material development, code generation, and concern answering, using its reinforcement discovering optimization and CoT thinking capabilities.
 The page likewise includes implementation choices and licensing details to assist you get going with DeepSeek-R1 in your applications.
 3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be triggered to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
 5. For Variety of circumstances, enter a variety of instances (in between 1-100).
 6. For example type, pick your instance type. For optimal efficiency with DeepSeek-R1, a [GPU-based circumstances](http://huaang6688.gnway.cc3000) type like ml.p5e.48 xlarge is recommended.
 Optionally, you can configure sophisticated security and  [raovatonline.org](https://raovatonline.org/author/namchism044/) facilities settings, including virtual [private](https://library.kemu.ac.ke) cloud (VPC) networking, service role approvals, and file encryption settings. For the majority of [utilize](http://39.100.93.1872585) cases, the default settings will work well. However, for production implementations, you might wish to review these settings to line up with your organization's security and compliance requirements.
 7. Choose Deploy to start using the model.<br>
 <br>When the deployment is complete, you can test DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
 8. Choose Open in playground to access an interactive interface where you can try out various triggers and adjust model criteria like temperature and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimal outcomes. For instance, material for inference.<br>
 <br>This is an excellent way to explore the design's reasoning and text generation abilities before incorporating it into your applications. The play area provides immediate feedback, helping you understand how the model reacts to different inputs and letting you tweak your prompts for optimum outcomes.<br>
 <br>You can quickly evaluate the model in the play area through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
 <br>Run inference using guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to carry out inference using a released DeepSeek-R1 model 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 produce the guardrail, see the GitHub repo. After you have produced the guardrail, use the following code to implement guardrails. The script [initializes](http://133.242.131.2263003) the bedrock_[runtime](https://git.novisync.com) client, configures inference criteria, and sends a demand 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 solutions that you can release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your data, and release them into production utilizing either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through [SageMaker JumpStart](http://gitlab.xma1.de) offers 2 hassle-free techniques:  [fishtanklive.wiki](https://fishtanklive.wiki/User:DouglasWhitney) using the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker [Python SDK](http://47.76.210.1863000). Let's explore both methods to help you select the technique that finest fits your requirements.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following steps to deploy DeepSeek-R1 utilizing SageMaker JumpStart:<br>
 <br>1. On the SageMaker console, pick Studio in the navigation pane.
 2. First-time users will be triggered to create a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The model internet browser shows available designs, with details like the provider name and model abilities.<br>
 <br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card.
 Each model card shows [essential](http://www.grainfather.de) details, including:<br>
 <br>- Model name
 - Provider name
 - Task classification (for example, Text Generation).
 Bedrock Ready badge (if appropriate), showing that this model can be signed up with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to [conjure](https://social.stssconstruction.com) up the design<br>
 <br>5. Choose the design card to see the design details page.<br>
 <br>The design details page includes the following details:<br>
 <br>- The model name and supplier details.
 Deploy button to deploy the design.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab includes essential details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical specs.
 - Usage guidelines<br>
 <br>Before you deploy the design, it's advised to examine the design details and license terms to validate compatibility with your usage case.<br>
 <br>6. Choose Deploy to continue with deployment.<br>
 <br>7. For Endpoint name, use the immediately produced name or produce a custom-made one.
 8. For Instance type ¸ select an instance type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, get in the number of instances (default: 1).
 Selecting suitable [circumstances](https://englishlearning.ketnooi.com) types and counts is important for expense and performance optimization. Monitor your implementation to change these settings as needed.Under Inference type, Real-time inference is selected by default. This is enhanced for sustained traffic and low latency.
 10. Review all setups for accuracy. For this design, we strongly advise adhering to SageMaker JumpStart default settings and making certain that network isolation remains in place.
 11. Choose Deploy to deploy the model.<br>
 <br>The implementation procedure can take numerous minutes to finish.<br>
 <br>When implementation is complete, your endpoint status will alter to InService. At this point, the model is [prepared](https://www.genbecle.com) to accept inference demands through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will show relevant metrics and status details. When the implementation is complete, you can invoke the model using a SageMaker runtime client and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the essential AWS permissions and environment setup. The following is a detailed code example that demonstrates how to release and use DeepSeek-R1 for reasoning programmatically. The code for releasing the model is supplied in the Github here. You can clone the note pad 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 produce a guardrail utilizing the Amazon Bedrock console or the API, and [execute](http://118.190.175.1083000) it as displayed in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent undesirable charges, complete the actions in this section to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you deployed the design 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 deployments section, find the endpoint you desire to delete.
 3. Select the endpoint, and on the Actions menu, select Delete.
 4. Verify the endpoint details to make certain you're deleting the right deployment: 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 costs if you leave it running. Use the following code to delete 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 explored how you can access and release the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker 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](https://deadlocked.wiki) business build ingenious solutions using AWS services and accelerated compute. Currently, he is concentrated on establishing strategies for  [larsaluarna.se](http://www.larsaluarna.se/index.php/User:Rosalind2029) fine-tuning and optimizing the reasoning performance of big language models. In his downtime, Vivek enjoys treking, enjoying movies, and attempting different foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://source.brutex.net) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](http://gitlab.xma1.de) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is a Professional Solutions Architect working on generative [AI](https://techtalent-source.com) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://asromafansclub.com) center. She is passionate about developing options that help clients accelerate their [AI](https://www.drawlfest.com) journey and unlock organization worth.<br>