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

2025-02-17 02:32:28 +08:00 · 2025-02-17 02:32:28 +08:00 · e41aa33367
parent 00f365961e
commit e41aa33367
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 deploy DeepSeek [AI](http://175.178.199.62:3000)'s first-generation frontier model, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion parameters to construct, experiment, and responsibly scale your generative [AI](http://39.108.86.52:3000) 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 similar actions to deploy the distilled variations of the designs as well.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://thaisfriendly.com) that utilizes reinforcement learning to boost thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A crucial distinguishing function is its support learning (RL) step, which was used to improve the design's actions beyond the basic pre-training and tweak procedure. By integrating RL, DeepSeek-R1 can adjust better to user feedback and objectives, eventually enhancing both relevance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, indicating it's geared up to break down intricate inquiries and reason through them in a detailed manner. This directed thinking process [enables](http://8.134.253.2218088) the design to produce more accurate, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT abilities, aiming to produce structured responses while [focusing](http://112.74.102.696688) on [interpretability](https://media.motorsync.co.uk) and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually recorded the industry's attention as a flexible text-generation model that can be integrated into various workflows such as representatives, rational reasoning and information interpretation jobs.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture enables activation of 37 billion criteria, making it possible for effective reasoning by routing inquiries to the most relevant specialist "clusters." This approach permits the model to focus on various issue domains while maintaining overall 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 circumstances to release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the reasoning [capabilities](https://aggm.bz) of the main R1 design to more effective architectures based upon popular open designs 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 mimic 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](https://grace4djourney.com) model, we advise deploying this model with guardrails in location. In this blog site, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent hazardous content, and examine models against crucial safety requirements. At the time of writing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can [produce](https://ssh.joshuakmckelvey.com) several guardrails tailored to various use cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing security controls across your generative [AI](http://139.162.7.140:3000) applications.<br>
 <br>Prerequisites<br>
 <br>To release the DeepSeek-R1 model, you require access to an ml.p5e circumstances. 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](https://www.nc-healthcare.co.uk) use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are releasing. To request a limit boost, create a limit increase demand and connect to your account team.<br>
 <br>Because you will be releasing this model with [Amazon Bedrock](https://rrallytv.com) Guardrails, make certain you have the appropriate AWS Identity and [Gain Access](http://wrgitlab.org) To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For guidelines, see Set up permissions to use guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails permits you to introduce safeguards, avoid hazardous material,  [garagesale.es](https://www.garagesale.es/author/toshahammon/) and assess models against crucial safety criteria. You can carry out precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use [guardrails](https://git.ddswd.de) to assess user inputs and design 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 develop the guardrail, see the GitHub repo.<br>
 <br>The basic circulation involves the following actions: First, the system receives 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](http://gogs.black-art.cn) is applied. If the output passes this final check, it's returned as the 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 demonstrate inference using this API.<br>
 <br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
 <br>Amazon Bedrock Marketplace offers you access to over 100 popular, emerging, and  [surgiteams.com](https://surgiteams.com/index.php/User:SonOyi09774) 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, choose Model brochure under Foundation models in the navigation pane.
 At the time of writing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other [Amazon Bedrock](http://129.211.184.1848090) tooling.
 2. Filter for DeepSeek as a company and pick the DeepSeek-R1 model.<br>
 <br>The model detail page supplies essential details about the design's capabilities, pricing structure, and implementation standards. You can discover detailed usage directions, including sample API calls and code bits for integration. The design supports different text generation tasks, consisting of content development, code generation, and concern answering, using its support finding out optimization and CoT thinking capabilities.
 The page also consists of implementation options and licensing details to help you get going with DeepSeek-R1 in your [applications](https://code.thintz.com).
 3. To begin 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, go into an endpoint name (in between 1-50 alphanumeric characters).
 5. For [Variety](https://syndromez.ai) of instances, enter a number of [circumstances](https://edurich.lk) (in between 1-100).
 6. For example type, choose your instance type. For ideal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
 Optionally, you can configure sophisticated security and facilities settings, including virtual personal cloud (VPC) networking, service function approvals, and encryption settings. For the [majority](https://3.223.126.156) of utilize cases, the default settings will work well. However, for production implementations, you may want to evaluate these [settings](https://insta.tel) to line up with your organization's security and compliance requirements.
 7. Choose Deploy to start using the model.<br>
 <br>When the implementation is total, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
 8. Choose Open in play ground to access an interactive interface where you can experiment with various prompts and change design parameters like temperature level and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For example, material for reasoning.<br>
 <br>This is an excellent way to check out the design's reasoning and text generation abilities before incorporating it into your applications. The playground supplies immediate feedback, assisting you understand how the model reacts to various inputs and letting you tweak your prompts for optimum results.<br>
 <br>You can quickly check the design in the playground through the UI. However, to conjure up the deployed design programmatically with any [Amazon Bedrock](https://git.silasvedder.xyz) APIs, you need to get the endpoint ARN.<br>
 <br>Run reasoning using guardrails with the  DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to carry out inference using a [released](http://47.108.94.35) DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock [console](https://gitea.alexconnect.keenetic.link) or the API. For the example code to create the guardrail, see the GitHub repo. After you have actually developed the guardrail, use the following code to carry out guardrails. The script initializes the bedrock_runtime client, sets up reasoning criteria, and sends a demand to generate 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 release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your usage case, with your information, and deploy them into production using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart uses 2 hassle-free methods: utilizing the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both techniques to help you pick the technique that finest suits your needs.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following steps to [release](http://stackhub.co.kr) DeepSeek-R1 using SageMaker JumpStart:<br>
 <br>1. On the SageMaker console, select Studio in the navigation pane.
 2. First-time users will be [prompted](https://copyrightcontest.com) to develop a domain.
 3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
 <br>The model browser shows available designs, with details like the company name and design capabilities.<br>
 <br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card.
 Each design card shows crucial details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task category (for instance, Text Generation).
 [Bedrock Ready](https://lokilocker.com) badge (if relevant), indicating that this model can be signed up 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 [consists](http://sgvalley.co.kr) of 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 includes crucial details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical specs.
 - Usage guidelines<br>
 <br>Before you release the model, it's suggested to evaluate the design details and license terms to validate compatibility with your usage case.<br>
 <br>6. Choose Deploy to proceed with release.<br>
 <br>7. For Endpoint name, use the automatically generated name or produce a customized one.
 8. For Instance type ¸ select an instance type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, go into the variety of instances (default: 1).
 Selecting suitable instance types and counts is crucial for [expense](http://tanpoposc.com) and efficiency optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time inference is chosen by default. This is enhanced for  [trademarketclassifieds.com](https://trademarketclassifieds.com/user/profile/2772329) sustained traffic and low latency.
 10. Review all configurations for precision. For this model, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network isolation remains in place.
 11. Choose Deploy to release the model.<br>
 <br>The release process can take several minutes to complete.<br>
 <br>When deployment is complete, your endpoint status will change to InService. At this point, the design is prepared to accept reasoning requests through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is complete, you can conjure up the [model utilizing](https://gitea.v-box.cn) a SageMaker runtime client and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 utilizing the [SageMaker Python](https://www.facetwig.com) SDK<br>
 <br>To begin with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the required AWS permissions and environment setup. The following is a detailed code example that shows how to release and utilize DeepSeek-R1 for inference programmatically. The code for [releasing](https://gayplatform.de) the design is [supplied](http://8.140.200.2363000) in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
 <br>You can run extra requests 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 produce a guardrail using the [Amazon Bedrock](https://www.panjabi.in) console or the API, and execute it as displayed in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent undesirable charges, finish the steps in this section to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace deployment<br>
 <br>If you released the model using Amazon Bedrock Marketplace, total the following actions:<br>
 <br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
 2. In the Managed deployments area, find the [endpoint](https://git.ddswd.de) you want to erase.
 3. Select the endpoint, and on the Actions menu, choose Delete.
 4. Verify the endpoint details to make certain you're erasing the correct deployment: 1. [Endpoint](https://www.jobsalert.ai) 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 checked out how you can access and deploy the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting 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 generative [AI](https://digital-field.cn:50443) business develop [innovative](https://ddsbyowner.com) [services utilizing](https://opela.id) AWS services and sped up calculate. Currently, he is focused on establishing strategies for fine-tuning and enhancing the inference performance of large language designs. In his free time, Vivek delights in hiking, viewing motion pictures, and [attempting](https://easterntalent.eu) various foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://www.hanmacsamsung.com) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His [location](https://www.assistantcareer.com) of focus is AWS [AI](http://8.134.253.221:8088) 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://sportify.brandnitions.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 artificial intelligence and generative [AI](https://gitea.nasilot.me) hub. She is passionate about building services that help customers accelerate their [AI](https://sc.e-path.cn) journey and unlock business value.<br>