kathibucher825/keliuyun
1
0
Code Issues Actions Packages Projects Wiki

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

Kathi Bucher 2025-02-21 11:02:19 +08:00
commit f3ea2883ad
1 changed files with 93 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart.-.md Normal file

@ -0,0 +1,93 @@
<br>Today, we are thrilled to reveal that DeepSeek R1 [distilled Llama](https://manilall.com) and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://oakrecruitment.uk)'s first-generation frontier model, DeepSeek-R1, together with the distilled variations ranging from 1.5 to 70 billion criteria to build, experiment, and responsibly scale your generative [AI](https://e-sungwoo.co.kr) concepts on AWS.<br>
<br>In this post, we show how to get started with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to deploy the distilled versions of the models as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) developed by DeepSeek [AI](https://service.lanzainc.xyz:10281) that utilizes reinforcement learning to improve reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential identifying function is its reinforcement learning (RL) action, which was used to fine-tune the model's actions beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adjust better to user feedback and goals, eventually enhancing both significance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, indicating it's equipped to break down complicated questions and reason through them in a detailed manner. This assisted thinking process allows the model to produce more precise, transparent, and detailed responses. This design combines RL-based fine-tuning with CoT abilities, aiming to create structured responses while concentrating on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has actually caught the industry's attention as a versatile text-generation design that can be incorporated into various workflows such as representatives, rational reasoning and information interpretation jobs.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion parameters, [enabling efficient](https://projectblueberryserver.com) reasoning by routing inquiries to the most relevant expert "clusters." This method enables the design to focus on different issue domains while maintaining general performance. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning capabilities of the main R1 design to more effective architectures based on [popular](https://93.177.65.216) open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller sized, more efficient models to simulate the behavior and thinking patterns of the bigger DeepSeek-R1 design, using it as an instructor model.<br>
<br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we [advise releasing](https://git.googoltech.com) this model with guardrails in location. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent harmful content, and evaluate models against [crucial security](https://hesdeadjim.org) criteria. At the time of writing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, [Bedrock Guardrails](https://centerdb.makorang.com) supports only the ApplyGuardrail API. You can create multiple guardrails tailored to various use cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls across your generative [AI](https://inamoro.com.br) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 design, you require access to an ml.p5e circumstances. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and confirm you're [utilizing](https://aggm.bz) ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 [xlarge instance](https://gitea.star-linear.com) in the AWS Region you are deploying. To request a limitation boost, produce a limit boost demand and connect to your account group.<br>
<br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) consents to utilize Amazon Bedrock Guardrails. For directions, see Set up authorizations to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails permits you to introduce safeguards, [prevent damaging](https://gamberonmusic.com) material, and assess designs against key safety requirements. You can carry out precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and design actions released on Marketplace and SageMaker JumpStart. You can produce a [guardrail utilizing](http://47.122.66.12910300) the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.<br>
<br>The basic flow involves the following steps: First, the system gets an input for the model. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent to the design for reasoning. After getting the design's output, another guardrail check is used. 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 indicating the nature of the intervention and whether it happened at the input or output stage. 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 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 brochure under Foundation models in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to [conjure](https://golz.tv) up the model. It doesn't [support Converse](https://git.uzavr.ru) APIs and other Amazon Bedrock tooling.
2. Filter for [DeepSeek](https://farmwoo.com) as a provider and select the DeepSeek-R1 model.<br>
<br>The model detail page supplies important details about the model's abilities, prices structure, and execution guidelines. You can find detailed usage instructions, including sample API calls and code snippets for integration. The model supports different text generation jobs, consisting of material development, code generation, and [question](https://yaseen.tv) answering, using its reinforcement learning optimization and CoT thinking abilities.
The page likewise includes release options and licensing details to assist you start with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, choose Deploy.<br>
<br>You will be prompted to set up the deployment details for DeepSeek-R1. The design ID will be [pre-populated](https://gitea.portabledev.xyz).
4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
5. For Number of circumstances, enter a variety of circumstances (in between 1-100).
6. For Instance type, select your circumstances 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 private cloud (VPC) networking, [service function](https://globviet.com) permissions, and file encryption settings. For most use cases, the default settings will work well. However, for production deployments, you may wish to evaluate these settings to align with your company's security and [compliance requirements](https://www.nas-store.com).
7. Choose Deploy to start using the design.<br>
<br>When the deployment is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock playground.
8. Choose Open in play area to access an interactive interface where you can explore different prompts and change design specifications like temperature and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal outcomes. For example, content for inference.<br>
<br>This is an outstanding method to check out the model's thinking and text generation capabilities before integrating it into your applications. The play area provides immediate feedback, assisting you [understand](https://youslade.com) how the [design reacts](https://xevgalex.ru) to numerous inputs and letting you [fine-tune](https://higgledy-piggledy.xyz) your prompts for optimal outcomes.<br>
<br>You can quickly test the model in the playground through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform inference utilizing a deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail utilizing the [Amazon Bedrock](http://101.34.66.2443000) console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning criteria, and sends a demand to generate text based on a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub 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 designs to your usage case, with your data, and deploy them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 design through SageMaker JumpStart uses two [convenient](https://suomalainennaikki.com) techniques: utilizing the intuitive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both methods to help you choose the approach that best matches your needs.<br>
<br>Deploy DeepSeek-R1 through [SageMaker JumpStart](https://teba.timbaktuu.com) UI<br>
<br>Complete the following steps to deploy DeepSeek-R1 utilizing SageMaker JumpStart:<br>
<br>1. On the SageMaker console, choose Studio in the navigation pane.
2. First-time users will be prompted to create a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The model browser displays available models, with details like the supplier name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card shows crucial details, including:<br>
<br>- Model name
- Provider name
- Task classification (for instance, Text Generation).
Bedrock Ready badge (if appropriate), showing that this design can be registered with Amazon Bedrock, allowing 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 service provider [details](https://manilall.com).
[Deploy button](https://apk.tw) to deploy 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 specs.
- Usage standards<br>
<br>Before you deploy the model, it's suggested to examine the model details and license terms to confirm compatibility with your usage case.<br>
<br>6. Choose Deploy to proceed with release.<br>
<br>7. For Endpoint name, use the [automatically](https://www.hammerloop.com) created name or develop a customized one.
8. For example type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, go into the variety of instances (default: 1).
Selecting proper circumstances types and counts is crucial for cost and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is [enhanced](http://8.134.38.1063000) for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we highly suggest sticking to SageMaker JumpStart default settings and making certain that network isolation remains in place.
11. Choose Deploy to deploy the model.<br>
<br>The implementation process can take a number of minutes to complete.<br>
<br>When implementation is total, your endpoint status will change to InService. At this point, the model is prepared to accept inference requests through the endpoint. You can monitor the release progress on the [SageMaker](http://101.34.66.2443000) console Endpoints page, which will display pertinent metrics and status details. When the implementation is total, you can invoke the model utilizing a SageMaker runtime customer and integrate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To get started with DeepSeek-R1 using the SageMaker Python SDK, you will need 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 deploy and use DeepSeek-R1 for inference programmatically. The code for deploying the model is offered 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 inference with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can likewise use the [ApplyGuardrail API](https://kition.mhl.tuc.gr) with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and [implement](https://champ217.flixsterz.com) it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To avoid undesirable charges, finish the steps in this area to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you deployed the design using Amazon Bedrock Marketplace, complete the following actions:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace releases.
2. In the Managed releases area, find the [endpoint](https://git.kairoscope.net) 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 proper release: 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 erase the [endpoint](http://58.87.67.12420080) 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](https://hayhat.net) the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, describe 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 helps emerging generative [AI](http://thinking.zicp.io:3000) companies construct innovative options using AWS services and sped up calculate. Currently, he is concentrated on establishing techniques for fine-tuning and enhancing the inference performance of large language models. In his downtime, Vivek delights in treking, watching films, and attempting different foods.<br>
<br>Niithiyn Vijeaswaran is a [Generative](http://secretour.xyz) [AI](https://www.weben.online) Specialist Solutions Architect with the Third-Party [Model Science](https://ec2-13-237-50-115.ap-southeast-2.compute.amazonaws.com) team at AWS. His area of focus is AWS [AI](https://superappsocial.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
<br>Jonathan Evans is an Expert Solutions Architect working on generative [AI](http://git.info666.com) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, [links.gtanet.com.br](https://links.gtanet.com.br/sharidarr65) engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and [generative](https://git.wheeparam.com) [AI](https://koubry.com) hub. She is passionate about building options that assist clients accelerate their [AI](https://www.nas-store.com) journey and unlock company value.<br>