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

Bertie Yamamoto 2025-02-17 11:51:31 +07:00
parent 965d977d24
commit 4aa6f1cdc1

@ -0,0 +1,93 @@
<br>Today, we are excited to announce that [DeepSeek](https://oros-git.regione.puglia.it) R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://amore.is)['s first-generation](http://xn--vk1b975azoatf94e.com) frontier design, DeepSeek-R1, in addition to the distilled variations ranging from 1.5 to 70 billion specifications to develop, experiment, and properly scale your generative [AI](http://47.100.72.85:3000) 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 similar steps to deploy the distilled variations of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) established by DeepSeek [AI](http://git.vimer.top:3000) that utilizes support discovering to improve thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential identifying feature is its support learning (RL) step, which was utilized to refine the design's actions beyond the standard pre-training and fine-tuning procedure. By including RL, DeepSeek-R1 can adjust more effectively to user feedback and [systemcheck-wiki.de](https://systemcheck-wiki.de/index.php?title=Benutzer:SusieChipman) objectives, eventually boosting both relevance and [clearness](http://www.asiapp.co.kr). In addition, DeepSeek-R1 uses a chain-of-thought (CoT) approach, suggesting it's geared up to break down complicated questions and reason through them in a detailed way. This assisted reasoning procedure allows the design to produce more accurate, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT capabilities, aiming to generate structured reactions while concentrating on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has actually caught the industry's attention as a versatile text-generation model that can be integrated into different workflows such as representatives, rational reasoning and data interpretation jobs.<br>
<br>DeepSeek-R1 [utilizes](https://git.todayisyou.co.kr) a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture of 37 billion specifications, enabling effective reasoning by routing questions to the most relevant expert "clusters." This method allows the design to concentrate on different issue domains while maintaining total effectiveness. DeepSeek-R1 requires at least 800 GB of [HBM memory](http://git.fast-fun.cn92) in FP8 format for inference. In this post, we will utilize an ml.p5e.48 xlarge instance to release the model. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 design 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 process of training smaller, more efficient designs to simulate the habits and thinking patterns of the larger DeepSeek-R1 design, utilizing it as an instructor model.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend deploying this design with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and examine designs against essential security requirements. At the time of composing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create several guardrails tailored to various usage cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing safety controls throughout your generative [AI](https://tjoobloom.com) 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 Service Quotas console and under AWS Services, pick Amazon SageMaker, and verify you're using ml.p5e.48 xlarge for [endpoint usage](https://poslovi.dispeceri.rs). Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are [releasing](https://www.jungmile.com). To ask for a limit increase, produce a limit 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 appropriate AWS Identity and Gain Access To Management (IAM) consents to use Amazon Bedrock Guardrails. For directions, see Set up approvals to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails enables you to [introduce](https://analyticsjobs.in) safeguards, avoid hazardous material, and evaluate models against key safety requirements. You can implement precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to assess user inputs and [model actions](https://alumni.myra.ac.in) [released](https://sundaycareers.com) 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 create the guardrail, see the GitHub repo.<br>
<br>The basic circulation involves the following steps: First, [garagesale.es](https://www.garagesale.es/author/seanedouard/) 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 to the model for inference. After getting the model's output, another guardrail check is used. 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 stage. The examples showcased in the following sections show inference 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 designs (FMs) through [Amazon Bedrock](http://demo.ynrd.com8899). 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 composing this post, you can use the InvokeModel API to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and pick the DeepSeek-R1 model.<br>
<br>The model detail page supplies important details about the design's abilities, prices structure, and application guidelines. You can discover detailed use directions, consisting of sample API calls and code bits for integration. The model supports numerous text generation tasks, including content development, [forum.pinoo.com.tr](http://forum.pinoo.com.tr/profile.php?id=1321201) code generation, and question answering, using its support discovering [optimization](https://git.satori.love) and CoT reasoning capabilities.
The page likewise consists of release alternatives and licensing details to help you get started with DeepSeek-R1 in your applications.
3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
<br>You will be [triggered](http://git.risi.fun) to configure the implementation details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, get in an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of instances, enter a number of instances (in between 1-100).
6. For Instance type, choose your instance type. For optimum performance with DeepSeek-R1, a [GPU-based circumstances](http://111.231.76.912095) type like ml.p5e.48 xlarge is advised.
Optionally, you can configure sophisticated security and infrastructure settings, including virtual private cloud (VPC) networking, service function consents, and file encryption settings. For many utilize cases, the default settings will work well. However, for production implementations, you may desire to examine these settings to align with your organization's security and compliance requirements.
7. Choose Deploy to start utilizing the model.<br>
<br>When the release is total, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
8. Choose Open in play area to access an interactive user interface where you can experiment with various prompts and adjust design specifications like temperature and maximum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimum outcomes. For example, material for reasoning.<br>
<br>This is an [outstanding method](https://vidy.africa) to explore the model's reasoning and text generation abilities before incorporating it into your applications. The play ground supplies instant feedback, helping you understand how the design reacts to numerous inputs and letting you fine-tune your prompts for optimum results.<br>
<br>You can quickly test the model in the playground through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to carry out reasoning using a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and [ApplyGuardrail API](http://8.134.253.2218088). You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have actually created the guardrail, use the following code to [implement guardrails](http://123.249.20.259080). The script initializes the bedrock_runtime customer, configures inference parameters, and sends a demand to generate 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, built-in algorithms, and prebuilt ML options that you can deploy with just a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your data, and release them into production utilizing either the UI or [wiki.snooze-hotelsoftware.de](https://wiki.snooze-hotelsoftware.de/index.php?title=Benutzer:Princess3594) SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 practical techniques: utilizing the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both techniques to help you choose the technique that best [matches](https://spaceballs-nrw.de) 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, pick Studio in the navigation pane.
2. [First-time](https://alumni.myra.ac.in) users will be prompted to produce a domain.
3. On the SageMaker Studio console, choose [JumpStart](http://47.109.153.573000) in the navigation pane.<br>
<br>The model internet browser shows available designs, with details like the service provider name and design [capabilities](http://www.maxellprojector.co.kr).<br>
<br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 model card.
Each model card shows key details, including:<br>
<br>- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if relevant), showing that this model can be [registered](http://119.29.169.1578081) with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the model card to view the model details page.<br>
<br>The design details page includes the following details:<br>
<br>- The model name and [supplier details](https://4stour.com).
Deploy button to deploy the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of important details, such as:<br>
<br>- Model description.
- License details.
- Technical specs.
- Usage guidelines<br>
<br>Before you [release](http://120.77.221.1993000) the design, it's suggested to evaluate the design details and license terms to validate compatibility with your use case.<br>
<br>6. Choose Deploy to continue with implementation.<br>
<br>7. For Endpoint name, utilize the automatically generated name or create a custom one.
8. For example [type ¸](https://earthdailyagro.com) pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the variety of instances (default: 1).
Selecting suitable instance types and counts is crucial for cost and performance optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for accuracy. For this design, we strongly recommend adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. [Choose Deploy](https://git.iws.uni-stuttgart.de) to deploy the design.<br>
<br>The implementation process can take a number of minutes to complete.<br>
<br>When release is complete, your endpoint status will change to InService. At this point, the model is all set to accept reasoning demands through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the release is complete, you can conjure up the model using a [SageMaker runtime](https://www.xtrareal.tv) client and integrate it with your [applications](http://oj.algorithmnote.cn3000).<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS consents and [environment](http://gitlab.suntrayoa.com) 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 provided 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 likewise use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
<br>Clean 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 model using Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace releases.
2. In the Managed releases area, find the endpoint you desire to delete.
3. Select the endpoint, and on the [Actions](https://fishtanklive.wiki) menu, [select Delete](http://www.asiapp.co.kr).
4. Verify the endpoint details to make certain you're [erasing](https://www.wikiwrimo.org) the proper implementation: 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 delete the [endpoint](http://1.94.127.2103000) 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 model 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 designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting begun with Amazon SageMaker [JumpStart](https://shiatube.org).<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He [assists emerging](https://codes.tools.asitavsen.com) generative [AI](https://superblock.kr) business develop ingenious services [utilizing](https://git.todayisyou.co.kr) AWS services and accelerated compute. Currently, he is concentrated on [establishing techniques](http://82.146.58.193) for fine-tuning and optimizing the reasoning efficiency of big language models. In his downtime, Vivek takes pleasure in treking, enjoying movies, and trying various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://www.mpowerplacement.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His [location](http://jolgoo.cn3000) of focus is AWS [AI](http://zerovalueentertainment.com:3000) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is a [Specialist](http://fridayad.in) Solutions Architect dealing with generative [AI](https://calamitylane.com) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://git.satori.love) center. She is enthusiastic about building services that help customers accelerate their [AI](http://47.110.52.132:3000) journey and unlock company worth.<br>