marcellajenkin/jobsleed
1
0
Code Issues Actions Packages Projects Wiki

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

Marcella Jenkinson 2025-02-07 08:03:47 +08:00
commit 60b62100f1
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 delighted to announce that DeepSeek R1 distilled Llama and [Qwen designs](https://photohub.b-social.co.uk) are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](https://git.wyling.cn)'s first-generation frontier model, DeepSeek-R1, in addition to the [distilled variations](https://photohub.b-social.co.uk) ranging from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative [AI](https://www.tippy-t.com) concepts 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 comparable steps to release the distilled variations of the models as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) developed by [DeepSeek](http://careers.egylifts.com) [AI](https://git.polycompsol.com:3000) that uses reinforcement discovering to enhance thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. A crucial identifying function is its reinforcement learning (RL) step, which was utilized to fine-tune the model's responses beyond the basic pre-training and tweak process. By incorporating RL, DeepSeek-R1 can adapt more successfully to user feedback and goals, ultimately enhancing both importance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, indicating it's [equipped](https://community.cathome.pet) to break down [complex questions](http://gitea.digiclib.cn801) and factor through them in a detailed way. This assisted reasoning procedure permits the design to produce more accurate, transparent, and detailed answers. This model integrates [RL-based](http://47.106.205.1408089) fine-tuning with CoT capabilities, aiming to generate structured reactions while concentrating on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has actually [captured](https://gitlab.ngser.com) the market's attention as a flexible [text-generation design](http://116.62.145.604000) that can be incorporated into various workflows such as representatives, rational reasoning and data analysis jobs.<br>
<br>DeepSeek-R1 utilizes a [Mixture](https://git.vicagroup.com.cn) of Experts (MoE) architecture and is 671 billion [criteria](https://47.98.175.161) in size. The MoE architecture enables activation of 37 billion parameters, enabling effective reasoning by routing questions to the most relevant expert "clusters." This approach allows the model to concentrate on various problem domains while maintaining total performance. DeepSeek-R1 requires at least 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 model. ml.p5e.48 xlarge comes with 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 efficient architectures based upon 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 effective designs to imitate the habits and thinking patterns of the larger DeepSeek-R1 model, utilizing it as a teacher design.<br>
<br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we advise releasing this design with guardrails in location. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent harmful content, and evaluate models against key safety criteria. At the time of composing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce several guardrails tailored to different use cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls throughout your generative [AI](https://git.ivran.ru) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, you require access to an ml.p5e [instance](http://www.lebelleclinic.com). To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, [larsaluarna.se](http://www.larsaluarna.se/index.php/User:DominickJulian9) select Amazon SageMaker, and confirm you're using ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are releasing. To ask for a limitation increase, develop a [limitation boost](https://academia.tripoligate.com) demand and connect to your account team.<br>
<br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the right AWS [Identity](http://175.178.113.2203000) and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For instructions, see Set up to utilize guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails [permits](https://rabota.newrba.ru) you to introduce safeguards, avoid damaging content, and evaluate models against key safety criteria. You can implement precaution for the DeepSeek-R1 model [utilizing](https://gitea.blubeacon.com) the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to examine user inputs and design reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.<br>
<br>The basic flow involves the following actions: 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 inference. After receiving the model'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 stepped in by the guardrail, a message is returned showing the nature of the [intervention](https://teba.timbaktuu.com) and whether it took place 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](http://funnydollar.ru) Marketplace<br>
<br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of composing this post, you can utilize the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a service provider and pick the DeepSeek-R1 design.<br>
<br>The design detail page provides necessary details about the model's capabilities, pricing structure, and application guidelines. You can discover detailed use guidelines, including sample API calls and code bits for integration. The design supports numerous text generation jobs, consisting of content production, code generation, and question answering, using its reinforcement discovering optimization and CoT thinking abilities.
The page likewise consists of implementation alternatives and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, choose Deploy.<br>
<br>You will be triggered to configure the deployment details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
5. For Number of circumstances, go into a variety of instances (between 1-100).
6. For Instance type, [kousokuwiki.org](http://kousokuwiki.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:AnkeStarnes867) pick your instance type. For optimum efficiency 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 authorizations, and file encryption settings. For many use cases, the default settings will work well. However, for production releases, you may want to examine these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to begin using the design.<br>
<br>When the deployment is total, you can test DeepSeek-R1's capabilities 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 change design parameters like temperature and maximum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum outcomes. For instance, material for reasoning.<br>
<br>This is an excellent way to explore the design's thinking and text generation capabilities before integrating it into your applications. The play area supplies immediate feedback, assisting you understand how the model reacts to numerous inputs and letting you tweak your triggers for ideal results.<br>
<br>You can rapidly check the design in the play ground through the UI. However, to invoke the deployed design [programmatically](https://gitea.chofer.ddns.net) with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform reasoning using a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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 actually created the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, sets up reasoning parameters, and sends a demand to create [text based](http://117.72.39.1253000) 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 information, and deploy them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides two convenient techniques: using the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's explore both techniques to help you select the approach that best suits your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following actions to release DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the SageMaker console, pick Studio in the navigation pane.
2. [First-time](http://lstelecom.co.kr) users will be triggered to create a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The design browser shows available designs, with details like the provider name and model abilities.<br>
<br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 [design card](https://www.lotusprotechnologies.com).
Each design card reveals crucial details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if suitable), suggesting that this model can be registered with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the design<br>
<br>5. Choose the model card to view the design details page.<br>
<br>The design details page includes the following details:<br>
<br>- The design name and company details.
[Deploy button](https://git.pawott.de) to release the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab consists of essential details, such as:<br>
<br>- Model description.
- License details.
- Technical specs.
- Usage standards<br>
<br>Before you release 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 implementation.<br>
<br>7. For Endpoint name, utilize the [instantly produced](https://easterntalent.eu) name or produce a custom one.
8. For example type ¸ choose a [circumstances type](https://redebrasil.app) (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the variety of circumstances (default: 1).
Selecting suitable instance types and counts is [crucial](http://yanghaoran.space6003) for [surgiteams.com](https://surgiteams.com/index.php/User:KaseyDees635) cost and efficiency optimization. Monitor your release to change these settings as needed.Under Inference type, Real-time reasoning is selected by default. This is optimized for sustained traffic and low latency.
10. Review all configurations for accuracy. For this design, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to deploy the model.<br>
<br>The release procedure can take numerous minutes to complete.<br>
<br>When deployment is complete, your endpoint status will alter to InService. At this moment, the model is prepared to accept reasoning requests through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the release is complete, you can invoke the model utilizing a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To begin with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the [SageMaker Python](https://www.stormglobalanalytics.com) SDK and make certain you have the required AWS permissions and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for inference programmatically. The code for deploying the model is supplied in the Github here. You can clone the note pad and run 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 develop a guardrail utilizing the Amazon Bedrock console or the API, and execute it as shown in the following code:<br>
<br>Clean up<br>
<br>To prevent unwanted charges, finish the actions in this area to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace release<br>
<br>If you deployed the model utilizing Amazon Bedrock Marketplace, total the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace deployments.
2. In the Managed implementations area, find the endpoint you wish to delete.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you're erasing the proper release: 1. [Endpoint](https://gitea.uchung.com) 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 if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.<br>
<br>Conclusion<br>
<br>In this post, we explored how you can access and deploy the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to start. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting started 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://167.172.148.93:4433) companies develop innovative solutions using AWS services and sped up calculate. Currently, he is concentrated on establishing strategies for fine-tuning and enhancing the inference performance of big language designs. In his downtime, Vivek delights in hiking, watching films, and trying different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://gitea.ashcloud.com) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](https://sodam.shop) [accelerators](https://www.nairaland.com) (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](https://www.goodbodyschool.co.kr) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://syndromez.ai) center. She is passionate about constructing solutions that assist customers accelerate their [AI](https://schoolmein.com) journey and unlock service value.<br>