susannahbeesto
/
hcah
1
0
Code Issues Packages Projects Wiki

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

Susannah Beeston 2025-03-06 17:10:41 +08:00
commit 443b403a49
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 reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon [Bedrock Marketplace](https://pittsburghtribune.org) and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://1.214.207.44:10333)'s first-generation frontier model, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion specifications to construct, experiment, and responsibly scale your generative [AI](https://10mektep-ns.edu.kz) [concepts](https://gitlab.steamos.cloud) on AWS.<br>
<br>In this post, we show how to get started with DeepSeek-R1 on Amazon Bedrock Marketplace and [SageMaker JumpStart](http://gs1media.oliot.org). You can follow similar steps to release the distilled variations of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://munidigital.iie.cl) that utilizes reinforcement discovering to boost reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A crucial differentiating feature is its support learning (RL) action, which was [utilized](https://twitemedia.com) to improve the design's actions 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 employs a chain-of-thought (CoT) approach, suggesting it's geared up to break down complex queries and reason through them in a detailed way. This [directed thinking](http://careers.egylifts.com) procedure permits the model to produce more precise, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT capabilities, aiming to generate structured actions while concentrating on [interpretability](https://career.finixia.in) and user interaction. With its comprehensive capabilities DeepSeek-R1 has actually recorded the market's attention as a flexible text-generation model that can be incorporated into various workflows such as agents, [larsaluarna.se](http://www.larsaluarna.se/index.php/User:DarinGallegos) rational thinking and data analysis tasks.<br>
<br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The [MoE architecture](https://praca.e-logistyka.pl) permits activation of 37 billion parameters, enabling [effective inference](http://39.105.128.46) by routing queries to the most [relevant specialist](https://git.k8sutv.it.ntnu.no) "clusters." This method permits the model to specialize in various issue domains while maintaining general performance. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 [xlarge instance](http://okna-samara.com.ru) to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 design to more effective 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 effective models to imitate the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as an instructor design.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we [advise releasing](http://175.25.51.903000) this model with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging content, and evaluate designs against essential security criteria. At the time of writing this blog, 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 usage cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative [AI](https://sportsprojobs.net) applications.<br>
<br>Prerequisites<br>
<br>To deploy 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, pick 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 instance in the AWS Region you are releasing. To request a limitation increase, create a [limitation boost](https://kurva.su) 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) consents to use Amazon Bedrock Guardrails. For directions, see Set up approvals to use guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails permits you to introduce safeguards, avoid hazardous content, and assess designs against crucial safety requirements. You can carry out precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and model responses 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 produce 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 to the design for inference. After getting the design's output, another [guardrail check](https://gigsonline.co.za) is used. If the [output passes](https://git.perrocarril.com) this final check, it's [returned](https://1millionjobsmw.com) as the last result. However, if either the input or output is intervened by the guardrail, a message is returned suggesting the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following areas show inference utilizing 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, total the following actions:<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 use the InvokeModel API to conjure up the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and select the DeepSeek-R1 model.<br>
<br>The model detail page provides important details about the design's capabilities, pricing structure, and execution guidelines. You can discover detailed usage directions, including sample API calls and code bits for combination. The design supports various text generation tasks, consisting of material production, code generation, and question answering, utilizing its reinforcement learning optimization and CoT reasoning abilities.
The page also consists of deployment options and licensing details to help you start with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, pick Deploy.<br>
<br>You will be triggered to configure the release details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Number of circumstances, go into a number of circumstances (between 1-100).
6. For example type, pick your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
Optionally, you can configure innovative security and facilities settings, including virtual private cloud (VPC) networking, service role permissions, and encryption settings. For many use cases, the default settings will work well. However, for production deployments, you may wish to examine these settings to align with your organization's security and [compliance](https://huconnect.org) requirements.
7. Choose Deploy to begin utilizing the design.<br>
<br>When the release is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
8. Choose Open in play area to access an interactive interface where you can experiment with different triggers 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 excellent method to explore the design's reasoning and text generation capabilities before integrating it into your applications. The play ground supplies instant feedback, assisting you comprehend how the [model reacts](http://www.c-n-s.co.kr) to various inputs and letting you fine-tune your prompts for optimum results.<br>
<br>You can rapidly evaluate the design in the play ground through the UI. However, to conjure up the deployed model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to carry out inference utilizing a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. 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. After you have actually created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning specifications, and sends a demand to generate text based upon a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and [prebuilt](http://grainfather.co.uk) ML options that you can deploy with just a few 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 design through SageMaker JumpStart provides two hassle-free methods: using the intuitive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you select the technique that best matches your requirements.<br>
<br>Deploy DeepSeek-R1 through [SageMaker JumpStart](https://geoffroy-berry.fr) UI<br>
<br>Complete the following steps to deploy DeepSeek-R1 [utilizing SageMaker](https://aloshigoto.jp) JumpStart:<br>
<br>1. On the SageMaker console, select Studio in the navigation 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 model web browser displays available designs, with [details](https://mypocket.cloud) like the company name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card shows crucial details, including:<br>
<br>- Model name
- Provider name
- Task category (for example, Text Generation).
Bedrock Ready badge (if applicable), showing that this design can be signed up with Amazon Bedrock, [enabling](http://121.41.31.1463000) you to use Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the model card to view the model 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 model.
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 [requirements](https://hylpress.net).
- Usage guidelines<br>
<br>Before you release the design, it's recommended to review the design details and license terms to confirm compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with release.<br>
<br>7. For Endpoint name, use the instantly produced name or develop a customized one.
8. For example type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, get in the number of circumstances (default: 1).
Selecting appropriate instance types and counts is crucial for cost and efficiency optimization. Monitor your deployment to change these [settings](https://git.cloudtui.com) as needed.Under Inference type, Real-time inference 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 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 release process can take numerous minutes to complete.<br>
<br>When release is total, your endpoint status will change to InService. At this moment, the model is prepared to accept reasoning requests through the endpoint. You can keep an eye on the release development on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the implementation is total, you can invoke the design using a SageMaker runtime customer and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To get begun with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the essential AWS authorizations and environment setup. The following is a detailed code example that shows how to deploy and use DeepSeek-R1 for inference programmatically. The code for deploying the model is offered 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 inference with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To avoid undesirable charges, complete the steps in this section to tidy 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 actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, choose Marketplace deployments.
2. In the [Managed releases](http://kousokuwiki.org) area, locate the endpoint you want to erase.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're deleting the right 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 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 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in [SageMaker Studio](https://1.214.207.4410333) 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](https://www.myjobsghana.com) Marketplace, and Getting going 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](https://cariere.depozitulmax.ro) generative [AI](https://vidhiveapp.com) business develop ingenious solutions utilizing AWS services and sped up [calculate](https://git.collincahill.dev). Currently, he is focused on developing methods for fine-tuning and enhancing the inference performance of large language models. In his downtime, Vivek enjoys hiking, watching films, and attempting different cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://sahabatcasn.com) Specialist Solutions [Architect](http://plethe.com) with the Third-Party [Model Science](https://maibuzz.com) team at AWS. His area of focus is AWS [AI](https://lovelynarratives.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect dealing with generative [AI](https://video.disneyemployees.net) with the Third-Party Model Science group at AWS.<br>
<br>[Banu Nagasundaram](https://tube.leadstrium.com) leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial [intelligence](https://samman-co.com) and generative [AI](http://161.97.176.30) center. She is enthusiastic about constructing options that help clients accelerate their [AI](https://89.22.113.100) journey and unlock business value.<br>