antonioremingt/nagaev
1
0
Code Issues Actions Packages Projects Wiki

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

Antonio Remington 2025-04-11 07:43:02 +08:00
parent 137d074af1
commit 17b13c8e9d
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 excited 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://git.prime.cv)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled variations varying from 1.5 to 70 billion parameters to construct, experiment, and responsibly scale your [generative](http://39.99.224.279022) [AI](https://feniciaett.com) ideas on AWS.<br>
<br>In this post, we demonstrate how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled variations of the models too.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) established by DeepSeek [AI](http://git.hsgames.top:3000) that uses reinforcement finding out to boost thinking capabilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. A key distinguishing function is its support knowing (RL) step, which was used to improve the design's responses beyond the basic pre-training and tweak process. By including RL, DeepSeek-R1 can adjust more effectively to user feedback and objectives, ultimately improving both importance and [clarity](https://git.progamma.com.ua). In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, [indicating](https://code.linkown.com) it's geared up to break down [complicated queries](https://reckoningz.com) and reason through them in a detailed manner. This directed reasoning procedure permits the model to produce more precise, transparent, and detailed responses. This model combines RL-based fine-tuning with CoT abilities, aiming to produce structured actions while concentrating on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has caught the industry's attention as a versatile text-generation model that can be incorporated into various workflows such as agents, sensible thinking and data interpretation jobs.<br>
<br>DeepSeek-R1 utilizes a Mixture 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 questions to the most pertinent professional "clusters." This [approach](https://lab.gvid.tv) permits the model to specialize in various issue domains while maintaining general effectiveness. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge instance to deploy the model. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs offering 1128 GB of [GPU memory](http://142.93.151.79).<br>
<br>DeepSeek-R1 [distilled models](https://git.wun.im) bring the [reasoning abilities](https://git.clicknpush.ca) 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 describes a process of training smaller, more effective designs to imitate the habits and thinking patterns of the bigger DeepSeek-R1 design, using it as an instructor design.<br>
<br>You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend deploying this design with guardrails in location. In this blog, we will utilize Amazon Bedrock Guardrails to [introduce](https://gogs.tyduyong.com) safeguards, prevent harmful content, and assess designs against key security criteria. At the time of writing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create multiple guardrails tailored to different use cases and use them to the DeepSeek-R1 model, enhancing user experiences and standardizing safety controls throughout your generative [AI](http://47.105.162.154) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 model, you require 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 validate you're using 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 limit boost, develop a limit increase demand and reach out to your account team.<br>
<br>Because you will be releasing this model with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) approvals to utilize Amazon Bedrock Guardrails. For guidelines, see Set up consents to use guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails enables you to present safeguards, avoid damaging material, and evaluate models against crucial security requirements. You can execute precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to assess user inputs and [model reactions](https://tv.360climatechange.com) deployed on [Amazon Bedrock](http://101.132.73.143000) Marketplace and SageMaker JumpStart. You can create 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 flow involves the following actions: [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:IVQPete49368) 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 to the model for reasoning. After getting the [design's](https://lokilocker.com) output, another guardrail check is used. If the output passes this last check, it's returned as the outcome. However, if either the input or output is intervened by the guardrail, a message is returned indicating the nature of the intervention and whether it took place 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 offers you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, pick Model brochure under [Foundation designs](http://hammer.x0.to) 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](https://ai.ceo) as a [provider](https://skillfilltalent.com) and select the DeepSeek-R1 design.<br>
<br>The model detail page supplies essential [details](http://121.40.194.1233000) about the design's abilities, rates structure, and implementation guidelines. You can find detailed usage guidelines, including sample API calls and code snippets for combination. The design supports numerous text generation jobs, consisting of material development, code generation, and question answering, utilizing its optimization and CoT reasoning capabilities.
The page likewise includes release alternatives and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, select Deploy.<br>
<br>You will be prompted to configure the deployment details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For [Variety](http://113.105.183.1903000) of instances, get in a variety of circumstances (in between 1-100).
6. For example type, select your instance type. For optimum performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised.
Optionally, you can configure advanced security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service role consents, and file encryption settings. For many use cases, the default settings will work well. However, for production deployments, you may wish to examine these settings to align with your company's security and compliance requirements.
7. Choose Deploy to start using the model.<br>
<br>When the release is complete, you can evaluate DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
8. Choose Open in playground to access an interactive user interface where you can experiment with various prompts and adjust design criteria like temperature and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimal results. For instance, material for inference.<br>
<br>This is an excellent method to check out the model's reasoning and text generation abilities before incorporating it into your applications. The play ground provides immediate feedback, helping you understand how the model responds to different inputs and letting you fine-tune your prompts for optimal results.<br>
<br>You can rapidly test the design in the play ground through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform reasoning utilizing a released DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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 created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, sets up [inference](http://112.74.93.6622234) specifications, and sends out a demand to produce text based upon 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 solutions that you can release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, 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 instinctive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's [explore](http://139.199.191.273000) both methods to help you pick the [technique](https://app.deepsoul.es) that best fits your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following actions to release DeepSeek-R1 utilizing SageMaker JumpStart:<br>
<br>1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be prompted to create a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The design web browser displays available models, with details like the [service provider](http://8.222.247.203000) name and [design capabilities](https://www.employment.bz).<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card.
Each design card reveals crucial details, including:<br>
<br>- Model name
- Provider name
- Task classification (for instance, Text Generation).
Bedrock Ready badge (if appropriate), suggesting that this design can be signed up with Amazon Bedrock, enabling you to utilize Amazon Bedrock APIs to conjure up the design<br>
<br>5. Choose the design card to view the model details page.<br>
<br>The model details page [consists](http://h.gemho.cn7099) of the following details:<br>
<br>- The model name and service provider details.
Deploy button to release the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of essential details, such as:<br>
<br>- Model description.
- License details.
- Technical requirements.
- Usage guidelines<br>
<br>Before you release the design, it's suggested to examine the [design details](https://www.lizyum.com) and license terms to validate compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with deployment.<br>
<br>7. For [Endpoint](https://gitea.egyweb.se) name, utilize the immediately produced name or produce a custom-made one.
8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the variety of circumstances (default: 1).
Selecting proper instance types and counts is crucial for expense and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference type, [Real-time inference](https://git.toolhub.cc) is chosen by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for precision. For this design, we strongly recommend adhering to SageMaker JumpStart default settings and making certain that [network seclusion](https://cloudsound.ideiasinternet.com) remains in place.
11. Choose Deploy to deploy the model.<br>
<br>The implementation procedure can take numerous minutes to finish.<br>
<br>When implementation is complete, your endpoint status will change to InService. At this point, the design is all set to accept reasoning demands through the endpoint. You can keep an eye on the implementation progress on the SageMaker console Endpoints page, which will show relevant metrics and [status details](https://medea.medianet.cs.kent.edu). When the [deployment](http://euhope.com) is total, you can invoke the model using a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To get begun with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the required AWS consents and environment setup. The following is a detailed code example that demonstrates how to release and utilize DeepSeek-R1 for inference programmatically. The code for deploying the model is offered in the Github here. You can clone the notebook and range from SageMaker Studio.<br>
<br>You can run additional demands against the predictor:<br>
<br>Implement guardrails and run inference 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 develop a guardrail utilizing the [Amazon Bedrock](http://150.158.183.7410080) console or the API, and execute it as displayed in the following code:<br>
<br>Clean up<br>
<br>To avoid undesirable charges, complete the steps in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you released the design utilizing Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, select Marketplace releases.
2. In the Managed deployments area, find the endpoint you desire to erase.
3. Select the endpoint, and on the Actions menu, [select Delete](https://canadasimple.com).
4. Verify the endpoint details to make certain you're erasing the appropriate deployment: 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 if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we [checked](https://www.letsauth.net9999) 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 begin. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, 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](https://cyltalentohumano.com) [AI](http://www.carnevalecommunity.it) business develop ingenious services using AWS services and accelerated calculate. Currently, he is concentrated on establishing strategies for [fine-tuning](https://becalm.life) and enhancing the reasoning performance of large language models. In his downtime, Vivek takes pleasure in hiking, viewing movies, and attempting various cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://1millionjobsmw.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](http://www.c-n-s.co.kr) 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://goalsshow.com) with the Third-Party Model Science team at AWS.<br>
<br>[Banu Nagasundaram](https://www.waitumusic.com) leads item, engineering, and [strategic partnerships](https://www.boatcareer.com) for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://talentlagoon.com) center. She is passionate about developing services that help customers accelerate their [AI](https://4stour.com) journey and unlock company worth.<br>