ceciliawinkle/uucloud
1
0
Code Issues Packages Projects Wiki

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

Cecilia Winkle
2025-04-03 15:43:35 +09:00
parent d455438a9e
commit 756519aa03
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 and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://fatims.org)'s first-generation frontier model, DeepSeek-R1, in addition to the distilled variations ranging from 1.5 to 70 billion [criteria](http://sgvalley.co.kr) to build, experiment, and properly scale your generative [AI](http://plus-tube.ru) concepts on AWS.<br>
<br>In this post, we show how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to [release](https://livy.biz) the distilled versions of the models also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://www.meetyobi.com) that uses support learning to improve reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. An essential identifying function is its support learning (RL) action, which was used to fine-tune the design's responses beyond the standard pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adjust better to user feedback and objectives, ultimately enhancing both importance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) technique, [indicating](https://git.magicvoidpointers.com) it's geared up to break down complex queries and factor through them in a [detailed](https://laborando.com.mx) way. This guided thinking procedure enables the model to produce more precise, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT capabilities, aiming to create structured responses while focusing on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has captured the industry's attention as a versatile text-generation design that can be incorporated into numerous workflows such as agents, rational reasoning and information interpretation jobs.<br>
<br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion criteria, making it possible for effective inference by routing queries to the most pertinent specialist "clusters." This technique permits the model to specialize in various problem domains while maintaining overall efficiency. 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 features 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs 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 describes a process of training smaller, more efficient models to mimic the behavior and reasoning patterns of the bigger DeepSeek-R1 design, using 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 suggest releasing this design with guardrails in place. In this blog, we will utilize Amazon [Bedrock](https://git.uucloud.top) Guardrails to present safeguards, prevent hazardous material, and examine models against essential security requirements. At the time of writing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create [numerous guardrails](https://www.thempower.co.in) tailored to different use cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing safety [controls](http://219.150.88.23433000) throughout your generative [AI](https://circassianweb.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you need access to an ml.p5e instance. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose 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 circumstances in the AWS Region you are deploying. To request a limitation increase, create a limit boost 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) permissions to utilize Amazon Bedrock Guardrails. For guidelines, see Set up authorizations to use guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to introduce safeguards, avoid hazardous material, and assess designs against key safety criteria. You can implement precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to examine user inputs and model actions released on Amazon Bedrock [Marketplace](https://www.jungmile.com) and SageMaker JumpStart. You can [develop](https://git.obo.cash) a guardrail utilizing 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 steps: First, the system gets 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 design for inference. After receiving the design's output, another guardrail check is used. 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 indicating the nature of the intervention and whether it happened at the input or output stage. The examples showcased in the following areas show reasoning using this API.<br>
<br>Deploy DeepSeek-R1 in [Amazon Bedrock](http://47.96.15.2433000) Marketplace<br>
<br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized structure [designs](https://git.flandre.net) (FMs) through [Amazon Bedrock](https://cagit.cacode.net). 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 designs in the [navigation](https://www.frigorista.org) 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 as a company and select the DeepSeek-R1 model.<br>
<br>The design detail page provides necessary details about the model's capabilities, pricing structure, and application guidelines. You can find detailed usage directions, including sample API calls and code bits for combination. The design supports different text generation jobs, [consisting](http://www.chemimart.kr) of content development, code generation, and concern answering, utilizing its support learning [optimization](https://lifefriendsurance.com) and CoT reasoning abilities.
The page also includes release choices and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, choose Deploy.<br>
<br>You will be triggered to set up the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, get in an [endpoint](https://www.wcosmetic.co.kr5012) name (between 1-50 alphanumeric characters).
5. For Variety of instances, enter a number of circumstances (in between 1-100).
6. For Instance type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
Optionally, you can configure advanced security and infrastructure settings, including virtual private cloud (VPC) networking, service function consents, and encryption settings. For a lot of utilize cases, the default settings will work well. However, for production releases, you may want to evaluate these [settings](https://www.punajuaj.com) to align with your organization's security and compliance requirements.
7. Choose Deploy to begin utilizing the design.<br>
<br>When the deployment is total, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
8. Choose Open in play area to access an interactive interface where you can try out various triggers and change model parameters like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for ideal results. For example, material for reasoning.<br>
<br>This is an outstanding way to explore the design's thinking and [higgledy-piggledy.xyz](https://higgledy-piggledy.xyz/index.php/User:Sunny732248) text generation abilities before incorporating it into your applications. The play area supplies immediate feedback, helping you understand how the model responds to various inputs and letting you tweak your prompts for optimum outcomes.<br>
<br>You can quickly check the design in the playground through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run inference using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example shows 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](http://www.grandbridgenet.com82) console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have created the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, [configures reasoning](http://git.taokeapp.net3000) parameters, and sends a demand to generate text based on a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and prebuilt ML solutions that you can release with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and [raovatonline.org](https://raovatonline.org/author/hrqjeannine/) release them into [production utilizing](https://git.obo.cash) either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart uses two convenient methods: utilizing the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both techniques to help you choose the method that best suits your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following actions 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 create a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The design browser displays available models, with details like the provider name and model capabilities.<br>
<br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each design card reveals key details, including:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if applicable), suggesting that this model can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to conjure up the design<br>
<br>5. Choose the model card to view the design 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 includes crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical requirements.
- Usage guidelines<br>
<br>Before you release the model, it's suggested to review the model details and license terms to [verify compatibility](https://blessednewstv.com) with your usage case.<br>
<br>6. Choose Deploy to continue with release.<br>
<br>7. For Endpoint name, utilize the automatically generated name or develop a customized one.
8. For Instance type ¸ select an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, go into the number of circumstances (default: 1).
Selecting appropriate instance types and counts is important for cost and efficiency optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, [yewiki.org](https://www.yewiki.org/User:FredGoble653) Real-time reasoning is selected by default. This is optimized for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we highly recommend adhering to SageMaker JumpStart default settings and making certain that network isolation remains in [location](https://taar.me).
11. Choose Deploy to deploy the design.<br>
<br>The implementation procedure can take numerous minutes to finish.<br>
<br>When release is complete, your endpoint status will alter to InService. At this moment, the model is ready to accept inference demands through the endpoint. You can keep an eye on the [implementation progress](https://gitea.nasilot.me) on the SageMaker console Endpoints page, which will [display relevant](http://peterlevi.com) metrics and status details. When the deployment is total, you can [conjure](https://yourmoove.in) up the model using a SageMaker runtime customer and incorporate 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 need to set up the SageMaker Python SDK and make certain you have the needed AWS authorizations and environment setup. The following is a detailed code example that shows how to deploy and utilize DeepSeek-R1 for [inference programmatically](https://mount-olive.com). The code for [deploying](http://101.34.87.71) the model is [offered](https://lovn1world.com) in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
<br>You can run additional requests against the predictor:<br>
<br>Implement guardrails and run reasoning with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can likewise utilize 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 displayed in the following code:<br>
<br>Tidy up<br>
<br>To avoid undesirable charges, [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:AnnelieseCheel) 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 using 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](http://hmkjgit.huamar.com) you want to erase.
3. Select the endpoint, and on the Actions menu, [select Delete](https://gofleeks.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 erase 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 out how you can access and release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get going. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Beginning 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://gofleeks.com) business build [innovative options](https://diversitycrejobs.com) using AWS and sped up compute. Currently, he is [focused](http://git.meloinfo.com) on developing techniques for fine-tuning and enhancing the reasoning efficiency of large language designs. In his totally free time, Vivek takes pleasure in treking, viewing films, and [attempting](https://vidacibernetica.com) various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://www.chinami.com) Specialist Solutions Architect with the Third-Party Model [Science](https://paknoukri.com) team at AWS. His location of focus is AWS [AI](https://git.xedus.ru) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is a Professional Solutions Architect working on generative [AI](https://visualchemy.gallery) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://kol-jobs.com) center. She is [enthusiastic](http://47.101.131.2353000) about constructing services that assist consumers accelerate their [AI](https://somkenjobs.com) journey and unlock service value.<br>