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

master
Charissa De Beuzeville 2025-03-06 03:41:01 +08:00
commit 602d53cb10
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are excited to reveal that DeepSeek R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and [yewiki.org](https://www.yewiki.org/User:MaisieRoldan5) Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://gomyneed.com)'s first-generation frontier design, DeepSeek-R1, [wiki.asexuality.org](https://wiki.asexuality.org/w/index.php?title=User_talk:CharleneCuningha) along with the distilled variations ranging from 1.5 to 70 billion parameters to build, experiment, and responsibly scale your generative [AI](https://git.rungyun.cn) ideas on AWS.<br>
<br>In this post, we show how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to deploy the distilled variations of the models as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) developed by DeepSeek [AI](https://youarealways.online) that uses support finding out to enhance reasoning capabilities through a multi-stage training [process](http://129.211.184.1848090) from a DeepSeek-V3-Base structure. An essential differentiating feature is its support learning (RL) action, which was used to improve the model's responses beyond the standard pre-training and tweak procedure. By including RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately enhancing both importance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, implying it's geared up to break down complicated queries and reason through them in a detailed manner. This guided reasoning process allows the model to produce more precise, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT abilities, aiming to produce structured responses while focusing on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has recorded the industry's attention as a flexible text-generation model that can be integrated into various workflows such as representatives, sensible thinking and information analysis tasks.<br>
<br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture enables activation of 37 billion criteria, [enabling efficient](https://gitlab-dev.yzone01.com) reasoning by routing inquiries to the most appropriate specialist "clusters." This approach allows the model to specialize in various problem domains while maintaining total efficiency. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 [xlarge circumstances](https://parejas.teyolia.mx) to deploy the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 design to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller, more effective models to mimic the habits and thinking patterns of the bigger DeepSeek-R1 model, utilizing it as a teacher design.<br>
<br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock [Marketplace](https://slovenskymedved.sk). Because DeepSeek-R1 is an emerging design, we recommend releasing this design with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid harmful content, and evaluate models against essential security requirements. At the time of composing this blog, for DeepSeek-R1 releases on [SageMaker JumpStart](http://1.117.194.11510080) and [Bedrock](https://wiki.atlantia.sca.org) Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create numerous guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing security controls across your generative [AI](http://git.oksei.ru) [applications](https://www.calogis.com).<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e instance. To check if you have quotas for P5e, [wiki.eqoarevival.com](https://wiki.eqoarevival.com/index.php/User:Sylvia77R6526) open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and validate you're utilizing ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge [circumstances](https://www.elitistpro.com) in the AWS Region you are releasing. To request a limitation increase, produce a limitation increase demand and connect to your account group.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For directions, see Establish authorizations to use 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 examine models against key safety requirements. You can carry out precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and model reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail utilizing the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
<br>The general circulation involves 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 to the design for inference. After getting the design's output, another guardrail check is used. If the output passes this last check, it's [returned](https://www.usbstaffing.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 took place at the input or output phase. The examples showcased in the following sections demonstrate inference using this API.<br>
<br>Deploy DeepSeek-R1 in [Amazon Bedrock](http://41.111.206.1753000) Marketplace<br>
<br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and [it-viking.ch](http://it-viking.ch/index.php/User:Faye68A072588) specialized structure designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following actions:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure under Foundation models in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to conjure up the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a supplier and pick the DeepSeek-R1 design.<br>
<br>The design detail page provides vital details about the model's capabilities, pricing structure, and [application standards](http://aat.or.tz). You can find detailed use instructions, consisting of sample API calls and code snippets for integration. The model supports different text generation tasks, consisting of content creation, code generation, and concern answering, utilizing its support finding out optimization and CoT thinking abilities.
The page also consists of deployment choices and licensing details to help you start with DeepSeek-R1 in your applications.
3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
<br>You will be triggered to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Number of instances, enter a number of circumstances (between 1-100).
6. For Instance type, pick your circumstances type. For ideal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
Optionally, you can set up sophisticated security and facilities settings, including virtual private cloud (VPC) networking, service role consents, and file encryption settings. For a lot of use cases, the default settings will work well. However, for [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11943978) production deployments, you may wish to review these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to start using the model.<br>
<br>When the deployment is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
8. Choose Open in play area to access an interactive interface where you can try out different triggers and adjust model parameters like temperature and maximum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for ideal results. For example, content for reasoning.<br>
<br>This is an outstanding method to check out the [model's reasoning](https://career.logictive.solutions) and text generation [capabilities](https://gitlab.dndg.it) before integrating it into your [applications](http://202.90.141.173000). The play area supplies immediate feedback, helping you comprehend how the model responds to different inputs and letting you tweak your prompts for optimum outcomes.<br>
<br>You can rapidly check the model in the play area through the UI. However, to invoke the deployed model 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 perform reasoning utilizing a released DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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 developed the guardrail, use the following code to carry out guardrails. The script initializes the bedrock_runtime customer, configures inference specifications, and sends out a demand to produce text based upon a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an [artificial intelligence](http://osbzr.com) (ML) center with FMs, built-in algorithms, and prebuilt ML solutions that you can release with just a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your data, and release them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart provides 2 hassle-free approaches: using the user-friendly SageMaker JumpStart UI or executing programmatically through the [SageMaker Python](http://119.130.113.2453000) SDK. Let's check out both approaches to help you choose the technique that finest matches your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following [actions](https://catvcommunity.com.tr) to deploy DeepSeek-R1 [utilizing SageMaker](https://stationeers-wiki.com) JumpStart:<br>
<br>1. On the SageMaker console, choose Studio in the navigation pane.
2. First-time users will be triggered to produce a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The [design web](https://hylpress.net) browser shows available designs, with details like the company name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 design card.
Each model card shows crucial details, including:<br>
<br>- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if suitable), suggesting that this design can be signed up with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to conjure up the model<br>
<br>5. Choose the model card to see the model details page.<br>
<br>The model details page [consists](https://globalhospitalitycareer.com) 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](http://gogs.kexiaoshuang.com).
- Usage guidelines<br>
<br>Before you release the model, it's suggested to review the model details and license terms to confirm compatibility with your usage case.<br>
<br>6. Choose Deploy to proceed with implementation.<br>
<br>7. For Endpoint name, utilize the automatically produced name or develop a custom-made one.
8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For [Initial](https://recrutementdelta.ca) instance count, get in the variety of circumstances (default: 1).
Selecting proper circumstances types and counts is essential for cost and performance optimization. [Monitor](https://job-daddy.com) your deployment to change these settings as needed.Under [Inference](http://pakgovtjob.site) type, Real-time reasoning is chosen by default. This is enhanced for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we strongly advise adhering to SageMaker [JumpStart default](https://2t-s.com) settings and making certain that network seclusion remains in location.
11. Choose Deploy to deploy the model.<br>
<br>The release procedure can take several minutes to complete.<br>
<br>When release is complete, your endpoint status will change to InService. At this point, the design is prepared to accept inference requests through the endpoint. You can keep an eye on the implementation progress on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the implementation is complete, you can conjure up the model using a SageMaker runtime customer and integrate 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 install the SageMaker Python SDK and make certain you have the necessary AWS consents 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 deploying the model is in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
<br>You can run additional demands against the predictor:<br>
<br>Implement guardrails and run reasoning with your [SageMaker JumpStart](https://git.prime.cv) predictor<br>
<br>Similar to Amazon Bedrock, you can likewise use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail using the Amazon Bedrock [console](http://175.27.215.923000) or the API, and implement it as revealed in the following code:<br>
<br>Tidy up<br>
<br>To avoid undesirable charges, finish the steps in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace implementation<br>
<br>If you released the [design utilizing](https://reklama-a5.by) Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon Bedrock console, under [Foundation models](https://gitlab.dndg.it) in the navigation pane, choose Marketplace implementations.
2. In the Managed deployments area, find the endpoint you want to delete.
3. Select the endpoint, and on the Actions menu, [choose Delete](https://iamtube.jp).
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 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 out how you can access and release the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to start. For [pediascape.science](https://pediascape.science/wiki/User:TreyLegg225) more details, describe 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>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative [AI](http://47.75.109.82) companies construct ingenious options using AWS services and accelerated compute. Currently, he is focused on establishing strategies for fine-tuning and [surgiteams.com](https://surgiteams.com/index.php/User:Wanda46F48) enhancing the reasoning efficiency of big language designs. In his leisure time, Vivek enjoys hiking, enjoying films, and attempting different cuisines.<br>
<br>[Niithiyn Vijeaswaran](http://travelandfood.ru) is a Generative [AI](http://24insite.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](http://gitlab.gomoretech.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is an Expert Solutions Architect working on generative [AI](https://vishwakarmacommunity.org) with the Third-Party Model Science team at AWS.<br>
<br>[Banu Nagasundaram](https://te.legra.ph) leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://whotube.great-site.net) hub. She is enthusiastic about developing options that assist clients accelerate their [AI](https://nurseportal.io) journey and unlock business value.<br>