hungsilverman/gdguanhui
1
0
Code Issues Actions Packages Projects Wiki

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

Hung Silverman 2025-02-09 17:46:26 +04:00
commit 45c3ce720d
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 deploy DeepSeek [AI](https://git.mhurliman.net)'s first-generation frontier model, DeepSeek-R1, along with the distilled versions varying from 1.5 to 70 billion criteria to build, [surgiteams.com](https://surgiteams.com/index.php/User:KaseyDees635) experiment, and properly scale your generative [AI](http://93.104.210.100:3000) ideas on AWS.<br>
<br>In this post, we demonstrate how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled versions of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language design (LLM) established by DeepSeek [AI](http://wiki-tb-service.com) that uses reinforcement finding out to enhance thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key differentiating feature is its reinforcement learning (RL) action, which was utilized to fine-tune the model's responses beyond the standard pre-training and fine-tuning procedure. By integrating RL, DeepSeek-R1 can adapt more effectively to user feedback and goals, ultimately improving both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, meaning it's equipped to break down complex questions and reason through them in a detailed manner. This assisted reasoning procedure enables the design to [produce](http://47.76.141.283000) more precise, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT abilities, aiming to produce structured responses while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has actually recorded the market's attention as a flexible text-generation design that can be integrated into different workflows such as agents, sensible thinking and information interpretation tasks.<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 specifications, enabling effective inference by routing questions to the most relevant expert "clusters." This method enables the model to focus on various problem domains while maintaining general efficiency. 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 design. ml.p5e.48 [xlarge features](https://iklanbaris.id) 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the reasoning capabilities of the main R1 design to more [effective architectures](https://hellovivat.com) based upon popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more effective designs to mimic the behavior and thinking patterns of the larger DeepSeek-R1 model, using it as a [teacher design](http://shenjj.xyz3000).<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 model with guardrails in place. In this blog site, we will use Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and evaluate designs against essential security requirements. At the time of writing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can [develop numerous](http://www.forwardmotiontx.com) guardrails tailored to different use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative [AI](http://182.92.143.66:3000) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 design, you need access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and confirm you're utilizing ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To ask for a limit increase, develop a limitation increase demand 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 right AWS Identity and [Gain Access](https://prsrecruit.com) To Management (IAM) permissions to use Amazon Bedrock Guardrails. For directions, see Set up authorizations to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails permits you to introduce safeguards, prevent harmful material, and evaluate designs against crucial safety criteria. You can carry out [precaution](http://gogs.black-art.cn) for the DeepSeek-R1 model using the Amazon Bedrock [ApplyGuardrail API](http://tesma.co.kr). This permits you to apply guardrails to evaluate user inputs and design reactions deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail utilizing the Amazon [Bedrock console](https://adsall.net) 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 receives 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 getting the design's output, another guardrail check is applied. If the output passes this final 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 happened at the input or output stage. The examples showcased in the following areas show inference using 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 designs (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 composing this post, you can utilize the InvokeModel API to invoke the design. It doesn't support Converse APIs and other [Amazon Bedrock](https://jobs.cntertech.com) tooling.
2. Filter for [DeepSeek](https://guiding-lights.com) as a provider and choose the DeepSeek-R1 design.<br>
<br>The model detail page provides vital details about the model's capabilities, rates structure, and application standards. You can find detailed use directions, consisting of sample API calls and code snippets for integration. The model supports numerous text generation tasks, [consisting](https://m1bar.com) of content development, code generation, and question answering, utilizing its support finding out optimization and CoT reasoning abilities.
The page likewise consists of release alternatives and licensing details to help you get going with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, choose Deploy.<br>
<br>You will be triggered to configure the deployment details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
5. For Number of instances, go into a number of circumstances (between 1-100).
6. For example type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised.
Optionally, [oeclub.org](https://oeclub.org/index.php/User:MauricioRdz) you can configure advanced security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service function authorizations, and file encryption settings. For the majority of utilize cases, the default settings will work well. However, for production implementations, you might wish to review these settings to align with your organization's security and compliance requirements.
7. Choose Deploy to begin using the design.<br>
<br>When the release is total, you can test DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
8. Choose Open in playground to access an interactive user interface where you can explore various triggers and change model parameters like temperature and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimal results. For example, material for inference.<br>
<br>This is an excellent method to check out the design's reasoning and text generation capabilities before integrating it into your applications. The play area supplies instant feedback, helping you comprehend how the model reacts to different inputs and letting you fine-tune your prompts for optimum outcomes.<br>
<br>You can rapidly evaluate the model in the playground through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform inference utilizing a deployed DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. 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. After you have actually developed the guardrail, [utilize](http://git.sdkj001.cn) the following code to implement guardrails. The script [initializes](https://git.daoyoucloud.com) the bedrock_runtime client, sets up inference criteria, and sends a demand to generate text based upon a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an [artificial intelligence](http://forum.kirmizigulyazilim.com) (ML) hub with FMs, built-in algorithms, [raovatonline.org](https://raovatonline.org/author/dwaynepalme/) and prebuilt ML [solutions](https://www.genbecle.com) that you can deploy with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11879073) release them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart offers two practical methods: using the intuitive SageMaker JumpStart UI or implementing programmatically through the [SageMaker Python](https://takesavillage.club) SDK. Let's check out both methods to assist you select the method that best fits your requirements.<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, pick Studio in the navigation pane.
2. First-time users will be triggered to create a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The design internet browser displays available models, [wavedream.wiki](https://wavedream.wiki/index.php/User:TammieRaposo6) with details like the supplier name and model abilities.<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card.
Each design card shows essential details, [consisting](http://hmind.kr) of:<br>
<br>- Model name
- Provider name
- Task (for instance, Text Generation).
[Bedrock Ready](https://gitlab.vp-yun.com) badge (if relevant), indicating that this design can be registered with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to invoke the model<br>
<br>5. Choose the model card to view the model details page.<br>
<br>The design details page includes the following details:<br>
<br>- The design name and supplier details.
[Deploy button](https://thenolugroup.co.za) to release the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of important details, such as:<br>
<br>- Model description.
- License details.
- Technical specifications.
- Usage guidelines<br>
<br>Before you deploy the design, it's recommended to review the design details and license terms to verify compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with implementation.<br>
<br>7. For Endpoint name, utilize the instantly produced name or create a custom-made one.
8. For Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of instances (default: 1).
Selecting suitable instance types and counts is crucial for cost and efficiency optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time inference is selected by default. This is [optimized](http://git.1473.cn) for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we strongly recommend sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the model.<br>
<br>The [release procedure](https://remnantstreet.com) can take several minutes to finish.<br>
<br>When release is total, your [endpoint status](http://120.77.67.22383) will alter to InService. At this moment, the model is prepared to accept reasoning [requests](https://git.alexavr.ru) through the endpoint. You can keep track of the release development on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the deployment is total, you can conjure up the [design utilizing](https://zidra.ru) a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To begin with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the [essential AWS](http://www.ipbl.co.kr) consents 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 supplied in the Github here. You can clone the note pad and run 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://www.ssecretcoslab.com) predictor<br>
<br>Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail using the Amazon Bedrock console or the API, and execute it as revealed in the following code:<br>
<br>Tidy up<br>
<br>To prevent unwanted charges, finish the steps in this area to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace implementation<br>
<br>If you deployed the model using Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
2. In the Managed implementations area, find the endpoint you wish to erase.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the proper implementation: 1. [Endpoint](https://shiatube.org) name.
2. Model name.
3. Endpoint 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 erase 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](https://sebagai.com) JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to start. For more details, describe Use Amazon Bedrock [tooling](http://clinicanevrozov.ru) with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting with Amazon SageMaker [JumpStart](https://kaamdekho.co.in).<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for [Inference](http://101.132.163.1963000) at AWS. He helps emerging generative [AI](http://182.92.143.66:3000) companies construct innovative options utilizing AWS services and accelerated compute. Currently, he is concentrated on establishing techniques for fine-tuning and optimizing the reasoning efficiency of big language models. In his downtime, Vivek takes pleasure in treking, enjoying movies, and attempting various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://119.29.81.51) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](https://www.behavioralhealthjobs.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect dealing with generative [AI](https://freelancejobsbd.com) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](http://40.73.118.158) hub. She is passionate about building services that assist consumers accelerate their [AI](https://gps-hunter.ru) journey and unlock organization value.<br>