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

Essie Traeger 2025-04-03 08:48:16 +08:00
commit 6f0e554862
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are thrilled to reveal that DeepSeek R1 distilled Llama and Qwen designs are available through [Amazon Bedrock](https://www.characterlist.com) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now [release DeepSeek](https://projobs.dk) [AI](https://hyg.w-websoft.co.kr)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled versions ranging from 1.5 to 70 billion parameters to build, experiment, and responsibly scale your generative [AI](https://www.opad.biz) concepts 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 actions to release the distilled variations of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) developed by DeepSeek [AI](https://sparcle.cn) that uses support finding out to [enhance reasoning](https://bence.net) capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key distinguishing function is its support learning (RL) step, which was utilized to improve the beyond the basic pre-training and fine-tuning procedure. By integrating RL, DeepSeek-R1 can adjust better to user feedback and objectives, ultimately enhancing both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, implying it's equipped to break down intricate questions and reason through them in a detailed way. This guided thinking [process](https://repo.myapps.id) allows the model to produce more precise, transparent, and detailed answers. This design combines RL-based fine-tuning with CoT capabilities, aiming to generate structured reactions while concentrating on [interpretability](https://git.snaile.de) and user interaction. With its wide-ranging abilities DeepSeek-R1 has captured the industry's attention as a versatile text-generation model that can be [integrated](http://39.105.129.2293000) into numerous workflows such as agents, sensible thinking and data analysis jobs.<br>
<br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture allows activation of 37 billion criteria, making it possible for effective inference by routing inquiries to the most relevant specialist "clusters." This [technique enables](http://pinetree.sg) the design to focus on different issue domains while maintaining general efficiency. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge circumstances to deploy the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the thinking abilities of the main R1 model to more effective architectures based on popular open [designs](https://precise.co.za) like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller sized, more effective designs to simulate the behavior and reasoning patterns of the bigger DeepSeek-R1 model, utilizing it as an instructor model.<br>
<br>You can deploy DeepSeek-R1 model either through [SageMaker JumpStart](https://slovenskymedved.sk) or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we advise deploying this design with guardrails in location. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous content, and assess designs against key security requirements. At the time of writing this blog, [genbecle.com](https://www.genbecle.com/index.php?title=Utilisateur:ZellaSchutt0) for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, [pipewiki.org](https://pipewiki.org/wiki/index.php/User:JonnaCanipe) Bedrock Guardrails supports only the ApplyGuardrail API. You can develop several guardrails tailored to various usage cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing security controls across your generative [AI](http://121.40.194.123:3000) [applications](https://www.mk-yun.cn).<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 model, you need access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and confirm you're utilizing ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are releasing. To request a limitation boost, produce a limit increase request and connect to your account group.<br>
<br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) approvals to utilize Amazon Bedrock Guardrails. For directions, see Establish consents to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails enables you to present safeguards, prevent hazardous material, and assess models against crucial security criteria. You can execute precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to assess user inputs and model actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a [guardrail utilizing](http://git.gonstack.com) the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo.<br>
<br>The basic flow involves the following actions: First, [wiki.asexuality.org](https://wiki.asexuality.org/w/index.php?title=User_talk:AleishaWorkman7) the system gets an input for the model. This input is then processed through the ApplyGuardrail API. If the input passes the [guardrail](https://zapinacz.pl) check, it's sent out to the model for reasoning. After getting the model's output, another guardrail check is applied. If the [output passes](http://101.36.160.14021044) this final check, it's returned as the result. However, if either the input or output is stepped in by the guardrail, a message is returned indicating the nature of the intervention and whether it took place at the input or output stage. 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](https://git.programming.dev) 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](https://baescout.com) console, select 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 design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and choose the DeepSeek-R1 design.<br>
<br>The model detail page supplies essential details about the model's abilities, pricing structure, and application standards. You can discover detailed usage directions, consisting of [sample API](https://izibiz.pl) calls and code bits for integration. The model supports different text generation jobs, including content production, code generation, and question answering, utilizing its support discovering optimization and CoT reasoning capabilities.
The page also consists of deployment options and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, select Deploy.<br>
<br>You will be prompted to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, go into an [endpoint](https://www.securityprofinder.com) name (in between 1-50 alphanumeric characters).
5. For Variety of circumstances, go into a number of instances (in between 1-100).
6. For example type, pick your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is [suggested](https://git.ffho.net).
Optionally, you can set up sophisticated security and facilities settings, consisting of virtual personal cloud (VPC) networking, service function permissions, and file encryption settings. For the majority of use cases, the default settings will work well. However, for production deployments, you might desire to examine these settings to line up with your organization's security and compliance requirements.
7. Choose Deploy to begin utilizing the design.<br>
<br>When the release is total, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
8. Choose Open in playground to access an interactive interface where you can try out different triggers and adjust design parameters like temperature level and maximum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum outcomes. For instance, content for reasoning.<br>
<br>This is an outstanding method to check out the model's reasoning and text generation capabilities before integrating it into your applications. The playground provides immediate feedback, assisting you understand how the model reacts to various inputs and [letting](https://www.lotusprotechnologies.com) you fine-tune your triggers for ideal outcomes.<br>
<br>You can quickly check the design in the play area through the UI. However, to conjure up the released design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run [inference](https://supremecarelink.com) using guardrails with the [released](https://www.ggram.run) DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to carry out inference utilizing a [released](http://geoje-badapension.com) DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock [console](https://video.emcd.ro) or the API. For the example code to develop the guardrail, see the GitHub repo. After you have produced the guardrail, [surgiteams.com](https://surgiteams.com/index.php/User:Benny26M6631456) use the following code to carry out guardrails. The script initializes the bedrock_runtime client, configures reasoning parameters, and sends out a request to create text 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, built-in algorithms, and prebuilt ML services that you can release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your information, and deploy them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart uses 2 convenient techniques: using the intuitive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both [techniques](https://git.schdbr.de) to help you choose the approach that finest matches your [requirements](http://114.111.0.1043000).<br>
<br>Deploy DeepSeek-R1 through [SageMaker JumpStart](https://web.zqsender.com) UI<br>
<br>Complete the following actions 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 create a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The [model web](https://jobs.web4y.online) browser displays available designs, with details like the supplier name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each design card reveals crucial details, including:<br>
<br>- Model name
- Provider name
- Task [category](http://133.242.131.2263003) (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](http://www.tomtomtextiles.com) APIs to conjure up the model<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 design name and [company details](https://starttrainingfirstaid.com.au).
Deploy button to release the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical specifications.
- Usage guidelines<br>
<br>Before you release the design, it's suggested to examine the model details and license terms to validate compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with release.<br>
<br>7. For Endpoint name, use the automatically created name or create a custom-made one.
8. For Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the variety of instances (default: 1).
Selecting suitable circumstances types and counts is vital for expense and efficiency optimization. Monitor your implementation to change these settings as needed.Under [Inference](https://git.poggerer.xyz) type, Real-time reasoning is picked by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for accuracy. For this design, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the design.<br>
<br>The implementation procedure can take numerous minutes to finish.<br>
<br>When deployment is complete, your endpoint status will alter to InService. At this point, the model is all set to accept reasoning requests through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the release is total, you can invoke the model utilizing a SageMaker runtime customer and [incorporate](https://islamichistory.tv) it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To get started with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker [Python SDK](http://kacm.co.kr) and make certain you have the essential AWS consents and environment setup. The following is a detailed code example that shows how to release and utilize DeepSeek-R1 for inference programmatically. The code for deploying the model 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 inference with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can also use 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>Clean up<br>
<br>To avoid undesirable charges, finish the actions in this area to clean 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 models in the navigation pane, choose Marketplace deployments.
2. In the Managed implementations area, find the endpoint you desire to erase.
3. Select the endpoint, and on the Actions menu, pick Delete.
4. Verify the endpoint details to make certain you're deleting the appropriate release: 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 erase the endpoint if you want to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we [checked](https://menfucks.com) 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 begun. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, Amazon SageMaker [JumpStart](https://git.mitsea.com) Foundation Models, Amazon Bedrock Marketplace, and Getting started with Amazon [SageMaker JumpStart](http://git.iloomo.com).<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative [AI](http://161.97.176.30) companies build innovative services utilizing AWS services and accelerated compute. Currently, he is concentrated on developing techniques for fine-tuning and optimizing the reasoning performance of large language designs. In his free time, Vivek delights in treking, viewing motion pictures, and trying different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://www.indianpharmajobs.in) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](https://knightcomputers.biz) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](https://theneverendingstory.net) 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](http://app.vellorepropertybazaar.in) hub. She is passionate about developing services that assist consumers accelerate their [AI](http://ep210.co.kr) journey and unlock service worth.<br>