berenicefunnel/agdatatec
1
0
Code Issues Packages Projects Wiki

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

Berenice Funnell
2025-03-06 12:57:02 +08:00
commit 664ebf0cc5
1 changed files with 93 additions and 0 deletions
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 reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock [Marketplace](https://eduberkah.disdikkalteng.id) and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](http://git.spaceio.xyz)'s first-generation frontier model, DeepSeek-R1, in addition to the [distilled variations](https://kkhelper.com) ranging from 1.5 to 70 billion specifications to construct, experiment, and responsibly scale your generative [AI](http://zeus.thrace-lan.info:3000) ideas 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 steps to release the distilled versions of the designs as well.<br>
<br>[Overview](http://haiji.qnoddns.org.cn3000) of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language design (LLM) established by DeepSeek [AI](https://tayseerconsultants.com) that uses support learning to improve thinking abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. An essential distinguishing feature is its [reinforcement learning](https://git.fpghoti.com) (RL) action, which was used to improve the [design's responses](http://150.158.183.7410080) beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adapt better to user feedback and goals, eventually boosting both importance and clearness. In addition, [garagesale.es](https://www.garagesale.es/author/marcyschwar/) DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, implying it's geared up to break down intricate inquiries and reason through them in a detailed manner. This assisted reasoning process enables the model to produce more accurate, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT capabilities, aiming to create structured responses while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has caught the industry's attention as a versatile text-generation model that can be integrated into different [workflows](https://git.dadunode.com) such as agents, sensible reasoning and data analysis jobs.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion parameters, making it possible for effective inference by routing inquiries to the most pertinent [specialist](https://usa.life) "clusters." This technique permits the design to specialize in different issue domains while maintaining general efficiency. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge instance to [release](http://www.my.vw.ru) the design. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning capabilities of the main R1 model to more effective architectures based on popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more effective models to simulate the habits and reasoning patterns of the bigger DeepSeek-R1 design, utilizing it as an instructor model.<br>
<br>You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest deploying this model with [guardrails](https://lat.each.usp.br3001) in location. In this blog, we will use Amazon Bedrock Guardrails to present safeguards, prevent harmful material, and examine models against key security criteria. At the time of [composing](https://niaskywalk.com) this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create numerous guardrails tailored to various usage cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing safety controls across your generative [AI](https://kaymack.careers) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you need access to an ml.p5e circumstances. To examine if you have quotas for P5e, open the Service Quotas [console](https://193.31.26.118) and under AWS Services, select 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](https://virtualoffice.com.ng) in the AWS Region you are deploying. To request a limit boost, create a limit increase request and reach out to your account team.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For directions, see Set up permissions to use guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to introduce safeguards, prevent damaging content, and assess models against key safety criteria. You can execute security measures for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to evaluate user inputs and model responses deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce 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 circulation involves the following actions: First, the system gets an input for the design. This input is then processed through the [ApplyGuardrail API](https://git.satori.love). If the input passes the guardrail check, it's sent out to the design for inference. After receiving the design's output, another guardrail check is applied. If the output passes this final check, it's returned as the result. 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 occurred at the input or output stage. The examples showcased in the following sections show reasoning 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 structure 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, choose Model catalog under Foundation models in the navigation pane.
At the time of writing this post, you can use the [InvokeModel API](http://47.107.29.613000) to invoke the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and select the DeepSeek-R1 model.<br>
<br>The model detail page supplies important details about the model's abilities, prices structure, and execution standards. You can find detailed usage instructions, consisting of sample API calls and code snippets for combination. The design supports various text generation tasks, consisting of material creation, code generation, and concern answering, using its reinforcement learning optimization and CoT thinking capabilities.
The page likewise consists of release options and licensing details to help you get going with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, pick Deploy.<br>
<br>You will be triggered to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, get in an [endpoint](http://192.241.211.111) name (between 1-50 alphanumeric characters).
5. For Variety of circumstances, enter a number of instances (in between 1-100).
6. For example type, choose your instance type. For optimum efficiency with DeepSeek-R1, a [GPU-based instance](https://gl.vlabs.knu.ua) type like ml.p5e.48 xlarge is recommended.
Optionally, you can configure sophisticated security and infrastructure settings, consisting of 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 examine these settings to line up with your [organization's security](https://git.gumoio.com) and compliance requirements.
7. Choose Deploy to start using the model.<br>
<br>When the implementation is complete, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
8. Choose Open in play area to access an interactive user interface where you can explore different triggers and change model parameters like temperature level and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimum results. For instance, material for inference.<br>
<br>This is an excellent method to check out the model's reasoning and text generation capabilities before incorporating it into your applications. The play area offers immediate feedback, [helping](http://fggn.kr) you comprehend how the [design responds](http://xn--vk1b975azoatf94e.com) to numerous inputs and letting you tweak 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 require to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform reasoning utilizing a deployed DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can produce 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 actually produced the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, configures reasoning criteria, and sends a demand to produce 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, integrated algorithms, and prebuilt ML services 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 deploy them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart offers 2 hassle-free techniques: [utilizing](http://jerl.zone3000) the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both [methods](https://www.execafrica.com) to assist you pick the method that best matches your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps to release DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the SageMaker console, choose Studio in the navigation pane.
2. First-time users will be prompted to create a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
<br>The design browser shows available models, with details like the service provider name and design abilities.<br>
<br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card.
Each model card reveals essential details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for instance, Text Generation).
Bedrock Ready badge (if appropriate), showing that this model can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to invoke the model<br>
<br>5. Choose the design card to see the model details page.<br>
<br>The design details page [consists](http://106.55.3.10520080) of the following details:<br>
<br>- The model name and company details.
Deploy button to [release](https://edu.shpl.ru) 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](https://trackrecord.id) requirements.
- Usage standards<br>
<br>Before you release the design, it's [recommended](http://47.103.91.16050903) to review the model details and license terms to validate compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with implementation.<br>
<br>7. For Endpoint name, use the immediately produced name or produce a custom-made one.
8. For example type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, get in the number of circumstances (default: 1).
Selecting suitable instance types and counts is important for expense and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference 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 model, we strongly advise adhering to [SageMaker JumpStart](http://140.82.32.174) default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the model.<br>
<br>The deployment procedure can take numerous minutes to complete.<br>
<br>When release is complete, your endpoint status will alter to InService. At this moment, the design is ready to accept reasoning requests through the endpoint. You can keep track of the deployment development on the SageMaker [console Endpoints](https://beta.talentfusion.vn) page, which will show relevant metrics and status [details](https://git.frugt.org). When the release is total, you can conjure up 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 started with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS permissions and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for reasoning programmatically. The code for deploying the model is provided 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 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 utilizing](https://www.cbl.aero) the Amazon Bedrock console or the API, and implement it as revealed in the following code:<br>
<br>Clean up<br>
<br>To avoid unwanted charges, finish the steps in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you released the model utilizing Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the pane, select Marketplace releases.
2. In the Managed implementations area, locate the endpoint you desire 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 right release: 1. Endpoint name.
2. Model name.
3. [Endpoint](https://skillfilltalent.com) status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you released will sustain expenses if you leave it running. Use the following code to delete the endpoint if you desire 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 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon [Bedrock Marketplace](http://180.76.133.25316300) now to get started. 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 Getting started with Amazon SageMaker JumpStart.<br>
<br>About the Authors<br>
<br>[Vivek Gangasani](https://www.wotape.com) is a Lead Specialist Solutions Architect for [Inference](https://git.cavemanon.xyz) at AWS. He [assists emerging](https://git.ascarion.org) generative [AI](http://101.132.100.8) business build innovative solutions using AWS services and accelerated calculate. Currently, he is concentrated on establishing methods for fine-tuning and enhancing the inference performance of big [language](https://gogs.kakaranet.com) models. In his complimentary time, Vivek delights in hiking, seeing motion pictures, and trying various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://durfee.mycrestron.com:3000) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](https://kaymack.careers) accelerators (AWS Neuron). He holds a [Bachelor's degree](http://haiji.qnoddns.org.cn3000) in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect dealing with generative [AI](https://3srecruitment.com.au) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](http://vivefive.sakura.ne.jp) center. She is enthusiastic about developing options that help clients accelerate their [AI](https://www.bakicicepte.com) journey and unlock organization worth.<br>