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

master
Benjamin Overton 2025-02-15 23:43:11 +00:00
parent 040d2fa935
commit c76d7bc0dd
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are [delighted](https://www.luckysalesinc.com) 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://chutpatti.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions ranging from 1.5 to 70 billion specifications to develop, experiment, and properly scale your generative [AI](https://baripedia.org) ideas on AWS.<br>
<br>In this post, we show how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to deploy the distilled versions of the models also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) established by DeepSeek [AI](https://revinr.site) that uses support finding out to improve thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key distinguishing function is its reinforcement knowing (RL) action, which was used to fine-tune the model's reactions beyond the basic pre-training and tweak procedure. By incorporating RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately boosting both relevance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, [meaning](https://www.videomixplay.com) it's geared up to break down complicated inquiries and reason through them in a detailed way. This guided thinking process permits the design to produce more accurate, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT capabilities, aiming to generate structured actions while focusing on interpretability and [gratisafhalen.be](https://gratisafhalen.be/author/willianl17/) user interaction. With its extensive capabilities DeepSeek-R1 has caught the industry's attention as a versatile text-generation design that can be incorporated into different workflows such as agents, rational thinking and information interpretation tasks.<br>
<br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, enabling efficient reasoning by routing inquiries to the most pertinent expert "clusters." This technique permits the model to focus on various issue domains while maintaining total effectiveness. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for inference. In this post, we will utilize an ml.p5e.48 xlarge instance to release the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 model to more effective architectures based upon popular open [designs](http://39.106.223.11) like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of [training](http://103.140.54.203000) smaller, more effective designs to simulate the behavior and thinking patterns of the larger DeepSeek-R1 design, using it as an instructor model.<br>
<br>You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend releasing this model with guardrails in location. In this blog site, we will use Amazon Bedrock [Guardrails](http://165.22.249.528888) to present safeguards, avoid damaging content, and examine designs against essential security criteria. At the time of composing this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce several guardrails tailored to different use cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls throughout your generative [AI](http://git.zthymaoyi.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, you need access to an ml.p5e circumstances. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, select Amazon SageMaker, and validate you're utilizing 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 ask for a limit boost, develop a limitation boost demand and connect to your account team.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For instructions, see Establish permissions to utilize guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>[Amazon Bedrock](https://chutpatti.com) Guardrails allows you to present safeguards, prevent hazardous material, and assess models against crucial security requirements. You can execute security steps for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to evaluate user inputs and model responses released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the [GitHub repo](https://hotjobsng.com).<br>
<br>The basic flow involves 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 out to the design for reasoning. After receiving the model's output, another guardrail check is [applied](https://git.o-for.net). If the output passes this last check, it's returned as the result. However, if either the input or output is stepped in by the guardrail, a message is returned indicating the nature of the intervention and whether it occurred at the input or output stage. The examples showcased in the following areas demonstrate reasoning 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 specialized foundation designs (FMs) through [Amazon Bedrock](https://www.kmginseng.com). 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 utilize the InvokeModel API to invoke the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a supplier and pick the DeepSeek-R1 design.<br>
<br>The design detail page supplies essential details about the [model's](https://my-sugar.co.il) capabilities, rates structure, and execution guidelines. You can find detailed usage guidelines, including sample API calls and code bits for [trademarketclassifieds.com](https://trademarketclassifieds.com/user/profile/2672496) combination. The design supports different text generation jobs, consisting of material creation, code generation, and concern answering, using its reinforcement finding out optimization and CoT thinking capabilities.
The page likewise [consists](http://ep210.co.kr) of release options and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, select Deploy.<br>
<br>You will be triggered 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 Variety of instances, enter a number of circumstances (between 1-100).
6. For [Instance](http://120.77.205.309998) type, choose your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up sophisticated security and infrastructure settings, including virtual private cloud (VPC) networking, service function consents, and file encryption settings. For most utilize cases, the [default settings](https://eschoolgates.com) will work well. However, for production releases, you might want to examine these settings to align with your company's security and compliance requirements.
7. Choose Deploy to begin utilizing the model.<br>
<br>When the deployment is total, you can evaluate DeepSeek-R1's capabilities straight in the Amazon Bedrock playground.
8. Choose Open in play ground to access an interactive user interface where you can experiment with various prompts and change model criteria like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum results. For instance, content for reasoning.<br>
<br>This is an outstanding way to check out the design's reasoning and text generation capabilities before incorporating it into your [applications](https://goodinfriends.com). The provides instant feedback, assisting you understand how the design reacts to numerous inputs and [mediawiki.hcah.in](https://mediawiki.hcah.in/index.php?title=User:TyroneMcCabe) letting you fine-tune your prompts for ideal results.<br>
<br>You can rapidly evaluate the model in the play ground through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run inference using guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform inference using a released DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop a [guardrail](http://31.184.254.1768078) using the [Amazon Bedrock](https://social.updum.com) console or the API. For the example code to create 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, configures inference criteria, and sends out a demand to produce text based on a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an [artificial intelligence](http://git.qwerin.cz) (ML) hub with FMs, integrated algorithms, and prebuilt ML services that you can release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs 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 offers two hassle-free techniques: using the intuitive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's explore both techniques to assist you select the approach that best suits your requirements.<br>
<br>Deploy DeepSeek-R1 through [SageMaker JumpStart](http://hitq.segen.co.kr) UI<br>
<br>Complete the following actions to deploy DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the [SageMaker](https://corerecruitingroup.com) console, [select Studio](https://git.rell.ru) 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](https://interlinkms.lk) pane.<br>
<br>The design internet browser shows available models, with details like the provider name and model capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each design card shows crucial details, consisting of:<br>
<br>- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if applicable), [indicating](https://activeaupair.no) that this model can be registered with Amazon Bedrock, permitting you to [utilize Amazon](http://8.136.199.333000) Bedrock APIs to invoke the model<br>
<br>5. Choose the design card to view the design details page.<br>
<br>The [design details](https://raovatonline.org) page consists of the following details:<br>
<br>- The model name and supplier details.
Deploy button to deploy the model.
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 deploy the model, it's suggested to evaluate the design details and license terms to confirm compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with [release](http://git.setech.ltd8300).<br>
<br>7. For Endpoint name, use the [automatically](https://loveyou.az) created name or produce a customized one.
8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the number of circumstances (default: 1).
Selecting appropriate circumstances types and counts is crucial for cost and [links.gtanet.com.br](https://links.gtanet.com.br/zarakda51931) performance optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, Real-time reasoning is selected by default. This is enhanced for sustained traffic and [low latency](http://xrkorea.kr).
10. Review all configurations for precision. For this design, we highly recommend sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the model.<br>
<br>The release process can take numerous minutes to finish.<br>
<br>When deployment is total, your endpoint status will alter to InService. At this point, the model is prepared to accept reasoning requests through the endpoint. You can monitor the release development on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the release is total, you can conjure up the model using a SageMaker runtime client and incorporate 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 set up the SageMaker Python SDK and make certain you have the essential AWS permissions and environment setup. The following is a detailed code example that demonstrates how to release and [utilize](https://www.kenpoguy.com) DeepSeek-R1 for reasoning programmatically. The code for [releasing](https://git.agri-sys.com) the design is offered in the Github here. You can clone the note pad 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 likewise utilize 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 unwanted charges, finish the steps in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you deployed the design using Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace deployments.
2. In the Managed releases area, locate the endpoint you want to delete.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the right implementation: 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 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 checked out how you can access and release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker 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 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://boonbac.com) companies develop innovative options utilizing AWS [services](https://famenest.com) and sped up calculate. Currently, he is concentrated on establishing methods for fine-tuning and optimizing the inference performance of large [language](http://123.207.52.1033000) designs. In his complimentary time, [Vivek delights](http://47.104.6.70) in hiking, seeing movies, and trying various foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://namoshkar.com) Specialist Solutions Architect with the [Third-Party Model](https://upmasty.com) Science team at AWS. His location of focus is AWS [AI](http://47.100.220.92:10001) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer [Science](https://gamberonmusic.com) and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](https://gitlab.damage.run) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and [generative](https://miggoo.com.br) [AI](https://doop.africa) center. She is passionate about building solutions that help clients accelerate their [AI](https://yourrecruitmentspecialists.co.uk) journey and unlock service value.<br>