erickmceacharn
/
yezhem
1
0
Code Issues Packages Projects Wiki

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

Erick McEacharn 2025-02-20 10:10:57 +08:00
commit f59302bd73
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](https://gogocambo.com) JumpStart. With this launch, you can now release DeepSeek [AI](https://www.webthemes.ca)'s first-generation frontier model, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion specifications to develop, experiment, and properly scale your generative [AI](https://www.imf1fan.com) ideas on AWS.<br>
<br>In this post, we demonstrate how to get started with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to deploy the distilled variations of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) established by [DeepSeek](http://47.110.248.4313000) [AI](https://bnsgh.com) that uses reinforcement learning to boost reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. A key identifying function is its support learning (RL) action, which was utilized to improve the model's responses beyond the basic pre-training and fine-tuning process. By integrating RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately boosting both significance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, implying it's geared up to break down complicated queries and factor through them in a detailed way. This directed reasoning [process](http://192.241.211.111) allows the design to produce more precise, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT abilities, aiming to generate structured reactions while concentrating on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has actually captured the industry's attention as a flexible text-generation design that can be integrated into numerous workflows such as agents, sensible thinking and data interpretation jobs.<br>
<br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture allows activation of 37 billion criteria, allowing effective inference by routing inquiries to the most appropriate professional "clusters." This technique permits the model to concentrate on different issue domains while maintaining total 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 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the reasoning capabilities of the main R1 design to more efficient architectures based on popular open [designs](https://rhcstaffing.com) like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller sized, [pipewiki.org](https://pipewiki.org/wiki/index.php/User:LatashaI90) more effective models to mimic the habits and thinking patterns of the larger DeepSeek-R1 model, using it as an instructor design.<br>
<br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend releasing this design with [guardrails](http://114.55.54.523000) in place. In this blog, we will use Amazon Bedrock Guardrails to present safeguards, avoid hazardous content, and examine models against key security criteria. At the time of composing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails [supports](https://mxlinkin.mimeld.com) only the ApplyGuardrail API. You can create several guardrails tailored to various use cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing security controls across your generative [AI](https://gitea.easio-com.com) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 model, you need access to an ml.p5e instance. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and [confirm](https://www.50seconds.com) you're using ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To ask for a limitation increase, [develop](https://www.ejobsboard.com) a limitation increase request and [connect](https://gogs.rg.net) to your account group.<br>
<br>Because you will be [deploying](https://pennswoodsclassifieds.com) this design with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) consents to utilize Amazon Bedrock Guardrails. For directions, see Establish authorizations to utilize guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to present safeguards, prevent hazardous content, and evaluate models against key security criteria. You can carry out precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to assess user inputs and design reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
<br>The basic circulation includes the following steps: First, the system receives 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 inference. After receiving the model's output, another guardrail check is used. If the output passes this final check, it's returned as the outcome. However, if either the input or output is [intervened](https://neejobs.com) by the guardrail, a message is returned indicating the nature of the intervention and whether it happened at the input or [output stage](https://jobs.campus-party.org). 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 gives 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, pick Model catalog under Foundation designs in the navigation pane.
At the time of composing 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 pick the DeepSeek-R1 design.<br>
<br>The model detail page supplies vital details about the [model's](https://circassianweb.com) abilities, prices structure, and application guidelines. You can find detailed usage instructions, [including sample](http://euhope.com) API calls and code snippets for combination. The design supports various text generation jobs, including content creation, code generation, and question answering, using its reinforcement finding out optimization and CoT thinking capabilities.
The page likewise consists of release choices and [licensing](http://it-viking.ch) details to help you get started with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, choose Deploy.<br>
<br>You will be prompted to set up the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
5. For Variety of circumstances, enter a number of instances (between 1-100).
6. For Instance type, pick your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is [recommended](http://82.157.11.2243000).
Optionally, you can configure advanced security and facilities settings, consisting of virtual personal cloud (VPC) networking, service function authorizations, and encryption settings. For many use cases, the default settings will work well. However, for production deployments, you may wish to evaluate these settings to line up with your organization's security and [89u89.com](https://www.89u89.com/author/maniegillin/) compliance requirements.
7. Choose Deploy to begin utilizing the model.<br>
<br>When the deployment is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock playground.
8. Choose Open in play ground to access an interactive interface where you can explore various prompts and adjust design specifications 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 instance, content for inference.<br>
<br>This is an exceptional method to check out the model's reasoning and text generation abilities before incorporating it into your applications. The play area provides instant feedback, [assisting](https://interconnectionpeople.se) you comprehend how the model reacts to various inputs and letting you fine-tune your prompts for optimal results.<br>
<br>You can quickly test the design in the play area through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference using guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to carry out inference utilizing a released DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock [console](https://insta.tel) or the API. For the example code to develop the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to carry out guardrails. The script initializes the bedrock_runtime client, configures reasoning specifications, and sends out a demand to produce text based upon a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, built-in algorithms, and prebuilt ML solutions that you can release with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your information, and release them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart offers two hassle-free techniques: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's explore both techniques to help you pick the [technique](https://suomalainennaikki.com) that finest matches your requirements.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps to release 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 to develop a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The model web browser shows available models, with details like the service provider name and model capabilities.<br>
<br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card.
Each design card reveals key details, consisting of:<br>
<br>- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if suitable), indicating that this design can be signed up with Amazon Bedrock, [enabling](https://bolsadetrabajo.tresesenta.mx) you to utilize Amazon Bedrock APIs to conjure up the model<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 model name and company details.
Deploy button to deploy the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab includes crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical specifications.
[- Usage](http://124.220.187.1423000) guidelines<br>
<br>Before you deploy the model, it's recommended to review the design details and license terms to confirm compatibility with your use case.<br>
<br>6. Choose Deploy to continue with implementation.<br>
<br>7. For [Endpoint](https://abileneguntrader.com) name, use the automatically created name or develop a custom-made one.
8. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the number of circumstances (default: 1).
Selecting proper circumstances types and counts is crucial for cost and efficiency optimization. Monitor your release to change these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is optimized for sustained traffic and low latency.
10. Review all setups for precision. For this model, we strongly recommend sticking to SageMaker JumpStart default settings and making certain that network isolation remains in place.
11. Choose Deploy to deploy the design.<br>
<br>The deployment procedure can take numerous minutes to complete.<br>
<br>When release is complete, your [endpoint status](https://interconnectionpeople.se) will alter to InService. At this moment, the design is prepared to accept reasoning requests through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will show appropriate [metrics](https://canworkers.ca) and status details. When the implementation is total, you can [conjure](https://gitea.daysofourlives.cn11443) up the model using a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To begin with DeepSeek-R1 utilizing the [SageMaker Python](https://europlus.us) SDK, you will need to install the SageMaker Python SDK and make certain you have the required AWS consents and environment setup. The following is a [detailed](http://git.bplt.ru) code example that shows how to deploy and utilize DeepSeek-R1 for inference programmatically. The code for deploying the design is offered in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
<br>You can run additional requests against the predictor:<br>
<br>Implement guardrails and run reasoning with your [SageMaker JumpStart](https://ivebo.co.uk) predictor<br>
<br>Similar to Amazon Bedrock, you can likewise use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail using the Amazon Bedrock [console](http://szfinest.com6060) or the API, and execute it as shown in the following code:<br>
<br>Tidy up<br>
<br>To avoid unwanted charges, complete the [actions](https://aggm.bz) in this section to clean up your [resources](https://www.hammerloop.com).<br>
<br>Delete the Amazon Bedrock [Marketplace](http://ptube.site) implementation<br>
<br>If you released the design utilizing Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, choose Marketplace [implementations](https://www.istorya.net).
2. In the Managed implementations section, locate the endpoint you desire to delete.
3. Select the endpoint, and on the Actions menu, choose 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 deployed will sustain costs if you leave it running. Use the following code to erase the endpoint if you wish to stop sustaining charges. For [garagesale.es](https://www.garagesale.es/author/toshahammon/) 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 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to start. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting begun 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](https://www.egomiliinteriors.com.ng) companies develop ingenious options utilizing AWS [services](https://blablasell.com) and sped up compute. Currently, he is focused on establishing methods for fine-tuning and optimizing the inference efficiency of big language models. In his leisure time, Vivek delights in hiking, viewing movies, and trying different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://118.89.58.19:3000) Specialist Solutions Architect with the Third-Party Model [Science](http://www.withsafety.net) group at AWS. His area of focus is AWS [AI](https://virnal.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Professional Solutions Architect dealing with [generative](https://social.web2rise.com) [AI](https://daeshintravel.com) 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](https://awaz.cc) hub. She is enthusiastic about developing solutions that help consumers accelerate their [AI](http://148.66.10.10:3000) journey and unlock service value.<br>