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

Sheila Mccune 2025-04-02 23:45:05 +08:00
commit 982d918908
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are thrilled to announce that DeepSeek R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](https://investsolutions.org.uk)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled versions [ranging](https://git.mhurliman.net) from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative [AI](http://113.105.183.190:3000) concepts on AWS.<br>
<br>In this post, we demonstrate how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable actions to deploy the distilled variations of the models also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language design (LLM) developed by DeepSeek [AI](https://dolphinplacements.com) that uses support finding out to boost reasoning abilities through a multi-stage training procedure from a DeepSeek-V3[-Base structure](http://103.205.66.473000). A key identifying function is its reinforcement knowing (RL) action, which was used to improve the model's reactions beyond the basic pre-training and tweak procedure. By incorporating RL, DeepSeek-R1 can adapt more effectively to user feedback and goals, ultimately improving both significance and [clearness](http://47.103.108.263000). In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, implying it's equipped to break down intricate questions and reason through them in a detailed manner. This assisted reasoning process permits the model to produce more accurate, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured reactions while concentrating on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has recorded the market's attention as a flexible text-generation design that can be integrated into numerous workflows such as agents, logical reasoning and information interpretation jobs.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture allows activation of 37 billion parameters, enabling efficient inference by routing inquiries to the most pertinent specialist "clusters." This technique enables the model to specialize in various issue domains while maintaining overall performance. 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 instance to deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 model to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller, more effective designs to imitate the behavior and reasoning patterns of the larger DeepSeek-R1 design, utilizing it as an instructor design.<br>
<br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we [recommend releasing](https://git.soy.dog) this design with guardrails in location. In this blog, we will use Amazon Bedrock Guardrails to present safeguards, avoid damaging content, and evaluate models against key security requirements. At the time of writing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can develop several guardrails tailored to various use cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls across your generative [AI](https://www.angevinepromotions.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, 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, pick Amazon SageMaker, and verify you're utilizing ml.p5e.48 xlarge for [endpoint](https://sadegitweb.pegasus.com.mx) use. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are releasing. To request a limitation increase, create a limitation increase [request](http://www.kotlinx.com3000) and connect to your account team.<br>
<br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) [approvals](https://www.majalat2030.com) to use Amazon Bedrock Guardrails. For directions, see Set up approvals to use guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails enables you to introduce safeguards, avoid harmful material, and examine designs against crucial safety requirements. You can carry out precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to examine user inputs and model reactions deployed 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.<br>
<br>The basic flow includes the following actions: 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 model for reasoning. After getting the design's output, another guardrail check is used. If the output passes this last check, it's [returned](https://git.on58.com) 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 happened at the input or output stage. The examples showcased in the following sections show [inference](http://rootbranch.co.za7891) using 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 models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:<br>
<br>1. On the Amazon Bedrock console, pick Model brochure under Foundation models in the navigation pane.
At the time of writing this post, you can utilize the [InvokeModel API](https://tmiglobal.co.uk) 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 model.<br>
<br>The design detail page supplies necessary details about the model's abilities, rates structure, and application standards. You can discover detailed usage directions, consisting of sample API calls and code snippets for combination. The design supports various text generation jobs, consisting of content production, code generation, and question answering, using its support discovering optimization and CoT thinking capabilities.
The page likewise consists of release options and licensing details to help you get started with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select Deploy.<br>
<br>You will be triggered 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, enter a variety of instances (between 1-100).
6. For Instance type, choose your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up innovative security and facilities settings, including virtual private cloud (VPC) networking, service function authorizations, and file encryption settings. For many use cases, the default settings will work well. However, for production releases, you might wish to review these settings to line up with your organization's security and compliance requirements.
7. [Choose Deploy](http://www.fasteap.cn3000) to start utilizing the design.<br>
<br>When the implementation is total, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
8. Choose Open in play area to access an interactive interface where you can experiment with different triggers and change design specifications like temperature level and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For example, content for inference.<br>
<br>This is an exceptional method to explore the model's thinking and text generation capabilities before incorporating it into your applications. The play ground provides immediate feedback, assisting you understand how the design reacts to [numerous inputs](http://metis.lti.cs.cmu.edu8023) and letting you fine-tune your triggers for ideal results.<br>
<br>You can rapidly test the design in the play ground through the UI. However, to conjure up the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to carry out inference utilizing a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have actually [developed](http://vk-mix.ru) the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures reasoning criteria, and sends out a demand to [generate text](https://europlus.us) 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, [higgledy-piggledy.xyz](https://higgledy-piggledy.xyz/index.php/User:DortheaGeorgina) you can tailor pre-trained models to your use case, with your data, and deploy them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart uses two hassle-free methods: utilizing the intuitive SageMaker [JumpStart](http://dev.nextreal.cn) UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you select the technique that best matches 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](https://audioedu.kyaikkhami.com) console, select 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 design browser displays available designs, with details like the [service provider](http://47.104.234.8512080) name and model capabilities.<br>
<br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 [design card](http://lophas.com).
Each design card reveals crucial details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if appropriate), showing that this design can be registered with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to conjure up the model<br>
<br>5. Choose the design card to see the design details page.<br>
<br>The [model details](http://git.moneo.lv) page includes 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 consists of crucial details, such as:<br>
<br>- Model description.
- License details.
[- Technical](https://linkin.commoners.in) specs.
- Usage guidelines<br>
<br>Before you release the model, it's recommended to examine the design details and license terms to verify compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with release.<br>
<br>7. For Endpoint name, use the automatically produced name or develop a customized one.
8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of instances (default: 1).
Selecting appropriate circumstances types and counts is essential for expense and [efficiency optimization](https://www.gritalent.com). Monitor your release to adjust these settings as needed.Under [Inference](https://git.itbcode.com) type, Real-time inference is selected by default. This is optimized for sustained traffic and low latency.
10. Review all configurations for accuracy. For this design, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to release the design.<br>
<br>The deployment procedure can take numerous minutes to complete.<br>
<br>When implementation is complete, your endpoint status will change to InService. At this point, the design is prepared to accept inference demands through the [endpoint](https://bandbtextile.de). You can monitor the release progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is complete, you can conjure up the model utilizing 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 using 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 shows how to release and utilize DeepSeek-R1 for reasoning programmatically. The code for releasing the design 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](https://bantooplay.com) 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](http://touringtreffen.nl) or the API, and implement it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To avoid unwanted charges, complete the steps in this area to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you released the model utilizing Amazon Bedrock Marketplace, total the following steps:<br>
<br>1. On the [Amazon Bedrock](https://demanza.com) console, under Foundation designs in the [navigation](https://git.tedxiong.com) pane, pick Marketplace releases.
2. In the Managed releases section, find the [endpoint](http://www.litehome.top) you want to delete.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the right release: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart design you deployed 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](http://lophas.com) out how you can access and [release](https://testgitea.educoder.net) the DeepSeek-R1 model using 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 models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going with Amazon SageMaker JumpStart.<br>
<br>About the Authors<br>
<br> is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging [generative](http://8.137.89.263000) [AI](http://47.99.132.164:3000) business construct innovative options utilizing [AWS services](https://social.instinxtreme.com) and sped up compute. Currently, he is concentrated on establishing strategies for fine-tuning and enhancing the inference performance of large language models. In his leisure time, Vivek enjoys hiking, watching films, and attempting different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://www.fasteap.cn:3000) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His location of focus is AWS [AI](http://git.pancake2021.work) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is an Expert Solutions Architect working on generative [AI](https://alldogssportspark.com) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](http://swwwwiki.coresv.net) center. She is enthusiastic about building services that assist clients accelerate their [AI](https://videofrica.com) journey and unlock organization value.<br>