elvisnewcomer
/
tfjiang
1
0
Code Issues Packages Projects Wiki

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

Elvis Newcomer 2025-04-12 08:20:32 +00:00
commit 7ac1f60856
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 thrilled 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://www.luckysalesinc.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions varying from 1.5 to 70 billion parameters to build, experiment, [forum.pinoo.com.tr](http://forum.pinoo.com.tr/profile.php?id=1356302) and properly scale your [generative](http://47.108.161.783000) [AI](https://www.usbstaffing.com) ideas on AWS.<br>
<br>In this post, we [demonstrate](https://dooplern.com) how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to deploy the distilled versions of the designs too.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) developed by DeepSeek [AI](https://www.wikispiv.com) that uses reinforcement learning to enhance thinking abilities through a multi-stage training [procedure](https://git.yharnam.xyz) from a DeepSeek-V3-Base structure. A crucial distinguishing [feature](http://47.114.82.1623000) is its support knowing (RL) action, which was used to refine the design's reactions beyond the standard pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately boosting both significance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, indicating it's geared up to break down intricate inquiries and reason through them in a detailed manner. This assisted reasoning procedure allows the design to produce more accurate, transparent, and detailed responses. This design integrates [RL-based fine-tuning](https://jobs.ahaconsultant.co.in) with CoT capabilities, aiming to generate structured actions while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has recorded the market's attention as a flexible text-generation model that can be integrated into different [workflows](https://prsrecruit.com) such as agents, logical thinking and information analysis jobs.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) [architecture](https://rhcstaffing.com) and is 671 billion criteria in size. The MoE architecture allows activation of 37 billion specifications, enabling efficient reasoning by routing questions to the most pertinent expert "clusters." This method enables the design to focus on various issue domains while maintaining total effectiveness. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 [xlarge circumstances](https://chemitube.com) to deploy the model. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 model to more efficient architectures based upon [popular](https://jobspage.ca) open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller, more efficient designs to mimic the behavior and thinking patterns of the larger DeepSeek-R1 model, 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 design, we recommend releasing this design with guardrails in location. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent hazardous material, and examine models against key safety criteria. At the time of composing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create several guardrails tailored to various usage cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative [AI](https://dainiknews.com) .<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 design, you need access to an ml.p5e [instance](http://8.136.199.333000). To check 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 circumstances in the AWS Region you are releasing. To request a limitation increase, develop a limitation boost request and connect to your account team.<br>
<br>Because you will be releasing this model with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) approvals to utilize Amazon Bedrock Guardrails. For instructions, see Establish authorizations to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to introduce safeguards, prevent damaging material, and examine designs against key security requirements. You can carry out precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to [examine](https://social.mirrororg.com) user inputs and model actions released on Amazon Bedrock Marketplace and [SageMaker JumpStart](https://git.yharnam.xyz). 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 includes the following actions: 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 out to the model for reasoning. After getting the model's output, another guardrail check is applied. If the [output passes](https://findschools.worldofdentistry.org) this final check, it's returned as the outcome. 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 occurred at the input or output stage. The examples showcased in the following sections show reasoning using this API.<br>
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
<br>Amazon Bedrock Marketplace provides you access to over 100 popular, [archmageriseswiki.com](http://archmageriseswiki.com/index.php/User:SoonDunham98000) emerging, and specialized structure designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:<br>
<br>1. On the Amazon Bedrock console, choose Model catalog under Foundation designs in the navigation pane.
At the time of composing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a [supplier](https://www.jjldaxuezhang.com) and choose the DeepSeek-R1 model.<br>
<br>The design detail page provides important details about the model's abilities, rates structure, and execution standards. You can find detailed usage guidelines, consisting of sample API calls and code snippets for [integration](https://git.markscala.org). The design supports different text generation tasks, consisting of material creation, code generation, and concern answering, using its support finding out optimization and CoT reasoning capabilities.
The page likewise includes release choices and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select Deploy.<br>
<br>You will be prompted to configure the release details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
5. For Number of circumstances, go into a variety of instances (between 1-100).
6. For Instance type, pick your instance type. For optimal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, [it-viking.ch](http://it-viking.ch/index.php/User:ConnieHebert) you can set up advanced security and infrastructure settings, including virtual private cloud (VPC) networking, service role approvals, and file encryption settings. For a lot of utilize cases, the default settings will work well. However, for production deployments, you might desire to evaluate these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to start utilizing the design.<br>
<br>When the implementation is complete, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
8. Choose Open in play area to access an interactive user interface where you can explore different triggers and change design parameters like temperature and maximum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum outcomes. For example, material for inference.<br>
<br>This is an excellent method to explore the design's reasoning and text generation abilities before integrating it into your applications. The play ground provides instant feedback, [assisting](https://smarthr.hk) you comprehend how the design reacts to different inputs and letting you tweak your triggers for optimal results.<br>
<br>You can quickly check the design in the [play ground](https://uniondaocoop.com) 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 inference using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform inference utilizing a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can [produce](http://119.45.195.10615001) 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 developed the guardrail, use the following code to carry out guardrails. The script initializes the bedrock_runtime client, [configures inference](http://hjl.me) criteria, and sends out a request to create 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 services that you can release with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your information, and release them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart offers 2 practical techniques: utilizing the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's explore both methods to assist you choose the technique that finest fits your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps 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 [prompted](https://git.augustogunsch.com) to develop a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The model browser displays available designs, with details like the provider name and model capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card reveals key details, including:<br>
<br>- Model name
- [Provider](https://wamc1950.com) name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if appropriate), indicating that this design can be signed up with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the model card to see the design details page.<br>
<br>The design details page consists of the following details:<br>
<br>- The design name and service provider details.
Deploy button to deploy the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of crucial details, such as:<br>
<br>- Model description.
- License [details](http://git.permaviat.ru).
- Technical requirements.
- Usage guidelines<br>
<br>Before you deploy the model, it's recommended to review the model details and license terms to validate compatibility with your usage case.<br>
<br>6. Choose Deploy to proceed with deployment.<br>
<br>7. For Endpoint name, [utilize](https://cyberbizafrica.com) the immediately produced name or [develop](https://pedulidigital.com) a customized one.
8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the variety of instances (default: 1).
Selecting proper instance types and counts is important for cost and performance optimization. Monitor your release to change these settings as needed.Under Inference type, Real-time inference is selected by default. This is [enhanced](https://iklanbaris.id) for sustained traffic and low latency.
10. Review all setups for precision. For this design, we strongly suggest adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to release the model.<br>
<br>The deployment process can take a number of minutes to complete.<br>
<br>When implementation is total, your endpoint status will alter to InService. At this moment, the model is prepared to accept inference requests through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will show relevant metrics and status details. When the deployment is complete, you can invoke the model utilizing 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 need to set up the [SageMaker Python](https://cyberbizafrica.com) SDK and make certain you have the necessary AWS authorizations and environment setup. The following is a detailed code example that shows how to [release](http://forum.infonzplus.net) and utilize DeepSeek-R1 for inference programmatically. The code for releasing the model is provided in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
<br>You can run extra demands against the predictor:<br>
<br>Implement guardrails and run reasoning with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail utilizing 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, finish the steps in this section to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace implementation<br>
<br>If you released the model using Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace implementations.
2. In the Managed releases section, find the [endpoint](https://ejamii.com) you want to delete.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the appropriate release: 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 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 deploy the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, refer to Use Amazon Bedrock [tooling](http://slfood.co.kr) with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, [disgaeawiki.info](https://disgaeawiki.info/index.php/User:CecilaDalgarno) Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Beginning with Amazon [SageMaker JumpStart](http://106.52.242.1773000).<br>
<br>About the Authors<br>
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging generative [AI](http://124.220.187.142:3000) business build ingenious services utilizing AWS services and accelerated calculate. Currently, he is concentrated on establishing techniques for fine-tuning and optimizing the reasoning performance of big language designs. In his downtime, Vivek delights in hiking, seeing films, and trying various foods.<br>
<br>Niithiyn Vijeaswaran is a [Generative](http://154.209.4.103001) [AI](https://jimsusefultools.com) Specialist Solutions Architect with the [Third-Party Model](https://tobesmart.co.kr) Science group at AWS. His location of focus is AWS [AI](https://www.jobsalert.ai) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](https://www.allclanbattles.com) with the Third-Party Model [Science](https://www.airemploy.co.uk) group at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://rna.link) hub. She is enthusiastic about developing solutions that assist customers accelerate their [AI](https://git.xantxo-coquillard.fr) journey and unlock service worth.<br>