kristihibbs200/interjinn
1
0
Code Issues Actions Packages Projects Wiki

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

Kristi Hibbs 2025-04-08 04:00:48 +08:00
commit bfd08de6d3
1 changed files with 93 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart.-.md Normal file

@ -0,0 +1,93 @@
<br>Today, we are delighted 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://wiki.whenparked.com)'s first-generation frontier design, DeepSeek-R1, along with the distilled variations ranging from 1.5 to 70 billion criteria to construct, experiment, and responsibly scale your generative [AI](https://jobsscape.com) [concepts](https://pediascape.science) 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 similar steps to release the distilled variations of the designs as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language design (LLM) established by DeepSeek [AI](https://www.hijob.ca) that uses reinforcement discovering to boost reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A crucial identifying feature is its reinforcement knowing (RL) action, which was utilized to improve the design's actions beyond the standard pre-training and fine-tuning process. By incorporating RL, DeepSeek-R1 can adjust more effectively to user feedback and objectives, eventually enhancing both importance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, indicating it's equipped to break down complex queries and reason through them in a detailed way. This assisted reasoning process enables the design to produce more accurate, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT abilities, aiming to generate structured actions while concentrating on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has actually recorded the industry's attention as a versatile text-generation model that can be incorporated into different workflows such as representatives, [rational reasoning](http://git.chaowebserver.com) and information analysis tasks.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion specifications, enabling effective inference by routing inquiries to the most appropriate professional "clusters." This method enables the model to specialize in various issue domains while maintaining total [performance](http://thegrainfather.com). DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge circumstances to deploy the design. ml.p5e.48 xlarge includes 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 on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of [training](https://cloudsound.ideiasinternet.com) smaller sized, more effective designs to mimic the behavior and reasoning patterns of the larger DeepSeek-R1 model, using it as an instructor model.<br>
<br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest deploying this design with guardrails in place. In this blog, we will [utilize Amazon](http://118.25.96.1183000) Bedrock Guardrails to introduce safeguards, avoid harmful material, and assess models against key safety requirements. At the time of writing this blog, for DeepSeek-R1 deployments on [SageMaker JumpStart](http://139.224.213.43000) and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce numerous guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls across your generative [AI](http://47.100.23.37) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 design, you require access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and validate you're utilizing ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 [xlarge circumstances](https://www.anetastaffing.com) in the AWS Region you are deploying. To request a limit boost, create a limit increase request and connect to your account team.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the appropriate [AWS Identity](https://dztrader.com) and Gain Access To Management (IAM) permissions to use Amazon Bedrock Guardrails. For directions, 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 present safeguards, avoid damaging material, and assess designs against key security requirements. You can execute security steps for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and design actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop 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 general circulation 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 getting the design's output, another guardrail check is used. If the output passes this last 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 happened at the input or output phase. The examples showcased in the following sections demonstrate inference utilizing this API.<br>
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
<br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To [gain access](https://git.goolink.org) to DeepSeek-R1 in Amazon Bedrock, total the following actions:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure 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 doesn't support Converse APIs and other [Amazon Bedrock](https://gitlab.econtent.lu) tooling.
2. Filter for DeepSeek as a provider and pick the DeepSeek-R1 model.<br>
<br>The design detail page offers important details about the model's abilities, rates structure, and [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11860868) implementation guidelines. You can discover detailed usage guidelines, consisting of sample API calls and code bits for combination. The model supports various text generation jobs, including material development, code generation, and [concern](http://dkjournal.co.kr) answering, utilizing its reinforcement finding out optimization and CoT thinking capabilities.
The page also includes implementation options and [licensing details](https://albion-albd.online) to assist you start with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, select Deploy.<br>
<br>You will be triggered to set up the release details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
5. For Variety of instances, go into a variety of circumstances (in between 1-100).
6. For Instance type, pick your circumstances type. For optimal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can configure innovative security and infrastructure settings, including virtual personal cloud (VPC) networking, service function approvals, and encryption settings. For most use cases, the default settings will work well. However, for production implementations, you might desire to examine these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to start utilizing the model.<br>
<br>When the deployment is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
8. Choose Open in playground to access an interactive user interface where you can experiment with different prompts and change design specifications like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum results. For example, material for reasoning.<br>
<br>This is an excellent way to explore the model's thinking and text generation abilities before incorporating it into your [applications](https://inktal.com). The play ground provides immediate feedback, [assisting](http://47.108.239.2023001) you understand how the design reacts to various inputs and letting you fine-tune your [triggers](http://www.zhihutech.com) for ideal results.<br>
<br>You can quickly check the model in the play ground through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference utilizing guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to [perform inference](http://dev.ccwin-in.com3000) using a released DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can create a [guardrail utilizing](https://chatgay.webcria.com.br) the Amazon Bedrock console or the API. For the example code to create the guardrail, see the [GitHub repo](https://git.sommerschein.de). After you have produced the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, sets up reasoning specifications, and sends out a request 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) hub with FMs, built-in algorithms, and prebuilt ML options that you can deploy with just a couple of 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 SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart provides two convenient approaches: [utilizing](https://musicplayer.hu) the intuitive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you select the approach that best matches your needs.<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 console, select Studio in the navigation pane.
2. First-time users will be triggered to develop a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
<br>The model web browser shows available designs, with details like the provider name and design abilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card shows essential details, including:<br>
<br>- Model name
- Provider name
- Task category (for example, Text Generation).
[Bedrock Ready](https://remnantstreet.com) badge (if suitable), suggesting that this design can be signed up with Amazon Bedrock, enabling you to [utilize Amazon](https://playtube.ann.az) to conjure up the design<br>
<br>5. Choose the [model card](https://redmonde.es) to see the model details page.<br>
<br>The design details page consists of the following details:<br>
<br>- The design name and company details.
Deploy button to release 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 requirements.
- Usage standards<br>
<br>Before you deploy the model, it's advised to review the model details and license terms to [verify compatibility](http://8.138.140.943000) with your use case.<br>
<br>6. Choose Deploy to [continue](http://wowonder.technologyvala.com) with release.<br>
<br>7. For Endpoint name, use the immediately generated name or create a custom one.
8. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the variety of circumstances (default: 1).
Selecting appropriate circumstances types and counts is vital for cost and performance optimization. Monitor your deployment 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 precision. For this model, we strongly recommend adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to deploy the model.<br>
<br>The implementation procedure can take several minutes to complete.<br>
<br>When implementation is complete, your endpoint status will change to InService. At this moment, the design is all set to accept inference demands through the [endpoint](https://jobs.ezelogs.com). You can keep track of the release development on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the release is complete, you can invoke the design using a SageMaker runtime client and integrate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the necessary 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 supplied in the Github here. You can clone the notebook and range 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 produce a guardrail using the Amazon Bedrock console or the API, and implement it as revealed in the following code:<br>
<br>Clean up<br>
<br>To avoid undesirable charges, finish the steps in this area to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you [deployed](https://theglobalservices.in) the design 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 implementations.
2. In the Managed deployments area, find the endpoint 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 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 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](https://www.olindeo.net) now to get begun. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going 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://praca.e-logistyka.pl) companies build innovative services utilizing AWS services and accelerated calculate. Currently, he is concentrated on developing strategies for fine-tuning and optimizing the reasoning efficiency of big language models. In his leisure time, Vivek takes pleasure in hiking, [viewing motion](https://www.so-open.com) pictures, and trying different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://meephoo.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](https://parissaintgermainfansclub.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Professional Solutions Architect dealing with generative [AI](https://jovita.com) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, [SageMaker's artificial](https://schoolmein.com) intelligence and generative [AI](https://nusalancer.netnation.my.id) hub. She is passionate about developing solutions that help consumers accelerate their [AI](https://ideezy.com) journey and unlock business value.<br>