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

2025-04-12 03:45:24 +08:00 · 2025-04-12 03:45:24 +08:00 · 828bfb4fb0
commit 828bfb4fb0
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are delighted to reveal 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://lab.gvid.tv)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative [AI](https://usvs.ms) concepts on AWS.<br>
 <br>In this post, we demonstrate how to begin with DeepSeek-R1 on Amazon Bedrock [Marketplace](http://ods.ranker.pub) and SageMaker JumpStart. You can follow similar steps to release 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](https://fototik.com) that utilizes support finding out to improve thinking abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key differentiating function is its support learning (RL) step, which was utilized to refine the model's reactions beyond the [standard pre-training](https://git.biosens.rs) and tweak procedure. By [including](https://gitea.itskp-odense.dk) RL, DeepSeek-R1 can adapt better to user feedback and objectives, eventually enhancing both importance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, implying it's geared up to break down complicated inquiries and factor through them in a detailed way. This directed reasoning procedure enables the design to produce more precise, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured [actions](https://gitea.dokm.xyz) while [concentrating](https://39.105.45.141) 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 incorporated into different workflows such as agents, logical thinking and information 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 specifications, making it possible for effective inference by routing queries to the most relevant expert "clusters." This approach enables the design to concentrate on different problem 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 use an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the [reasoning capabilities](https://www.beyoncetube.com) 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 describes a process of training smaller, more effective models to simulate the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as a teacher design.<br>
 <br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend releasing this model with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid harmful content, and assess models against essential safety [criteria](https://meeting2up.it). At the time of writing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the [ApplyGuardrail API](http://39.101.167.1953003). You can create numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative [AI](http://82.157.11.224:3000) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you require access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and confirm you're utilizing ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the [AWS Region](http://christianpedia.com) you are deploying. To request a limitation increase,  [it-viking.ch](http://it-viking.ch/index.php/User:ElveraSneddon9) develop a limit increase request and reach out to your account group.<br>
 <br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) authorizations to utilize Amazon Bedrock Guardrails. For guidelines, see Set up approvals to use guardrails for material filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br> Guardrails enables you to introduce safeguards, prevent damaging material, and examine designs against crucial security requirements. You can carry out safety procedures for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to evaluate user inputs and model reactions released on [Amazon Bedrock](https://www.ntcinfo.org) Marketplace and SageMaker JumpStart. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo.<br>
 <br>The general circulation involves the following actions: First,  [wiki.myamens.com](http://wiki.myamens.com/index.php/User:ChanaWroe521668) the system gets 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 model for [inference](https://atfal.tv). After receiving the design's output, another guardrail check is applied. If the output passes this final check, it's returned as the result. However, if either the input or output is stepped in by the guardrail, a [message](https://git.watchmenclan.com) is [returned indicating](https://jobs.360career.org) the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following sections demonstrate 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 actions:<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](https://git.protokolla.fi) APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a company and select the DeepSeek-R1 design.<br>
 <br>The model detail page provides essential details about the [design's](https://soehoe.id) abilities, prices structure, and execution guidelines. You can discover detailed use instructions, consisting of [sample API](https://bertlierecruitment.co.za) calls and code bits for integration. The model supports numerous text generation tasks, [including](https://seconddialog.com) content development, code generation, and concern answering, using its reinforcement discovering optimization and CoT thinking abilities.
 The page likewise includes release options and licensing details to help you start with DeepSeek-R1 in your applications.
 3. To begin using DeepSeek-R1, choose Deploy.<br>
 <br>You will be triggered to configure the deployment details for  [archmageriseswiki.com](http://archmageriseswiki.com/index.php/User:LeandraKrichauff) DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, enter an endpoint name (in between 1-50 [alphanumeric](https://dsspace.co.kr) characters).
 5. For Variety of instances, go into a number of circumstances (between 1-100).
 6. For example 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 settings, including virtual private cloud (VPC) networking, service function approvals, and file encryption settings. For many utilize cases, the default settings will work well. However, for production deployments, you may desire to evaluate these settings to line up with your company's security and compliance requirements.
 7. Choose Deploy to start using the design.<br>
 <br>When the deployment is complete, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
 8. Choose Open in play ground to access an interactive 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 design template for optimal results. For instance, content for reasoning.<br>
 <br>This is an excellent method to check out the design's reasoning and text generation capabilities before integrating it into your applications. The play ground offers immediate feedback, helping you understand how the model reacts to numerous inputs and letting you fine-tune your prompts for optimal 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 to get the endpoint ARN.<br>
 <br>Run inference using guardrails with the released DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to perform inference utilizing a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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 created the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, sets up inference specifications, and sends a demand 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) center with FMs, integrated algorithms, and prebuilt ML solutions that you can deploy with just a couple of clicks. With [SageMaker](http://47.106.228.1133000) JumpStart, you can tailor pre-trained models to your use case, with your data, and deploy them into production using either the UI or  [forum.altaycoins.com](http://forum.altaycoins.com/profile.php?id=1099984) SDK.<br>
 <br>Deploying DeepSeek-R1 design through SageMaker JumpStart provides 2 hassle-free techniques: utilizing the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both methods to assist you pick the technique that best fits 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, select Studio in the navigation pane.
 2. First-time users will be [prompted](http://8.140.244.22410880) to [develop](http://www5a.biglobe.ne.jp) a domain.
 3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
 <br>The model browser shows available designs, with details like the supplier name and model capabilities.<br>
 <br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card.
 Each design card shows essential details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task category (for example,  [trademarketclassifieds.com](https://trademarketclassifieds.com/user/profile/2672496) Text Generation).
 [Bedrock Ready](http://119.45.49.2123000) badge (if relevant), showing that this model can be registered with Amazon Bedrock, enabling you to utilize Amazon Bedrock APIs to invoke the model<br>
 <br>5. Choose the design card to see the model 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 model.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab includes crucial details, such as:<br>
 <br>- Model description.
 - License [details](http://shenjj.xyz3000).
 - Technical specs.
 - Usage standards<br>
 <br>Before you release the design, it's advised to review the model details and license terms to validate compatibility with your use case.<br>
 <br>6. Choose Deploy to continue with release.<br>
 <br>7. For Endpoint name, use the immediately generated name or develop a custom-made one.
 8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, get in the number of circumstances (default: 1).
 Selecting suitable circumstances types and counts is crucial for cost and efficiency optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time inference is picked by default. This is optimized for sustained traffic and low latency.
 10. Review all configurations for accuracy. For this design, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
 11. Choose Deploy to release the design.<br>
 <br>The implementation process can take numerous minutes to finish.<br>
 <br>When implementation is total, your endpoint status will change to InService. At this moment, the design is prepared to accept inference requests through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the release is total, you can invoke the design utilizing a SageMaker runtime customer and integrate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To start with DeepSeek-R1 using 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 demonstrates how to deploy and use DeepSeek-R1 for inference programmatically. The code for releasing the model is provided in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
 <br>You can run additional 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 use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail using the Amazon Bedrock console or the API, and implement it as shown in the following code:<br>
 <br>Tidy up<br>
 <br>To avoid undesirable charges, complete the actions in this section to tidy up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you released the design 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](https://property.listatto.ca) releases.
 2. In the Managed deployments section, find 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 deleting the proper release: 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 costs 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 explored how you can access and deploy the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, [Amazon Bedrock](http://jobshut.org) Marketplace, and Starting with Amazon SageMaker JumpStart.<br>
 <br>About the Authors<br>
 <br>[Vivek Gangasani](http://118.89.58.193000) is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative [AI](http://worldwidefoodsupplyinc.com) business build [innovative solutions](http://175.178.153.226) utilizing AWS services and accelerated compute. Currently, he is focused on developing strategies for  [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:OrvilleSalvado0) fine-tuning and enhancing the inference efficiency of big language models. In his spare time, Vivek delights in treking, watching motion pictures, and attempting different foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://dreamcorpsllc.com) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](http://test.wefanbot.com:3000) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](http://122.51.230.86:3000) 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://thesecurityexchange.com) center. She is enthusiastic about constructing solutions that help customers [accelerate](https://www.hi-kl.com) their [AI](https://www.punajuaj.com) journey and unlock service value.<br>