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

2025-04-10 11:08:02 +08:00 · 2025-04-10 11:08:02 +08:00 · 3cad775d5c
commit 3cad775d5c
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are excited to reveal that DeepSeek R1 distilled Llama and Qwen models are available through [Amazon Bedrock](https://www.imdipet-project.eu) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://git.cooqie.ch)'s first-generation frontier design, DeepSeek-R1, in addition to the [distilled versions](https://gitea.dusays.com) ranging from 1.5 to 70 billion criteria to develop, experiment, and responsibly scale your generative [AI](https://www.kritterklub.com) ideas on AWS.<br>
 <br>In this post, we show how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to release the distilled variations of the models also.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](http://135.181.29.174:3001) that uses reinforcement discovering to improve reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A [key identifying](https://49.12.72.229) [feature](https://repo.beithing.com) is its support learning (RL) step, which was used to refine the design's reactions beyond the standard pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adjust more efficiently to user feedback and objectives, eventually improving both relevance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, meaning it's equipped to break down complicated inquiries and factor through them in a detailed way. This assisted reasoning process allows the model to produce more precise, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT capabilities, aiming to create structured actions while focusing 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 numerous workflows such as agents, rational thinking and [data interpretation](http://ptube.site) tasks.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion [specifications](https://gitlab.reemii.cn) in size. The MoE architecture allows activation of 37 billion parameters, [enabling effective](https://39.98.119.14) inference by routing inquiries to the most [relevant professional](https://git.vincents.cn) "clusters." This method enables the model to focus on different problem domains while maintaining general efficiency. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for inference. In this post, we will utilize an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 model to more efficient 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, more efficient models to simulate the behavior and thinking patterns of the larger DeepSeek-R1 model, utilizing it as a teacher model.<br>
 <br>You can [release](https://ayjmultiservices.com) DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend deploying this model with [guardrails](https://www.sociopost.co.uk) in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent damaging material, and assess models against crucial safety criteria. At the time of [composing](https://social.mirrororg.com) this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce multiple guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls throughout your generative [AI](https://www.rhcapital.cl) applications.<br>
 <br>Prerequisites<br>
 <br>To release the DeepSeek-R1 model, you need access to an ml.p5e circumstances. To examine 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 circumstances in the AWS Region you are releasing. To ask for a limit boost, develop a limitation boost request and connect to your account group.<br>
 <br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) permissions to use Amazon Bedrock [Guardrails](http://82.156.24.19310098). For directions, see Set up consents to use guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails allows you to present safeguards,  [larsaluarna.se](http://www.larsaluarna.se/index.php/User:LamarMacandie) avoid damaging material, and assess models against crucial safety criteria. You can implement safety measures for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to use guardrails to evaluate user inputs and model actions [deployed](http://thinking.zicp.io3000) 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 produce the guardrail, see the GitHub repo.<br>
 <br>The basic flow includes the following steps: First, the system gets 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 model's output, another guardrail check is applied. If the output passes this final check, it's returned as the final 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 occurred at the input or output phase. The examples showcased in the following areas demonstrate inference 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 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, pick Model catalog 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.
 2. Filter for DeepSeek as a [service provider](https://rootsofblackessence.com) and choose the DeepSeek-R1 design.<br>
 <br>The design detail page provides essential details about the model's abilities, rates structure, and implementation guidelines. You can discover detailed usage instructions, consisting of sample API calls and code bits for integration. The design supports numerous text generation jobs, [including](http://139.224.213.43000) content production, code generation, and question answering, using its reinforcement finding out [optimization](http://163.66.95.1883001) and CoT thinking abilities.
 The page also includes implementation alternatives 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 prompted to configure the implementation details for DeepSeek-R1. The design ID will be pre-populated.
 4. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
 5. For Variety of instances, go into a number of circumstances (in between 1-100).
 6. For Instance type, pick your circumstances type. For optimum efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
 Optionally, you can configure sophisticated security and facilities settings, including virtual personal cloud (VPC) networking, service function approvals, and encryption settings. For a lot of use cases, the default settings will work well. However, for production deployments, you might desire to evaluate these settings to align with your [organization's security](https://members.mcafeeinstitute.com) and compliance requirements.
 7. Choose Deploy to start using the model.<br>
 <br>When the release is complete, you can check 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 triggers and adjust model criteria like temperature level and maximum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for ideal results. For instance, material for reasoning.<br>
 <br>This is an outstanding method to check out the model's thinking and text generation capabilities before incorporating it into your [applications](https://olymponet.com). The play area provides immediate feedback, helping you understand how the design reacts to numerous inputs and letting you tweak your triggers for optimal outcomes.<br>
 <br>You can rapidly test the design in the playground through the UI. However, to conjure up the deployed model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
 <br>Run inference utilizing [guardrails](https://tradingram.in) with the released DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to carry out reasoning utilizing a deployed DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and [ApplyGuardrail API](https://daeshintravel.com). You can develop a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have developed the guardrail, utilize the following code to [implement guardrails](https://deadlocked.wiki). The script initializes the bedrock_runtime customer, sets up inference criteria, and sends a request to generate text based upon a user timely.<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 [options](https://www.seekbetter.careers) that you can deploy with just a couple of clicks. With SageMaker JumpStart,  [garagesale.es](https://www.garagesale.es/author/sheltonhoot/) you can tailor pre-trained designs to your use case, with your data, and deploy them into production using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 practical methods: utilizing the [intuitive SageMaker](http://180.76.133.25316300) JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's explore both techniques to assist you pick the method that finest fits your requirements.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following actions to release DeepSeek-R1 using SageMaker JumpStart:<br>
 <br>1. On the SageMaker console, [select Studio](https://athleticbilbaofansclub.com) in the navigation pane.
 2. First-time users will be prompted to develop a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The model internet browser shows available models, with details like the company name and model capabilities.<br>
 <br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 [model card](http://funnydollar.ru).
 Each design card reveals essential details, consisting of:<br>
 <br>- Model name
 [- Provider](http://180.76.133.25316300) name
 - Task category (for example, Text Generation).
 Bedrock Ready badge (if relevant), suggesting that this design can be registered with Amazon Bedrock, [permitting](http://plethe.com) you to utilize Amazon [Bedrock](http://experienciacortazar.com.ar) APIs to invoke the design<br>
 <br>5. Choose the design card to see the model details page.<br>
 <br>The design details page includes the following details:<br>
 <br>- The design name and service provider details.
 Deploy button to release 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 requirements.
 - Usage standards<br>
 <br>Before you deploy the model, it's recommended to review the design details and license terms to verify compatibility with your usage case.<br>
 <br>6. Choose Deploy to continue with deployment.<br>
 <br>7. For Endpoint name, use the immediately generated name or produce a custom-made one.
 8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, enter the variety of circumstances (default: 1).
 Selecting proper [circumstances types](http://gagetaylor.com) and counts is vital for expense and efficiency optimization. Monitor your release to change these settings as needed.Under Inference type, Real-time inference is chosen by default. This is enhanced for sustained traffic and low latency.
 10. Review all configurations for precision. For this model, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network isolation remains in place.
 11. Choose Deploy to release the design.<br>
 <br>The release process can take numerous minutes to complete.<br>
 <br>When release is complete,  [surgiteams.com](https://surgiteams.com/index.php/User:JulietBoswell) your [endpoint status](https://pattondemos.com) will alter to InService. At this point, the model is all set to accept reasoning demands through the endpoint. You can monitor the deployment development on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the deployment is total, you can invoke the design utilizing a SageMaker runtime customer and integrate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using 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 required AWS authorizations and environment setup. The following is a detailed code example that shows how to deploy and use DeepSeek-R1 for inference programmatically. The code for deploying the design is supplied 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 reasoning 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 create a guardrail using the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
 <br>Clean up<br>
 <br>To prevent unwanted charges, complete the steps in this section to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you released the model 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 releases.
 2. In the Managed releases section, find the  you desire to delete.
 3. Select the endpoint, and on the Actions menu, choose Delete.
 4. Verify the endpoint details to make certain you're deleting 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 released will sustain costs if you leave it running. Use the following code to delete the endpoint if you desire 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  [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:SheliaTel71539) release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in [SageMaker Studio](https://www.pkjobs.store) or Amazon Bedrock Marketplace now to get begun. For more details, refer to Use Amazon Bedrock [tooling](https://servergit.itb.edu.ec) with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock 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 helps emerging generative [AI](https://code.balsoft.ru) business develop ingenious solutions utilizing AWS services and accelerated calculate. Currently, he is focused on establishing techniques for fine-tuning and enhancing the inference performance of large language models. In his downtime, Vivek takes pleasure in hiking, enjoying motion pictures, and attempting various cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://redebuck.com.br) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](http://git2.guwu121.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://harimuniform.co.kr) 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](http://47.105.180.150:30002) hub. She is [passionate](https://git.bourseeye.com) about constructing services that assist consumers accelerate their [AI](http://git.estoneinfo.com) journey and unlock organization worth.<br>