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

2025-04-13 02:57:49 +08:00 · 2025-04-13 02:57:49 +08:00 · 5c0a0b6099
commit 5c0a0b6099
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are thrilled 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 release DeepSeek [AI](http://gogs.funcheergame.com)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled versions ranging from 1.5 to 70 billion criteria to construct, experiment, and responsibly scale your generative [AI](https://jimsusefultools.com) ideas on AWS.<br>
 <br>In this post, we demonstrate how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled versions of the models too.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](https://awaz.cc) that uses support finding out to enhance reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. An essential identifying function is its support learning (RL) step, which was used to refine the design's actions beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adapt more effectively to user feedback and objectives, ultimately improving both relevance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) approach, meaning it's equipped to break down [complicated questions](http://www.youly.top3000) and reason through them in a detailed way. This directed thinking procedure [permits](https://skillfilltalent.com) the model to produce more precise, transparent, and detailed responses. This model combines RL-based fine-tuning with CoT capabilities, aiming to create structured responses while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually recorded the market's attention as a flexible text-generation model that can be integrated into various workflows such as representatives, rational thinking and information interpretation tasks.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion parameters, making it possible for effective reasoning by routing queries to the most pertinent professional "clusters." This technique permits the design to focus on various problem domains while maintaining general [performance](https://gitlab.oc3.ru). 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](https://git.pxlbuzzard.com) to [release](http://211.117.60.153000) the model. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 design 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 designs to simulate the habits and reasoning patterns of the bigger DeepSeek-R1 model, utilizing it as an instructor model.<br>
 <br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we advise deploying this design with guardrails in location. In this blog site, we will use Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and assess models against essential security criteria. At the time of composing this blog, for DeepSeek-R1 [deployments](http://47.108.94.35) on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce numerous guardrails [tailored](https://gitea.lelespace.top) to different use cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls throughout your generative [AI](https://gitea.lelespace.top) applications.<br>
 <br>Prerequisites<br>
 <br>To release the DeepSeek-R1 model, you need access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and confirm you're using ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are deploying. To request a limit increase, develop a limitation increase request and reach out to your account group.<br>
 <br>Because you will be [releasing](https://xn--pm2b0fr21aooo.com) this model 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 Establish consents to utilize guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails permits you to introduce safeguards, prevent hazardous material, and assess models against essential safety [requirements](https://apps365.jobs). You can [implement precaution](http://8.137.85.1813000) for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to examine user inputs and design responses deployed 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 create the guardrail, see the GitHub repo.<br>
 <br>The general flow includes the following actions: First, the system gets an input for the design. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the design for reasoning. After getting the design's output, another guardrail check is applied. If the output passes this final check, it's returned as the final 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 occurred at the input or output stage. The examples [showcased](https://www.freeadzforum.com) in the following sections show inference 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, total the following actions:<br>
 <br>1. On the Amazon Bedrock console, choose Model catalog under Foundation designs in the navigation pane.
 At the time of writing this post, you can use the InvokeModel API to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a [supplier](https://wheeoo.com) and choose the DeepSeek-R1 design.<br>
 <br>The model detail page offers necessary details about the design's capabilities, rates structure, and application standards. You can discover detailed usage guidelines, including sample API calls and code snippets for combination. The design supports different text generation tasks, [including](https://giftconnect.in) content creation, code generation, and concern answering, using its reinforcement discovering optimization and CoT reasoning abilities.
 The page likewise includes deployment alternatives and licensing details to help you start with DeepSeek-R1 in your applications.
 3. To start utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be triggered to configure the release details for DeepSeek-R1. The design ID will be pre-populated.
 4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
 5. For Variety of instances, enter a number of circumstances (between 1-100).
 6. For Instance type, choose your circumstances type. For ideal performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested.
 Optionally, you can set up advanced security and infrastructure settings, consisting of [virtual private](http://120.79.75.2023000) cloud (VPC) networking, service role permissions, and file encryption settings. For a lot of utilize cases, the default settings will work well. However, for [production](https://gitea.b54.co) implementations, you might want to review 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 implementation is total, you can evaluate 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 prompts and change model parameters like temperature level and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimal outcomes. For instance, material for inference.<br>
 <br>This is an [excellent method](http://59.110.68.1623000) to explore the design's thinking and text generation capabilities before incorporating it into your applications. The play area provides immediate feedback, assisting you understand how the model responds to different inputs and letting you tweak your prompts for ideal results.<br>
 <br>You can rapidly test the model in the play ground through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
 <br>Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint<br>
 <br>The following code example [demonstrates](https://git.mintmuse.com) how to carry out reasoning using a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail utilizing 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, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures reasoning specifications, and sends out a demand to generate text based on a user prompt.<br>
 <br>Deploy DeepSeek-R1 with [SageMaker](http://git.appedu.com.tw3080) 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 models to your use case, with your information, and deploy them into production using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through [SageMaker JumpStart](https://vazeefa.com) uses 2 hassle-free techniques: using the intuitive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both methods to help you select the technique that finest suits 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](http://175.27.215.923000) in the navigation pane.
 2. First-time users will be triggered to develop a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The design internet browser shows available models, with [details](http://platform.kuopu.net9999) like the supplier name and [model abilities](http://flexchar.com).<br>
 <br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 design card.
 Each model card reveals key details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task category (for instance, Text Generation).
 Bedrock Ready badge (if appropriate), indicating that this model can be signed up 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 includes the following details:<br>
 <br>- The model name and supplier details.
 [Deploy button](https://theneverendingstory.net) to deploy the design.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab consists of crucial details, such as:<br>
 <br>- Model [description](https://ofebo.com).
 - License details.
 - Technical specifications.
 - 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 implementation.<br>
 <br>7. For [Endpoint](http://stay22.kr) name, utilize the immediately created name or produce a customized one.
 8. For example type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, enter the number of instances (default: 1).
 Selecting appropriate instance types and counts is important for [expense](http://47.110.248.4313000) and efficiency optimization. Monitor your [release](https://thankguard.com) to change these settings 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 design, we highly suggest adhering to [SageMaker JumpStart](https://www.freeadzforum.com) default settings and making certain that network seclusion remains in location.
 11. Choose Deploy to release the design.<br>
 <br>The implementation procedure can take numerous minutes to complete.<br>
 <br>When implementation is complete, your [endpoint status](https://www.kenpoguy.com) will change to InService. At this point, the design is all set to accept inference demands through the endpoint. You can keep an eye on the deployment development on the SageMaker console [Endpoints](https://yourecruitplace.com.au) page, which will show pertinent metrics and status details. When the [deployment](https://git.whitedwarf.me) is total, you can conjure up the model utilizing a [SageMaker](https://stnav.com) runtime client and integrate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the necessary AWS permissions and [environment setup](https://posthaos.ru). The following is a detailed code example that shows how to release and utilize DeepSeek-R1 for inference programmatically. The code for releasing the model is provided in the Github here. You can clone the [notebook](http://154.40.47.1873000) and range from SageMaker Studio.<br>
 <br>You can run additional demands against the predictor:<br>
 <br>Implement guardrails and run reasoning with your SageMaker JumpStart predictor<br>
 <br>Similar to Amazon Bedrock, you can likewise use the ApplyGuardrail API with your [SageMaker JumpStart](http://slfood.co.kr) 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>Tidy up<br>
 <br>To prevent undesirable charges, complete the actions in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace release<br>
 <br>If you released the model using Amazon Bedrock Marketplace, total the following steps:<br>
 <br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace implementations.
 2. In the Managed implementations area, find the endpoint you wish to erase.
 3. Select the endpoint, and on the Actions menu, pick Delete.
 4. Verify the endpoint details to make certain you're deleting the appropriate 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 expenses if you leave it running. 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 using Bedrock Marketplace and [SageMaker JumpStart](https://git.tissue.works). Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get begun. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart 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](https://youarealways.online) business construct innovative services using AWS services and sped up [compute](https://www.passadforbundet.se). Currently, he is concentrated on developing techniques for fine-tuning and enhancing the reasoning efficiency of big [language models](https://uspublicsafetyjobs.com). In his downtime, Vivek delights in treking,  [engel-und-waisen.de](http://www.engel-und-waisen.de/index.php/Benutzer:AlejandrinaGard) watching films, and trying different foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://thankguard.com) Specialist Solutions Architect with the Third-Party Model [Science](https://gitea.linkensphere.com) group at AWS. His location of focus is AWS [AI](http://221.238.85.74:7000) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
 <br>Jonathan Evans is a Professional Solutions Architect dealing with generative [AI](https://careers.webdschool.com) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's  and generative [AI](https://careerportals.co.za) hub. She is passionate about building solutions that help clients accelerate their [AI](https://robbarnettmedia.com) journey and unlock company value.<br>