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

2025-04-07 11:12:02 +00:00 · 2025-04-07 11:12:02 +00:00 · 5eeee3603e
commit 5eeee3603e
parent 04b3c8380d
1 changed files with 93 additions and 0 deletions
--- a/DeepSeek-R1-Model-now-Available-in-Amazon-Bedrock-Marketplace-And-Amazon-SageMaker-JumpStart.md
+++ b/DeepSeek-R1-Model-now-Available-in-Amazon-Bedrock-Marketplace-And-Amazon-SageMaker-JumpStart.md
@ -0,0 +1,93 @@
 <br>Today, we are [excited](http://git.iloomo.com) 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 [AI](http://git2.guwu121.com)'s first-generation [frontier](https://git.xiaoya360.com) model, DeepSeek-R1, together with the distilled variations ranging from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative [AI](https://git.wun.im) ideas 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 actions to release the distilled variations of the models also.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a large language model (LLM) established by DeepSeek [AI](https://bahnreise-wiki.de) that uses reinforcement finding out to enhance thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key [distinguishing function](https://kaamdekho.co.in) is its support knowing (RL) step, which was utilized to fine-tune the model's reactions beyond the basic pre-training and tweak procedure. By including RL, DeepSeek-R1 can adjust more successfully to user feedback and objectives, eventually boosting both importance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, indicating it's geared up to break down complex inquiries and factor through them in a detailed manner. This directed reasoning procedure permits the design to produce more precise, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT abilities, aiming to generate structured responses while focusing on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has actually caught the industry's attention as a flexible text-generation design that can be incorporated into different workflows such as agents, sensible reasoning and information analysis jobs.<br>
 <br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion specifications, enabling effective inference by routing inquiries to the most appropriate professional "clusters." This method enables the model to concentrate on different problem domains while maintaining overall efficiency. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge instance to release 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 thinking capabilities of the main R1 design to more effective architectures based on [popular](https://www.p3r.app) open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller sized, more effective designs to simulate the habits and reasoning patterns of the larger DeepSeek-R1 design, utilizing it as an instructor design.<br>
 <br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend releasing this design with guardrails in location. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid harmful material, and [assess models](https://gitea.chofer.ddns.net) against key security criteria. At the time of composing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce multiple guardrails tailored to different usage cases and use them to the DeepSeek-R1 model, enhancing user experiences and [standardizing safety](https://satitmattayom.nrru.ac.th) controls across your generative [AI](http://www.amrstudio.cn:33000) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 model, 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, select Amazon SageMaker, and verify you're using ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To request a limitation boost, develop a [limit boost](https://forsetelomr.online) demand and connect to your account group.<br>
 <br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) consents to use  Guardrails. For guidelines, see Establish approvals to use guardrails for content filtering.<br>
 <br>Implementing guardrails with the [ApplyGuardrail](https://git.cno.org.co) API<br>
 <br>Amazon Bedrock Guardrails permits you to introduce safeguards,  [wiki.rolandradio.net](https://wiki.rolandradio.net/index.php?title=User:ChaseVandermark) avoid harmful content, and examine models against crucial safety criteria. You can carry out security steps for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to assess user inputs and model responses released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create 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 basic flow includes 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 receiving the model's output, another guardrail check is applied. If the output passes this last 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 the nature of the intervention and whether it happened 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 Marketplace<br>
 <br>Amazon Bedrock Marketplace gives 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 steps:<br>
 <br>1. On the Amazon Bedrock console, select 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 APIs and other Amazon Bedrock tooling.
 2. Filter for [DeepSeek](https://yourgreendaily.com) as a company and select the DeepSeek-R1 design.<br>
 <br>The design detail page supplies important details about the design's abilities, prices structure, and implementation guidelines. You can discover detailed usage directions, including sample API calls and code bits for integration. The design supports various text generation jobs, including material development, code generation, and concern answering, using its support learning optimization and CoT reasoning capabilities.
 The page likewise consists of implementation options and licensing details to help you start with DeepSeek-R1 in your applications.
 3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be prompted to set up the deployment details for DeepSeek-R1. The design ID will be pre-populated.
 4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters).
 5. For Number of circumstances, go into a variety of circumstances (in between 1-100).
 6. For example type, select your circumstances type. For ideal performance with DeepSeek-R1, a [GPU-based instance](https://webloadedsolutions.com) type like ml.p5e.48 xlarge is recommended.
 Optionally, you can configure advanced security and infrastructure settings, including virtual personal cloud (VPC) networking, service role permissions, and encryption settings. For many utilize cases, the default settings will work well. However, for production releases, you may wish to evaluate these settings to align with your company's security and compliance requirements.
 7. Choose Deploy to begin using the design.<br>
 <br>When the implementation is complete, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
 8. Choose Open in playground to access an interactive user interface where you can explore various triggers and change design criteria like temperature and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimum outcomes. For instance, content for reasoning.<br>
 <br>This is an excellent method to check out the design's thinking and text generation capabilities before incorporating it into your applications. The play area provides instant feedback, helping you understand how the design reacts to various inputs and letting you tweak your prompts for optimum results.<br>
 <br>You can rapidly test the design in the play ground through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
 <br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to carry out inference using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have developed the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime client, sets up reasoning parameters, and sends out a demand to produce text based on a user prompt.<br>
 <br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
 <br>SageMaker JumpStart is an artificial [intelligence](https://pleroma.cnuc.nu) (ML) hub with FMs, [built-in](https://www.oscommerce.com) algorithms, and prebuilt ML options that you can [release](http://125.43.68.2263001) with just a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your data, and deploy them into production utilizing either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides two convenient methods: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the [SageMaker Python](https://socialnetwork.cloudyzx.com) SDK. Let's check out both approaches to help you pick the approach that best suits your requirements.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following actions to release 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 produce a domain.
 3. On the [SageMaker Studio](https://candidates.giftabled.org) console, select JumpStart in the navigation pane.<br>
 <br>The model web browser displays available designs, with details like the service provider name and model abilities.<br>
 <br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 model card.
 Each design card shows key details, including:<br>
 <br>- Model name
 - Provider name
 - Task category (for example, Text Generation).
 Bedrock Ready badge (if relevant), showing 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 model card to view the design details page.<br>
 <br>The model details page consists of the following details:<br>
 <br>- The design name and provider details.
 Deploy button to deploy the model.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab includes important details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical requirements.
 - Usage standards<br>
 <br>Before you release the design, it's recommended to review the design details and license terms to validate compatibility with your usage case.<br>
 <br>6. Choose Deploy to proceed with implementation.<br>
 <br>7. For Endpoint name, use the instantly generated name or create a customized one.
 8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, go into the variety of instances (default: 1).
 Selecting appropriate instance types and counts is crucial 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 [optimized](https://farmwoo.com) 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 deployment process can take a number of minutes to complete.<br>
 <br>When deployment is total, your endpoint status will alter to InService. At this moment, the design is ready to accept reasoning requests through the endpoint. You can keep an eye on the deployment development on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the implementation is total, you can conjure up the design using a SageMaker runtime client and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To begin with DeepSeek-R1 [utilizing](https://www.highpriceddatinguk.com) the SageMaker Python SDK, you will [require](http://47.98.226.2403000) to install the SageMaker Python SDK and make certain you have the needed [AWS approvals](https://git.penwing.org) and environment setup. The following is a detailed code example that demonstrates how to deploy 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.<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 create a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
 <br>Clean up<br>
 <br>To avoid [unwanted](https://git.xedus.ru) charges, finish the actions in this section to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you [deployed](http://lyo.kr) the design using Amazon Bedrock Marketplace, complete the following actions:<br>
 <br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace releases.
 2. In the Managed deployments area, find the endpoint you desire to delete.
 3. Select the endpoint, and on the Actions menu, pick Delete.
 4. Verify the endpoint details to make certain you're erasing the appropriate implementation: 1. Endpoint name.
 2. Model name.
 3. Endpoint status<br>
 <br>Delete the SageMaker JumpStart predictor<br>
 <br>The SageMaker JumpStart model you released will sustain costs if you leave it running. Use the following code to delete 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 release the DeepSeek-R1 design using Bedrock Marketplace and [SageMaker](http://115.236.37.10530011) JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, [Amazon Bedrock](https://repo.farce.de) 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](https://gitee.mmote.ru) business build [ingenious](https://jktechnohub.com) solutions using AWS services and accelerated compute. Currently, he is focused on developing methods for fine-tuning and optimizing the inference performance of large language designs. In his [leisure](https://116.203.22.201) time, Vivek delights in hiking, enjoying motion pictures, and attempting various foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://heartbeatdigital.cn) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](http://mirae.jdtsolution.kr) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is an Expert Solutions Architect working on [generative](https://xtragist.com) [AI](http://119.23.214.109:30032) with the Third-Party Model Science group at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and [generative](http://47.108.92.883000) [AI](https://loveyou.az) hub. She is enthusiastic about developing services that help [clients accelerate](https://gallery.wideworldvideo.com) their [AI](http://hmind.kr) journey and unlock business worth.<br>