rosaurabousque/bluestoneapps
1
0
Code Issues Actions Packages Projects Wiki

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

Rosaura Bousquet 2025-02-07 09:46:20 +09:00
commit 1d378194e3
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](https://mediawiki.hcah.in) [AI](https://www.dutchsportsagency.com)'s first-generation frontier design, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion criteria to build, experiment, and properly scale your generative [AI](https://nakenterprisetv.com) [concepts](https://infinirealm.com) on AWS.<br>
<br>In this post, we demonstrate how to get begun with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled variations of the designs as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) developed by DeepSeek [AI](https://partyandeventjobs.com) that uses reinforcement discovering to enhance thinking abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A crucial differentiating function is its reinforcement knowing (RL) step, which was utilized to improve the design's reactions beyond the standard pre-training and tweak procedure. By integrating RL, DeepSeek-R1 can adapt better to user feedback and objectives, [pediascape.science](https://pediascape.science/wiki/User:ChandaRidenour) eventually boosting both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, implying it's equipped to break down complex questions and factor [larsaluarna.se](http://www.larsaluarna.se/index.php/User:DominiqueCurmi) through them in a detailed way. This guided thinking procedure permits the model to produce more precise, transparent, and detailed answers. This design combines RL-based fine-tuning with CoT abilities, aiming to create structured responses while concentrating on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has recorded the market's attention as a versatile text-generation model that can be integrated into various workflows such as agents, logical reasoning and information analysis tasks.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion [parameters](http://gagetaylor.com) in size. The MoE architecture allows [activation](http://120.79.7.1223000) of 37 billion parameters, enabling efficient inference by routing queries to the most appropriate specialist "clusters." This method permits the model to concentrate on different problem domains while maintaining total efficiency. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for inference. In this post, we will utilize an ml.p5e.48 xlarge instance to deploy the model. ml.p5e.48 xlarge comes with 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](https://gitea.gai-co.com) based upon popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller sized, more efficient designs to simulate the habits and thinking patterns of the larger DeepSeek-R1 model, utilizing it as a teacher model.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or [Bedrock Marketplace](http://awonaesthetic.co.kr). Because DeepSeek-R1 is an [emerging](https://chhng.com) model, we recommend releasing this design with guardrails in location. In this blog site, we will utilize Amazon Bedrock [Guardrails](https://testgitea.cldevops.de) to present safeguards, avoid damaging material, and examine designs against crucial security criteria. At the time of composing this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing safety controls across your generative [AI](http://git.scraperwall.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, you need access to an ml.p5e instance. To inspect if you have quotas for P5e, open the Service Quotas [console](https://armconnection.com) and under AWS Services, select Amazon SageMaker, and verify you're [utilizing](http://59.56.92.3413000) ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are deploying. To request a limitation boost, produce a limit increase demand and reach out to your account group.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For guidelines, see Establish permissions 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 hazardous material, and assess designs against essential security criteria. You can carry out precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to assess user inputs and design actions released 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 create the guardrail, see the GitHub repo.<br>
<br>The basic circulation includes the following actions: 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 reasoning. After receiving the design's output, another [guardrail check](https://nbc.co.uk) is applied. If the output passes this final check, it's returned as the final outcome. However, if either the input or output is stepped in by the guardrail, a message is [returned suggesting](https://tube.denthubs.com) the nature of the intervention and whether it happened at the input or output stage. The examples showcased in the following areas demonstrate reasoning [utilizing](https://tj.kbsu.ru) 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 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, [demo.qkseo.in](http://demo.qkseo.in/profile.php?id=995691) select 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 model. It does not [support Converse](https://loveyou.az) APIs and other Amazon Bedrock [tooling](http://8.140.200.2363000).
2. Filter for DeepSeek as a [supplier](https://www.viewtubs.com) and select the DeepSeek-R1 model.<br>
<br>The design detail page supplies necessary details about the design's abilities, prices structure, and execution guidelines. You can find detailed use directions, including sample API calls and code bits for integration. The model supports various text generation jobs, consisting of content development, code generation, and concern answering, utilizing its support finding out optimization and CoT thinking abilities.
The page likewise consists of implementation choices and licensing details to help you start with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select Deploy.<br>
<br>You will be triggered to set up the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
5. For Variety of instances, get in a variety of instances (in between 1-100).
6. For example type, select your instance type. For ideal performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, you can configure sophisticated security and infrastructure settings, including virtual [personal cloud](https://git.esc-plus.com) (VPC) networking, service role approvals, and file encryption settings. For a lot of use cases, the default settings will work well. However, for production deployments, you may want to examine these settings to align with your [company's security](http://ieye.xyz5080) and compliance requirements.
7. Choose Deploy to begin utilizing the design.<br>
<br>When the implementation is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
8. Choose Open in play ground to access an interactive interface where you can explore various triggers and adjust design 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 outcomes. For instance, material for reasoning.<br>
<br>This is an excellent way to explore the design's thinking and text generation capabilities before incorporating it into your applications. The playground supplies instant feedback, assisting you comprehend how the design reacts to numerous inputs and letting you fine-tune your triggers for optimum outcomes.<br>
<br>You can quickly check the design in the play area through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you [require](http://8.137.85.1813000) to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform reasoning using a deployed DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can create 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 [produced](https://tjoobloom.com) the guardrail, use the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning specifications, and sends out a demand to create text based on a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, built-in algorithms, and prebuilt ML options that you can release with simply a few 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 uses 2 convenient methods: utilizing the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's explore both approaches to assist you pick the technique that best matches your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps to deploy DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the SageMaker console, [wiki.whenparked.com](https://wiki.whenparked.com/User:AudryMarcell) pick Studio in the pane.
2. First-time users will be prompted to produce a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The design browser shows available designs, with details like the service provider name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each model card shows key details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if relevant), indicating that this model can be registered with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the model<br>
<br>5. Choose the design card to see the design details page.<br>
<br>The model details page consists of the following details:<br>
<br>- The model 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 essential details, such as:<br>
<br>- Model description.
- License details.
- Technical specs.
- Usage standards<br>
<br>Before you deploy the model, it's suggested to examine the model details and license terms to validate compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with release.<br>
<br>7. For [mediawiki.hcah.in](https://mediawiki.hcah.in/index.php?title=User:RandellKenney) Endpoint name, utilize the immediately generated name or create a custom-made one.
8. For Instance type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the variety of [instances](https://gitlab.interjinn.com) (default: 1).
Selecting suitable instance types and counts is important for cost and efficiency optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time reasoning is selected by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for accuracy. For this model, we highly recommend adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the model.<br>
<br>The deployment process can take a number of minutes to finish.<br>
<br>When deployment is total, your endpoint status will alter to InService. At this point, the design is all set to accept reasoning demands through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will display pertinent metrics and [garagesale.es](https://www.garagesale.es/author/chandaleong/) status details. When the implementation is complete, you can conjure up the model using a SageMaker runtime client and integrate 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 need to install the SageMaker Python SDK and make certain you have the required AWS approvals and environment setup. The following is a detailed code example that demonstrates how to release and use DeepSeek-R1 for reasoning programmatically. The code for releasing the model is provided in the Github here. You can clone the notebook and range from [SageMaker Studio](https://ari-sound.aurumai.io).<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 use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail using the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To avoid unwanted charges, finish the actions in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you released the model 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 releases](https://zenabifair.com) area, locate the endpoint you desire to erase.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you're deleting the right implementation: 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 expenses if you leave it running. Use the following code to delete the endpoint if you want 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 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting 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](http://115.238.48.210:9015) business build ingenious solutions utilizing AWS services and sped up compute. Currently, he is concentrated on establishing strategies for fine-tuning and optimizing the [reasoning performance](http://ledok.cn3000) of big language designs. In his spare time, Vivek takes pleasure in hiking, enjoying motion pictures, and attempting different foods.<br>
<br>[Niithiyn Vijeaswaran](https://gitlab-heg.sh1.hidora.com) is a Generative [AI](https://astonvillafansclub.com) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His location of focus is AWS [AI](http://170.187.182.121:3000) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a [Professional](https://git.fpghoti.com) Solutions Architect working on generative [AI](https://999vv.xyz) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](http://47.103.108.26:3000) center. She is passionate about constructing solutions that help clients accelerate their [AI](https://empleos.dilimport.com) journey and unlock service worth.<br>