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

2025-02-09 11:47:26 +08:00 · 2025-02-09 11:47:26 +08:00 · 4897e5f56d
commit 4897e5f56d
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are thrilled to reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](https://privamaxsecurity.co.ke)'s first-generation frontier model, DeepSeek-R1, in addition to the distilled versions varying from 1.5 to 70 billion parameters to develop, experiment, and responsibly scale your generative [AI](https://git.randomstar.io) ideas on AWS.<br>
 <br>In this post, we demonstrate how to get begun with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to release the [distilled versions](http://www.zeil.kr) of the designs also.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big [language design](https://jobs.ezelogs.com) (LLM) established by DeepSeek [AI](https://www.proathletediscuss.com) that utilizes support learning to boost reasoning capabilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential [distinguishing feature](https://property.listatto.ca) is its support knowing (RL) step, which was utilized to [improve](http://jerl.zone3000) the design's actions beyond the standard pre-training and tweak procedure. By including RL,  [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:TAHRena195267306) DeepSeek-R1 can adapt better to user feedback and goals, ultimately improving both relevance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, implying it's equipped to break down complex inquiries and reason through them in a detailed way. This assisted thinking procedure allows the model to produce more accurate, transparent, and detailed responses. This design [integrates RL-based](https://gitlab-zdmp.platform.zdmp.eu) fine-tuning with CoT capabilities, aiming to create structured actions while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has caught the market's attention as a versatile text-generation model that can be integrated into numerous workflows such as agents, sensible [reasoning](http://202.90.141.173000) and information analysis tasks.<br>
 <br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, making it possible for effective reasoning by routing questions to the most appropriate specialist "clusters." This approach enables the design to specialize in various issue domains while maintaining general [efficiency](https://gamberonmusic.com). 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 offering 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the [thinking capabilities](https://0miz2638.cdn.hp.avalon.pw9443) of the main R1 design 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 of training smaller sized, more effective designs to imitate the habits and reasoning patterns of the larger DeepSeek-R1 design, utilizing it as an instructor design.<br>
 <br>You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest releasing this design with guardrails in location. In this blog site, we will utilize Amazon [Bedrock Guardrails](https://techtalent-source.com) to introduce safeguards, prevent damaging content, and examine designs against essential safety criteria. At the time of composing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create multiple guardrails tailored to different use cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative [AI](https://git.dev-store.ru) applications.<br>
 <br>Prerequisites<br>
 <br>To [release](https://gitlab.ucc.asn.au) 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 SageMaker, and validate you're [utilizing](https://git.foxarmy.org) 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 request a limitation increase, develop a limitation increase 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 (IAM) authorizations to utilize Amazon Bedrock Guardrails. For guidelines, see Set up consents to utilize guardrails for material filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails enables you to introduce safeguards, avoid harmful content, and assess designs against essential security criteria. You can execute precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to [apply guardrails](https://it-storm.ru3000) to assess user inputs and [design reactions](http://www.zeil.kr) [deployed](https://topdubaijobs.ae) on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail utilizing the Amazon Bedrock console or the API. For the example code to [develop](https://www.bridgewaystaffing.com) the guardrail, see the GitHub repo.<br>
 <br>The basic [flow involves](https://93.177.65.216) 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 inference. After receiving the design's output, another guardrail check is applied. If the output passes this last 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 happened at the input or output stage. 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 offers 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 catalog under Foundation models in the navigation pane.
 At the time of writing this post, you can use the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a provider and choose the DeepSeek-R1 model.<br>
 <br>The design detail page offers important details about the model's abilities, prices structure, and execution standards. You can discover detailed usage instructions, consisting of sample API calls and code bits for integration. The model supports different text generation jobs, including content production, code generation, and concern answering, utilizing its support discovering optimization and CoT thinking abilities.
 The page also includes deployment choices and [licensing details](https://bestwork.id) to assist you begin with DeepSeek-R1 in your applications.
 3. To begin using DeepSeek-R1, choose Deploy.<br>
 <br>You will be prompted to set up the [implementation details](http://118.190.145.2173000) 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 Variety of circumstances, enter a variety of instances (between 1-100).
 6. For Instance type, select your circumstances type. For optimal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
 Optionally,  [wiki.whenparked.com](https://wiki.whenparked.com/User:AdriannaFawcett) you can configure advanced security and facilities settings, including virtual private cloud (VPC) networking, service role consents, and file encryption settings. For most use cases, the default settings will work well. However, for production implementations,  [surgiteams.com](https://surgiteams.com/index.php/User:Darnell83J) you may desire to examine these settings to align with your organization's security and compliance requirements.
 7. Choose Deploy to start using the model.<br>
 <br>When the implementation is complete, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
 8. Choose Open in playground to access an interactive user interface where you can try out various triggers and adjust model specifications like temperature and optimum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimal results. For instance, content for reasoning.<br>
 <br>This is an outstanding way to explore the model's thinking and text generation capabilities before integrating it into your applications. The playground provides instant feedback, helping you understand how the model reacts to numerous inputs and letting you fine-tune your triggers for optimum outcomes.<br>
 <br>You can rapidly check the design in the play area through the UI. However, to invoke the deployed model programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
 <br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to perform inference utilizing a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and [ApplyGuardrail API](https://www.lightchen.info). 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. After you have produced the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime client, configures inference specifications, and sends a request to generate text based on a user prompt.<br>
 <br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
 <br>SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and prebuilt ML [services](https://repo.maum.in) that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your information, and release them into production using either the UI or SDK.<br>
 <br>[Deploying](http://gitlab.hupp.co.kr) DeepSeek-R1 model through SageMaker JumpStart offers 2 hassle-free techniques: utilizing the instinctive SageMaker JumpStart UI or executing programmatically through the [SageMaker Python](https://kennetjobs.com) SDK. Let's explore both techniques to help you choose the technique that best 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, pick Studio in the navigation pane.
 2. First-time users will be prompted to produce a domain.
 3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
 <br>The model browser displays available models, with details like the service provider name and design abilities.<br>
 <br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card.
 Each design card reveals crucial details, including:<br>
 <br>- Model name
 - Provider name
 - Task classification (for instance, Text Generation).
 [Bedrock Ready](https://charin-issuedb.elaad.io) badge (if suitable), showing that this model can be signed up with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the model<br>
 <br>5. Choose the design card to see the model details page.<br>
 <br>The design details page consists of the following details:<br>
 <br>- The model name and service provider details.
 Deploy button to deploy the model.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab includes important details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical specs.
 - Usage standards<br>
 <br>Before you deploy the model, it's suggested to evaluate the design details and license terms to [validate compatibility](https://gitlab.tenkai.pl) with your usage case.<br>
 <br>6. Choose Deploy to continue with implementation.<br>
 <br>7. For Endpoint name, utilize the [instantly](http://60.205.104.1793000) created name or create a custom-made one.
 8. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, get in the number of circumstances (default: 1).
 Selecting suitable [instance](http://git.bplt.ru) types and counts is crucial for cost 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 highly recommend 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 implementation process can take numerous minutes to complete.<br>
 <br>When deployment is total, your endpoint status will alter to [InService](https://lafffrica.com). At this point, the design is ready to accept inference demands through the endpoint. You can keep an eye on the release progress on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the implementation is complete, you can conjure up the design using a SageMaker runtime customer and incorporate it with your [applications](http://okosg.co.kr).<br>
 <br>Deploy DeepSeek-R1 using the [SageMaker Python](https://supremecarelink.com) SDK<br>
 <br>To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the necessary [AWS approvals](https://demo.titikkata.id) and environment setup. The following is a detailed code example that shows how to deploy and utilize DeepSeek-R1 for reasoning programmatically. The code for deploying 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 requests against the predictor:<br>
 <br>[Implement guardrails](https://git.olivierboeren.nl) 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 utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent unwanted charges, complete the steps in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock [Marketplace](https://193.31.26.118) implementation<br>
 <br>If you released the model utilizing Amazon Bedrock Marketplace, total the following steps:<br>
 <br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace releases.
 2. In the Managed deployments section, find the [endpoint](https://git.ashcloudsolution.com) you desire to erase.
 3. Select the endpoint, and on the Actions menu, choose Delete.
 4. Verify the endpoint details to make certain you're erasing the appropriate implementation: 1. Endpoint name.
 2. Model name.
 3. Endpoint status<br>
 <br>Delete the SageMaker JumpStart predictor<br>
 <br>The SageMaker JumpStart model you deployed will sustain expenses 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 design utilizing 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 begun 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](https://juryi.sn) business build innovative options using AWS services and  [raovatonline.org](https://raovatonline.org/author/arletha3316/) accelerated calculate. Currently, he is concentrated on developing methods for fine-tuning and optimizing the reasoning efficiency of big language models. In his spare time, Vivek delights in hiking, viewing motion pictures, and attempting different cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://careers.tu-varna.bg)  Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](https://git.chirag.cc) 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://employmentabroad.com) with the [Third-Party Model](https://jobistan.af) Science team at AWS.<br>
 <br>Banu Nagasundaram leads product, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://oakrecruitment.uk) center. She is passionate about building options that assist customers accelerate their [AI](https://skillnaukri.com) journey and unlock business worth.<br>