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

2025-02-20 13:13:17 +08:00 · 2025-02-20 13:13:17 +08:00 · 486380cfd6
commit 486380cfd6
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 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 release DeepSeek [AI](https://kenyansocial.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative [AI](http://awonaesthetic.co.kr) concepts on AWS.<br>
 <br>In this post, we demonstrate how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to release the distilled variations of the designs too.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](http://pinetree.sg) that uses reinforcement discovering to enhance thinking abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. An essential distinguishing feature is its reinforcement knowing (RL) action, which was utilized to refine the model's actions beyond the standard pre-training and tweak process. By including RL, DeepSeek-R1 can adapt better to user feedback and goals, eventually enhancing both relevance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, implying it's equipped to break down complex inquiries and reason through them in a detailed manner. This directed reasoning [procedure](http://www.origtek.com2999) allows the model to produce more accurate, transparent, and detailed responses. This model combines RL-based fine-tuning with CoT abilities, aiming to create [structured responses](http://git.swordlost.top) while concentrating on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has captured the market's attention as a flexible text-generation model that can be integrated into numerous workflows such as representatives, logical thinking and data interpretation jobs.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture enables activation of 37 billion specifications, [allowing efficient](http://www.asystechnik.com) reasoning by routing inquiries to the most relevant expert "clusters." This approach permits the design to focus on various issue domains while maintaining overall performance. 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 circumstances to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 model to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process 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 model.<br>
 <br>You can release DeepSeek-R1 design either through  or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend deploying this design with guardrails in location. In this blog site,  [surgiteams.com](https://surgiteams.com/index.php/User:JulietBoswell) we will utilize Amazon Bedrock Guardrails to introduce safeguards, prevent damaging material, and examine models against key security criteria. At the time of writing this blog site, for DeepSeek-R1 deployments on [SageMaker JumpStart](http://124.16.139.223000) and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce numerous guardrails tailored to various use cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls across your generative [AI](http://47.106.205.140:8089) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you require access to an ml.p5e instance. To check 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 usage. Make certain that you have at least one ml.P5e.48 [xlarge instance](https://gl.vlabs.knu.ua) in the AWS Region you are releasing. To ask for a limitation increase, produce a limitation boost demand 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 appropriate AWS Identity and Gain Access To Management (IAM) approvals to use Amazon Bedrock Guardrails. For directions, 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, prevent damaging material, and examine designs against key security requirements. You can implement precaution for the DeepSeek-R1 model using the [Amazon Bedrock](https://www.sintramovextrema.com.br) ApplyGuardrail API. This permits you to apply guardrails to assess user inputs and model actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail utilizing the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
 <br>The basic 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 model for inference. After getting the model's output, another guardrail check is applied. If the output passes this final check, it's returned as the outcome. However, if either the input or output is stepped in by the guardrail, a message is returned indicating the nature of the [intervention](https://jobwings.in) and whether it happened at the input or output phase. 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 structure designs (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, pick Model catalog under [Foundation](https://social.netverseventures.com) designs in the navigation pane.
 At the time of composing this post, you can utilize the InvokeModel API to [conjure](https://hektips.com) up the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a service provider and select the DeepSeek-R1 design.<br>
 <br>The design detail page supplies necessary details about the model's abilities, rates structure, and application standards. You can find detailed use guidelines, consisting of sample API calls and code snippets for integration. The model supports various text generation jobs, consisting of material creation, code generation, and question answering, using its [reinforcement learning](https://git.magesoft.tech) optimization and CoT reasoning capabilities.
 The page likewise includes release choices and licensing details to help you get started with DeepSeek-R1 in your applications.
 3. To start utilizing DeepSeek-R1, pick Deploy.<br>
 <br>You will be prompted to configure the implementation 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 Number of circumstances, enter a variety of instances (between 1-100).
 6. For Instance type, choose your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
 Optionally, you can configure innovative security and facilities settings, including virtual personal cloud (VPC) networking, service function permissions, and encryption settings. For the majority of use cases, the default settings will work well. However, for production releases, you may want to evaluate these settings to align with your organization's security and compliance requirements.
 7. Choose Deploy to start utilizing the model.<br>
 <br>When the implementation is complete, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
 8. Choose Open in playground to access an interactive user interface where you can try out different triggers and adjust model specifications like temperature level and optimum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For example, material for inference.<br>
 <br>This is an excellent method to explore the model's reasoning and text generation abilities before incorporating it into your applications. The play area supplies instant feedback, assisting you understand how the model reacts to various inputs and letting you tweak your prompts for [optimum outcomes](http://fggn.kr).<br>
 <br>You can rapidly evaluate the model in the play ground through the UI. However, to invoke the released model 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 demonstrates how to perform reasoning [utilizing](http://globalk-foodiero.com) a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can create 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 produced the guardrail, use the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures reasoning parameters, and sends out a request to create 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, built-in algorithms, and prebuilt ML services that you can deploy with just a few clicks. With SageMaker JumpStart, you can [tailor pre-trained](http://git.1473.cn) models to your use case, with your information, and release them into [production](http://101.43.112.1073000) using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides two hassle-free techniques: using the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker [Python SDK](https://webshow.kr). Let's check out both techniques to assist you select the approach that finest fits your needs.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following steps to release DeepSeek-R1 using SageMaker JumpStart:<br>
 <br>1. On the [SageMaker](https://myafritube.com) console, choose Studio in the navigation pane.
 2. First-time users will be prompted to develop a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The model internet browser displays available models, with details like the supplier name and [model capabilities](https://local.wuanwanghao.top3000).<br>
 <br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 design card.
 Each design card shows [crucial](http://gitea.smartscf.cn8000) details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task [category](https://remote-life.de) (for instance, Text Generation).
 Bedrock Ready badge (if appropriate), indicating that this design can be registered with Amazon Bedrock, allowing 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 design name and supplier details.
 Deploy button to release the design.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab consists of important details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical [specifications](https://jamboz.com).
 - Usage standards<br>
 <br>Before you deploy the model, it's advised to examine the design details and license terms to confirm compatibility with your use case.<br>
 <br>6. Choose Deploy to continue with release.<br>
 <br>7. For Endpoint name, use the automatically produced name or develop a customized one.
 8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, enter the number of instances (default: 1).
 Selecting appropriate circumstances types and counts is essential for cost and performance optimization. Monitor your implementation to change these settings as needed.Under Inference type, [Real-time inference](https://mxlinkin.mimeld.com) 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 sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
 11. Choose Deploy to release the model.<br>
 <br>The release process can take a number of minutes to finish.<br>
 <br>When deployment is complete, your endpoint status will alter to InService. At this moment, the design is prepared to accept reasoning requests through the endpoint. You can keep track of the deployment progress on the [SageMaker console](https://omegat.dmu-medical.de) Endpoints page, which will show pertinent metrics and status details. When the deployment is total, you can conjure up the model utilizing a SageMaker runtime customer and integrate it with your applications.<br>
 <br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
 <br>To get started with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS authorizations 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 model 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 reasoning with your SageMaker JumpStart predictor<br>
 <br>Similar to Amazon Bedrock, you can likewise 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 displayed in the following code:<br>
 <br>Clean up<br>
 <br>To avoid unwanted charges, complete the actions in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you released the model utilizing Amazon Bedrock Marketplace, complete the following steps:<br>
 <br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace releases.
 2. In the Managed releases area, locate 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 correct release: 1. Endpoint name.
 2. Model name.
 3. Endpoint status<br>
 <br>Delete the SageMaker JumpStart predictor<br>
 <br>The SageMaker [JumpStart design](https://goalsshow.com) you deployed will sustain costs 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](https://consultoresdeproductividad.com) how you can access and deploy the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in [SageMaker Studio](https://inicknet.com) or Amazon Bedrock Marketplace now to get going. 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 Beginning with Amazon SageMaker [JumpStart](https://charin-issuedb.elaad.io).<br>
 <br>About the Authors<br>
 <br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging generative [AI](http://cloud-repo.sdt.services) companies develop innovative solutions using [AWS services](http://ja7ic.dxguy.net) and sped up compute. Currently, he is concentrated on developing techniques for fine-tuning and enhancing the inference efficiency of large language models. In his spare time, Vivek enjoys treking, watching motion pictures, and trying different foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://8.129.8.58) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](https://git.unicom.studio) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is a Specialist Solutions Architect dealing with generative [AI](http://133.242.131.226:3003) with the Third-Party Model Science group at AWS.<br>
 <br>Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial [intelligence](https://git.nagaev.pro) and [generative](http://git.tederen.com) [AI](https://integramais.com.br) center. She is passionate about constructing solutions that help customers accelerate their [AI](https://quickservicesrecruits.com) journey and unlock organization worth.<br>