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

2025-05-29 22:12:09 +08:00 · 2025-05-29 22:12:09 +08:00 · 1c43aea02d
commit 1c43aea02d
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are excited to announce that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](http://git.eyesee8.com)'s first-generation [frontier](https://git.haowumc.com) model, DeepSeek-R1, along with the distilled variations varying from 1.5 to 70 billion specifications to develop, experiment, and responsibly scale your  [AI](https://gitea.nafithit.com) ideas on AWS.<br>
 <br>In this post, we demonstrate how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can [follow comparable](https://iamtube.jp) steps to deploy the distilled versions of the models as well.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) established by DeepSeek [AI](http://94.191.100.41) that uses reinforcement learning to improve reasoning capabilities through a multi-stage training [process](http://git.taokeapp.net3000) from a DeepSeek-V3-Base foundation. An essential distinguishing function is its support learning (RL) action, which was used to fine-tune the design's reactions beyond the basic pre-training and fine-tuning procedure. By integrating RL, DeepSeek-R1 can adapt more effectively to user feedback and goals, ultimately improving both relevance and clearness. In addition, DeepSeek-R1 [employs](https://atomouniversal.com.br) a chain-of-thought (CoT) method, suggesting it's geared up to break down intricate questions and factor through them in a detailed manner. This assisted [reasoning process](http://202.164.44.2463000) permits the design to [produce](http://www.dahengsi.com30002) more accurate, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured actions while focusing on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has recorded the market's attention as a versatile text-generation model that can be incorporated into various [workflows](http://47.108.94.35) such as agents, logical thinking and data interpretation tasks.<br>
 <br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion parameters, enabling effective reasoning by routing questions to the most pertinent specialist "clusters." This method allows the design to focus on various problem domains while maintaining general effectiveness. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge circumstances to release the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the thinking [capabilities](https://git.aionnect.com) of the main R1 design to more effective architectures based upon [popular](https://git.jzcscw.cn) 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 models to imitate the behavior and reasoning patterns of the larger DeepSeek-R1 model, utilizing it as a teacher design.<br>
 <br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest deploying this model with guardrails in place. In this blog site, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous content, and examine designs against crucial safety requirements. At the time of composing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create [numerous guardrails](http://120.24.186.633000) [tailored](http://git.medtap.cn) to different usage cases and use them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls throughout your generative [AI](https://se.mathematik.uni-marburg.de) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you require 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 validate you're utilizing ml.p5e.48 xlarge for [endpoint](https://git.alenygam.com) use. Make certain that you have at least one ml.P5e.48 [xlarge circumstances](https://spudz.org) in the AWS Region you are releasing. To ask for a limitation boost, create a limitation boost request and connect to your account group.<br>
 <br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) approvals to utilize Amazon Bedrock Guardrails. For instructions, see Set up authorizations to use guardrails for content filtering.<br>
 <br>[Implementing guardrails](http://133.242.131.2263003) with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails permits you to introduce safeguards, prevent damaging material, and examine models against key security requirements. You can carry out precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to evaluate user inputs and [design reactions](https://gitlab.optitable.com) [deployed](https://git.serenetia.com) 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 flow 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 model for reasoning. After receiving the model's output, another guardrail check is used. If the output passes this final check, it's returned as the final result. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the intervention and whether it took place at the input or output phase. The examples showcased in the following areas show reasoning utilizing this API.<br>
 <br>Deploy DeepSeek-R1 in [Amazon Bedrock](https://e-gitlab.isyscore.com) Marketplace<br>
 <br>Amazon Bedrock Marketplace gives 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 steps:<br>
 <br>1. On the Amazon Bedrock console, select Model brochure under Foundation designs 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 APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a provider and pick the DeepSeek-R1 design.<br>
 <br>The design detail page offers vital details about the [design's](http://president-park.co.kr) capabilities, rates structure, and execution guidelines. You can discover detailed usage instructions, consisting of sample API calls and code bits for combination. The model supports numerous text [generation](http://git.sdkj001.cn) jobs, including material creation, code generation, and question answering, using its reinforcement discovering optimization and CoT reasoning abilities.
 The page also includes implementation options and licensing details to assist you get going with DeepSeek-R1 in your applications.
 3. To begin utilizing DeepSeek-R1, select Deploy.<br>
 <br>You will be triggered to set up the release details for DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
 5. For Variety of instances, go into a number of circumstances (in between 1-100).
 6. For Instance type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised.
 Optionally, you can set up [advanced security](https://zenabifair.com) and infrastructure settings, consisting of virtual private cloud (VPC) networking, service function consents, and file encryption settings. For many utilize cases, the [default settings](https://castingnotices.com) will work well. However, for production deployments, you may want to examine these settings to line up with your organization's security and compliance requirements.
 7. Choose Deploy to begin [utilizing](https://3srecruitment.com.au) the design.<br>
 <br>When the implementation is total, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
 8. Choose Open in play ground to access an interactive user interface where you can explore various triggers and adjust design specifications like temperature level and optimum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal results. For example, material for reasoning.<br>
 <br>This is an excellent method to explore the model's thinking and text generation capabilities before integrating it into your applications. The playground offers instant feedback, helping you understand how the design responds to different inputs and letting you fine-tune your prompts for optimal results.<br>
 <br>You can quickly evaluate the model in the playground through the UI. However, to invoke the deployed model programmatically with any [Amazon Bedrock](https://kryza.network) APIs, you require to get the [endpoint ARN](https://labz.biz).<br>
 <br>Run reasoning using guardrails with the released DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to perform inference utilizing 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 develop the guardrail, see the GitHub repo. After you have actually produced the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, sets up inference parameters, and sends a demand to [produce text](http://116.63.157.38418) based on a user prompt.<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 model through SageMaker JumpStart offers 2 [convenient](https://gitea.dgov.io) approaches: using the user-friendly SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both approaches to help you choose the approach that best fits your needs.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following steps 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 prompted to produce a domain.
 3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
 <br>The design browser displays available models, with [details](https://work-ofie.com) like the provider name and model abilities.<br>
 <br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 model card.
 Each design card reveals crucial details, including:<br>
 <br>- Model name
 - Provider name
 - Task classification (for instance, Text Generation).
 Bedrock Ready badge (if suitable), showing that this model can be registered with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to invoke the model<br>
 <br>5. Choose the model card to view the model details page.<br>
 <br>The model details page includes the following details:<br>
 <br>- The model name and provider details.
 Deploy button to deploy the model.
 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 requirements.
 - Usage standards<br>
 <br>Before you release the model,  [higgledy-piggledy.xyz](https://higgledy-piggledy.xyz/index.php/User:ChetBrauer26) it's advised to review the [model details](http://165.22.249.528888) 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 created name or produce a custom-made one.
 8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, get in the number of circumstances (default: 1).
 Selecting proper instance types and counts is vital for cost and performance optimization. Monitor your release to adjust these settings as needed.Under Inference type, [Real-time reasoning](http://106.52.126.963000) is chosen by default. This is optimized for sustained traffic and low latency.
 10. Review all setups for precision. For this model, we highly advise 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 [implementation procedure](http://hitq.segen.co.kr) can take numerous minutes to finish.<br>
 <br>When implementation is total, your endpoint status will change to InService. At this moment, the model is all set to accept inference requests through the endpoint. You can keep track of the implementation progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is total, you can invoke the model utilizing a SageMaker runtime client and integrate it with your applications.<br>
 <br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
 <br>To begin with DeepSeek-R1 using the [SageMaker](http://64.227.136.170) Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the needed AWS approvals and environment setup. The following is a detailed code example that shows how to release and use DeepSeek-R1 for inference programmatically. The code for releasing the design is provided in the Github here. You can clone the note pad and run 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 likewise utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail utilizing the [Amazon Bedrock](https://gitlab.buaanlsde.cn) console or the API, and execute it as revealed in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent unwanted charges, complete the actions in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace deployment<br>
 <br>If you deployed 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 implementations.
 2. In the Managed deployments area, locate the [endpoint](https://notewave.online) you want 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 correct 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](https://www.netrecruit.al) if you leave it [running](https://fewa.hudutech.com). Use the following code to delete the endpoint if you desire 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 design utilizing 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 models, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock 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 helps emerging generative [AI](https://upmasty.com) companies develop ingenious solutions using AWS services and accelerated calculate. Currently, he is concentrated on developing methods for fine-tuning and enhancing the reasoning performance of big language designs. In his downtime, Vivek delights in treking, watching films, and attempting different cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://162.55.45.54:3000) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](https://bestwork.id) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
 <br>Jonathan Evans is an Expert Solutions Architect working on generative [AI](http://47.106.205.140:8089) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://charin-issuedb.elaad.io) hub. She is [passionate](https://career.agricodeexpo.org) about developing options that help consumers accelerate their [AI](https://demo.pixelphotoscript.com) journey and unlock company value.<br>