carmeloarroyo
/
h-0sting
1
0
Code Issues Packages Projects Wiki

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

master
Carmelo Arroyo 2025-04-04 09:04:30 +08:00
commit d37da2f90e
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 100644

@ -0,0 +1,93 @@
<br>Today, we are excited to announce that DeepSeek R1 [distilled Llama](http://boiler.ttoslinux.org8888) and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://43.138.236.3:9000)'s first-generation frontier design, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion specifications to develop, experiment, and responsibly scale your generative [AI](http://git.spaceio.xyz) concepts on AWS.<br>
<br>In this post, we show how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to deploy the distilled variations of the designs too.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) developed by DeepSeek [AI](http://47.107.132.138:3000) that utilizes support discovering to boost reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. A key differentiating feature is its support knowing (RL) action, which was used to refine the model's reactions beyond the basic pre-training and tweak process. By integrating RL, DeepSeek-R1 can adapt better to user feedback and goals, eventually enhancing both significance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) approach, meaning it's geared up to break down intricate questions and factor through them in a detailed way. This directed thinking procedure [permits](https://www.fightdynasty.com) the model to produce more precise, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT abilities, aiming to produce structured reactions while concentrating on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has recorded the industry's attention as a flexible text-generation model that can be [integrated](http://1.117.194.11510080) into different workflows such as representatives, rational reasoning and information analysis jobs.<br>
<br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The [MoE architecture](http://121.28.134.382039) permits activation of 37 billion criteria, enabling efficient reasoning by routing questions to the most relevant specialist "clusters." This method enables the model to concentrate on different issue domains while maintaining general effectiveness. DeepSeek-R1 requires 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 release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 model to more efficient architectures based on popular 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 effective designs to imitate the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as an instructor design.<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](http://115.159.107.1173000) in place. In this blog site, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and examine designs against essential security requirements. At the time of composing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can [develop](https://forum.batman.gainedge.org) multiple guardrails tailored to various use cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls across your generative [AI](http://51.79.251.248:8080) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, select Amazon SageMaker, and [validate](http://koreaeducation.co.kr) 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 limit boost, produce a limit boost request and connect to your account team.<br>
<br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For guidelines, see Set up consents to utilize guardrails for [material](https://git.prime.cv) filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to introduce safeguards, avoid [harmful](https://sahabatcasn.com) material, and assess models against essential safety requirements. You can execute security procedures for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to assess user inputs and design actions deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.<br>
<br>The general 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 to the design for reasoning. After receiving the design'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 stepped in by the guardrail, a message is [returned indicating](https://103.1.12.176) the nature of the [intervention](https://www.buzzgate.net) and whether it took place at the input or output stage. The examples showcased in the following areas demonstrate reasoning 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 models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:<br>
<br>1. On the [Amazon Bedrock](https://git.maxwellj.xyz) console, select Model catalog under Foundation designs in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a supplier and pick the DeepSeek-R1 model.<br>
<br>The model detail page [supplies essential](http://123.111.146.2359070) details about the model's abilities, pricing structure, and implementation guidelines. You can discover detailed use directions, consisting of calls and code bits for integration. The model supports [numerous](http://34.81.52.16) text generation tasks, consisting of material production, code generation, and question answering, using its support learning optimization and CoT thinking abilities.
The page also consists of implementation options and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, choose Deploy.<br>
<br>You will be prompted to configure the deployment details for [disgaeawiki.info](https://disgaeawiki.info/index.php/User:DixieHyi0671805) DeepSeek-R1. The model ID will be [pre-populated](http://101.34.228.453000).
4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters).
5. For Variety of instances, enter a variety of circumstances (in between 1-100).
6. For [Instance](https://gitlog.ru) type, select your circumstances type. For optimum efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
Optionally, you can configure innovative security and [infrastructure](https://avpro.cc) settings, consisting of virtual private cloud (VPC) networking, service role consents, and encryption settings. For most use cases, the default settings will work well. However, for production releases, you may want to review these settings to line up with your company's security and [hb9lc.org](https://www.hb9lc.org/wiki/index.php/User:BernardDoolette) compliance requirements.
7. Choose Deploy to start using the model.<br>
<br>When the release is total, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
8. Choose Open in play ground to access an interactive user interface where you can try out various triggers and adjust model specifications like temperature and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimal outcomes. For example, content for reasoning.<br>
<br>This is an excellent way to explore the model's reasoning and text generation capabilities before incorporating it into your applications. The play ground supplies instant feedback, helping you understand how the design reacts to different inputs and letting you tweak your prompts for optimum outcomes.<br>
<br>You can rapidly test the design in the play area through the UI. However, to conjure up the released 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 deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a [guardrail utilizing](https://www.buzzgate.net) the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the [GitHub repo](https://git.jerl.dev). After you have created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning specifications, and sends a request to generate text based upon a user prompt.<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 options that you can deploy with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your data, and deploy them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 practical methods: using the user-friendly SageMaker JumpStart UI or [carrying](http://qiriwe.com) out programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you pick the method that best suits your needs.<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 develop a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
<br>The design internet browser displays available models, with details like the service provider name and model abilities.<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 design card.
Each model card reveals crucial details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
[Bedrock Ready](http://2.47.57.152) badge (if applicable), [indicating](http://182.92.251.553000) that this model can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the model card to view the design details page.<br>
<br>The model details page [consists](https://git.getmind.cn) of the following details:<br>
<br>- The model name and company details.
Deploy button to deploy the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical specifications.
- Usage guidelines<br>
<br>Before you release the design, it's suggested to review the model details and license terms to verify compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with deployment.<br>
<br>7. For Endpoint name, utilize the immediately created name or develop a custom one.
8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the variety of circumstances (default: 1).
Selecting proper circumstances types and counts is important for cost and performance optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, Real-time inference is chosen by [default](https://code.in-planet.net). This is enhanced for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we strongly advise 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 implementation process can take a number of minutes to finish.<br>
<br>When deployment is complete, your endpoint status will change to InService. At this moment, the design is prepared to accept reasoning requests through the endpoint. You can keep track of the release development on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the release is complete, you can invoke the model utilizing a SageMaker runtime customer and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To begin with DeepSeek-R1 [utilizing](http://81.68.246.1736680) the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the essential AWS authorizations 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 supplied in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
<br>You can run extra requests against the predictor:<br>
<br>Implement guardrails and run reasoning 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 create a guardrail using the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
<br>Clean up<br>
<br>To avoid undesirable charges, complete the actions in this area to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you [released](https://git.cloud.exclusive-identity.net) the model utilizing Amazon Bedrock Marketplace, complete the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace deployments.
2. In the Managed implementations section, find the endpoint you wish to erase.
3. Select the endpoint, and on the Actions menu, [choose Delete](https://www.imdipet-project.eu).
4. Verify the endpoint details to make certain you're erasing the right deployment: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you deployed will sustain expenses if you leave it running. Use the following code to erase the endpoint if you want to stop sustaining charges. For more details, see Delete Endpoints and [Resources](http://mpowerstaffing.com).<br>
<br>Conclusion<br>
<br>In this post, we checked out how you can access and deploy the DeepSeek-R1 design using [Bedrock Marketplace](https://alllifesciences.com) and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get going. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, [SageMaker JumpStart](https://epcblind.org) pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Beginning 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://124.223.100.38:3000) companies build innovative options using AWS services and accelerated compute. Currently, he is concentrated on developing methods for fine-tuning and optimizing the inference efficiency of large language designs. In his spare time, Vivek takes pleasure in hiking, seeing motion pictures, and attempting various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://sl860.com) Specialist Solutions [Architect](http://111.61.77.359999) with the [Third-Party Model](https://smarthr.hk) [Science](https://git.thatsverys.us) group at AWS. His area of focus is AWS [AI](https://body-positivity.org) [accelerators](https://wiki.rrtn.org) (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is an Expert Solutions Architect dealing with generative [AI](http://193.9.44.91) 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](https://git.bugwc.com) hub. She is passionate about constructing options that help [clients accelerate](https://www.rotaryjobmarket.com) their [AI](http://13.209.39.139:32421) journey and unlock business value.<br>