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

2025-02-20 05:48:44 +08:00
commit de704c791a
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 reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://testing-sru-git.t2t-support.com)'s first-generation frontier design, DeepSeek-R1, along with the distilled variations varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative [AI](https://ipen.com.hk) 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 actions to deploy the distilled versions of the designs also.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://pakfindjob.com) that uses reinforcement discovering to enhance reasoning capabilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential identifying function is its support knowing (RL) action, which was used to refine the design's responses beyond the basic pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adapt more successfully to user [feedback](https://talentocentroamerica.com) and goals, ultimately enhancing both significance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) technique, implying it's geared up to break down [intricate questions](https://ipmanage.sumedangkab.go.id) and factor through them in a detailed way. This assisted reasoning procedure enables the design to [produce](http://www.yasunli.co.id) more accurate, transparent, and [detailed responses](https://gitlab.econtent.lu). This model combines RL-based fine-tuning with CoT capabilities, aiming to create structured reactions while focusing on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has actually caught the industry's attention as a flexible text-generation design that can be integrated into different workflows such as representatives, rational thinking and data interpretation jobs.<br>
 <br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion parameters, making it possible for efficient inference by routing questions to the most relevant expert "clusters." This technique allows the model to concentrate on various problem domains while [maintaining](https://surgiteams.com) total performance. DeepSeek-R1 needs 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 to release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled designs bring the reasoning capabilities of the main R1 design to more [efficient architectures](https://testing-sru-git.t2t-support.com) 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 sized, more efficient designs to [imitate](https://git.cavemanon.xyz) the habits and thinking 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 [utilize Amazon](https://healthcarejob.cz) Bedrock Guardrails to present safeguards, prevent harmful material, and evaluate designs against essential safety 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 create several [guardrails tailored](https://twoo.tr) to different usage cases and use them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls across your generative [AI](https://git.thomasballantine.com) applications.<br>
 <br>Prerequisites<br>
 <br>To release 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 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 releasing. To ask for a limit increase, develop a limit increase request and connect to your account group.<br>
 <br>Because you will be releasing 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 utilize guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails allows you to introduce safeguards,  [wiki.whenparked.com](https://wiki.whenparked.com/User:JZKMireya164733) avoid harmful content, and evaluate models against key security requirements. You can  procedures for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and  [larsaluarna.se](http://www.larsaluarna.se/index.php/User:BerylTazewell8) model reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a [guardrail utilizing](https://radicaltarot.com) the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
 <br>The basic circulation involves 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 out to the model for inference. After getting the model's output, another guardrail check is applied. If the output passes this last check, it's returned as the 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 happened at the input or output stage. The examples showcased in the following sections demonstrate inference using 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 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 console, pick 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 design. It does not support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a [service provider](https://aceme.ink) and select the DeepSeek-R1 design.<br>
 <br>The design detail page supplies vital details about the model's capabilities, rates structure, and implementation standards. You can discover detailed usage directions, including sample API calls and code snippets for integration. The design supports numerous text generation tasks, consisting of material development, code generation, and concern answering, using its support learning optimization and CoT reasoning abilities.
 The page also includes implementation alternatives and licensing details to assist you get going with DeepSeek-R1 in your applications.
 3. To start using DeepSeek-R1, pick Deploy.<br>
 <br>You will be prompted to configure the implementation details for DeepSeek-R1. The model ID will be [pre-populated](https://laborando.com.mx).
 4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
 5. For Variety of circumstances, go into a variety of circumstances (between 1-100).
 6. For [Instance](https://code.3err0.ru) type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
 Optionally, you can configure sophisticated security and infrastructure settings, including virtual personal cloud (VPC) networking, service role consents, and [encryption settings](https://redsocial.cl). For many use cases, the default settings will work well. However, for production releases, you may wish to evaluate these settings to line up with your organization's security and compliance requirements.
 7. Choose Deploy to begin using the model.<br>
 <br>When the release is complete, you can evaluate DeepSeek-R1's capabilities straight in the Amazon Bedrock playground.
 8. Choose Open in play ground to access an interactive interface where you can try out different triggers and adjust design parameters like temperature and maximum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for ideal results. For instance, material for inference.<br>
 <br>This is an exceptional method to explore the design's reasoning and text generation capabilities before incorporating it into your applications. The play area supplies immediate feedback, assisting you comprehend how the [design responds](https://sportworkplace.com) to different inputs and [letting](https://hilife2b.com) you tweak your [triggers](http://www.asystechnik.com) for ideal results.<br>
 <br>You can quickly check the model in the play area through the UI. However,  [wiki.asexuality.org](https://wiki.asexuality.org/w/index.php?title=User_talk:GonzaloVue84412) to conjure up the released design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
 <br>Run reasoning using guardrails with the released DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to perform inference utilizing a deployed DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have produced the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_[runtime](http://christiancampnic.com) customer, sets up [reasoning](http://gsrl.uk) specifications, and sends out a demand to [generate text](https://twittx.live) based on a user timely.<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 deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your data, and release them into production using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart offers 2 convenient techniques: using the [instinctive SageMaker](https://www.calogis.com) JumpStart UI or implementing programmatically through the [SageMaker Python](https://pingpe.net) SDK. Let's check out both approaches to assist you choose the method that finest suits your needs.<br>
 <br>Deploy DeepSeek-R1 through [SageMaker JumpStart](https://customerscomm.com) 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 prompted to produce a domain.
 3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
 <br>The model browser displays available designs, with details like the provider name and design abilities.<br>
 <br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 model card.
 Each model card reveals crucial details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task classification (for instance, Text Generation).
 Bedrock Ready badge (if relevant), indicating that this model can be signed up with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to conjure up the model<br>
 <br>5. Choose the model card to view the model details page.<br>
 <br>The design details page includes the following details:<br>
 <br>- The model name and provider details.
 Deploy button 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.
 - License details.
 - Technical specifications.
 - Usage standards<br>
 <br>Before you deploy the model, it's advised to review the design details and license terms to validate compatibility with your use case.<br>
 <br>6. Choose Deploy to proceed with [release](https://chutpatti.com).<br>
 <br>7. For Endpoint name, use the immediately produced name or produce a customized one.
 8. For [Instance type](http://121.43.99.1283000) ¸ select a circumstances 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 implementation to change these settings as needed.Under Inference type, Real-time reasoning is picked by default. This is enhanced for sustained traffic and low latency.
 10. Review all configurations for precision. For this design, we highly recommend adhering to SageMaker JumpStart default settings and making certain that network isolation remains in place.
 11. Choose Deploy to deploy the model.<br>
 <br>The deployment process can take a number of minutes to finish.<br>
 <br>When implementation is total, your endpoint status will alter to InService. At this moment, the model is all set to accept inference requests through the [endpoint](http://8.140.200.2363000). You can keep track of the deployment progress on the SageMaker console Endpoints page, which will display pertinent [metrics](http://94.130.182.1543000) and status details. When the [deployment](http://tigg.1212321.com) is total, you can conjure up the model using a SageMaker runtime client and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
 <br>To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the necessary AWS authorizations and environment setup. The following is a detailed code example that shows how to release 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 additional requests 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 develop a guardrail using the Amazon Bedrock console or the API, and implement it as revealed in the following code:<br>
 <br>Tidy up<br>
 <br>To avoid undesirable charges, finish the steps in this area to tidy up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace deployment<br>
 <br>If you released the model using [Amazon Bedrock](https://bihiring.com) Marketplace, total the following steps:<br>
 <br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, select Marketplace [implementations](https://git.nazev.eu).
 2. In the Managed implementations area, locate 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 correct deployment: 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 expenses if you leave it running. Use the following code to delete the endpoint if you want to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
 <br>Conclusion<br>
 <br>In this post, we checked out how you can access and release the DeepSeek-R1 [design utilizing](https://winf.dhsh.de) 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 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 [assists emerging](https://loveyou.az) generative [AI](https://edenhazardclub.com) companies build innovative solutions utilizing AWS services and sped up compute. Currently, he is focused on developing strategies for fine-tuning and enhancing the reasoning efficiency of large language models. In his [complimentary](https://bocaiw.in.net) time, Vivek takes pleasure in treking, seeing movies, and trying different cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://gitlab.code-nav.cn) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](https://rootsofblackessence.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
 <br>Jonathan Evans is an Expert Solutions Architect dealing with generative [AI](http://107.172.157.44:3000) with the Third-Party Model Science group at AWS.<br>
 <br>[Banu Nagasundaram](https://gitcq.cyberinner.com) leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://skytechenterprisesolutions.net) hub. She is enthusiastic about building solutions that assist consumers accelerate their [AI](http://gitlab.boeart.cn) journey and unlock business value.<br>