Add DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart
commit
acc8828432
1 changed files with 93 additions and 0 deletions
|
|
@ -0,0 +1,93 @@
|
|||
<br>Today, we are [excited](https://www.hireprow.com) to reveal that DeepSeek R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://git.jishutao.com)'s first-generation frontier design, DeepSeek-R1, along with the [distilled versions](http://62.210.71.92) varying from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative [AI](http://git.superiot.net) concepts on AWS.<br>
|
||||
<br>In this post, we show how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and [SageMaker JumpStart](https://chancefinders.com). You can follow similar actions to release the distilled variations of the models as well.<br>
|
||||
<br>Overview of DeepSeek-R1<br>
|
||||
<br>DeepSeek-R1 is a large language model (LLM) established by DeepSeek [AI](https://evove.io) that utilizes support discovering to boost reasoning capabilities through a multi-stage training process from a DeepSeek-V3[-Base foundation](http://teamcous.com). A key differentiating feature is its reinforcement learning (RL) step, which was utilized to improve the design's responses beyond the basic pre-training and tweak procedure. By incorporating RL, DeepSeek-R1 can adjust better to user feedback and objectives, ultimately boosting both significance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, meaning it's geared up to break down complicated queries and reason through them in a detailed manner. This assisted reasoning procedure enables the model to produce more precise, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured actions while on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has actually recorded the industry's attention as a flexible text-generation design that can be incorporated into various workflows such as representatives, sensible reasoning and information analysis jobs.<br>
|
||||
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture enables activation of 37 billion specifications, allowing effective inference by routing queries to the most pertinent professional "clusters." This [technique permits](http://git.befish.com) the model to [specialize](http://revoltsoft.ru3000) in various issue domains while maintaining general 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 providing](http://8.134.61.1073000) 1128 GB of GPU memory.<br>
|
||||
<br>DeepSeek-R1 distilled designs bring the reasoning abilities of the main R1 model 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, more efficient models to imitate the habits and reasoning patterns of the larger DeepSeek-R1 design, utilizing it as a teacher design.<br>
|
||||
<br>You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest releasing this design with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and evaluate designs against crucial safety criteria. At the time of writing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can develop numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls throughout your generative [AI](http://git.aimslab.cn:3000) applications.<br>
|
||||
<br>Prerequisites<br>
|
||||
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e instance. To inspect if you have quotas for P5e, open the [Service Quotas](https://git.lotus-wallet.com) console and under AWS Services, pick Amazon SageMaker, and confirm you're using ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are releasing. To request a limitation boost, produce a [limitation boost](https://social.oneworldonesai.com) 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 proper AWS Identity and Gain Access To Management (IAM) authorizations to utilize Amazon Bedrock Guardrails. For guidelines, see Establish permissions to use guardrails for content filtering.<br>
|
||||
<br>Implementing guardrails with the ApplyGuardrail API<br>
|
||||
<br>Amazon Bedrock Guardrails enables you to present safeguards, avoid harmful material, and examine models against essential security requirements. You can execute precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to examine user inputs and model actions released on Amazon Bedrock [Marketplace](https://git.connectplus.jp) and SageMaker JumpStart. You can develop 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 involves the following steps: First, the system gets an input for the design. This input is then [processed](https://git.nullstate.net) through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the model for reasoning. After getting the model's output, another [guardrail check](https://centerfairstaffing.com) is used. If the output passes this last check, it's returned as the final outcome. 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 sections demonstrate inference utilizing this API.<br>
|
||||
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
|
||||
<br>Amazon Bedrock Marketplace offers you access to over 100 popular, [hb9lc.org](https://www.hb9lc.org/wiki/index.php/User:ZoraCintron60) emerging, and specialized foundation designs (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 models in the navigation pane.
|
||||
At the time of composing this post, you can utilize the InvokeModel API to invoke the design. It does not support Converse APIs and other Amazon Bedrock tooling.
|
||||
2. Filter for DeepSeek as a provider and choose the DeepSeek-R1 model.<br>
|
||||
<br>The design detail page offers vital details about the design's capabilities, prices structure, and application standards. You can find detailed usage instructions, consisting of sample API calls and code snippets for integration. The model supports numerous text generation tasks, consisting of material development, code generation, and question answering, using its [reinforcement learning](http://8.218.14.833000) optimization and CoT reasoning capabilities.
|
||||
The page likewise consists of implementation options and licensing details to assist you get going with DeepSeek-R1 in your applications.
|
||||
3. To start utilizing DeepSeek-R1, choose Deploy.<br>
|
||||
<br>You will be triggered to set up 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 Number of instances, enter a variety of [instances](http://106.55.234.1783000) (between 1-100).
|
||||
6. For Instance type, pick your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested.
|
||||
Optionally, you can set up advanced security and facilities settings, including virtual personal cloud (VPC) networking, service role permissions, and encryption settings. For many utilize cases, the default settings will work well. However, for production implementations, you might desire to examine these settings to align with your organization's security and compliance requirements.
|
||||
7. Choose Deploy to [start utilizing](https://www.diekassa.at) the model.<br>
|
||||
<br>When the deployment is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
|
||||
8. Choose Open in play ground to access an interactive user interface where you can experiment with different prompts and adjust model parameters like temperature and optimum length.
|
||||
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimal results. For instance, content for reasoning.<br>
|
||||
<br>This is an exceptional way to explore the model's reasoning and text generation capabilities before incorporating it into your applications. The playground offers immediate feedback, helping you comprehend how the model reacts to various inputs and letting you fine-tune your prompts for ideal outcomes.<br>
|
||||
<br>You can quickly check the model in the playground through the UI. However, to conjure up the deployed model programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
|
||||
<br>Run inference utilizing guardrails with the released DeepSeek-R1 endpoint<br>
|
||||
<br>The following code example demonstrates how to carry out reasoning utilizing a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. 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. After you have created the guardrail, [trademarketclassifieds.com](https://trademarketclassifieds.com/user/profile/2672496) use the following code to carry out guardrails. The script initializes the bedrock_runtime customer, sets up [inference](https://kaamdekho.co.in) parameters, and sends a demand to [produce text](https://denis.usj.es) based on a user prompt.<br>
|
||||
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
|
||||
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and prebuilt ML solutions that you can release with just a couple of 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 techniques: utilizing the instinctive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you select the method that best fits your needs.<br>
|
||||
<br>Deploy DeepSeek-R1 through [SageMaker JumpStart](https://sttimothysignal.org) UI<br>
|
||||
<br>Complete the following actions to deploy DeepSeek-R1 using SageMaker JumpStart:<br>
|
||||
<br>1. On the SageMaker console, choose Studio in the navigation pane.
|
||||
2. First-time users will be triggered to develop a domain.
|
||||
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
|
||||
<br>The model browser displays available designs, with [details](http://182.92.196.181) like the service provider name and design abilities.<br>
|
||||
<br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card.
|
||||
Each model card shows essential details, consisting of:<br>
|
||||
<br>- Model name
|
||||
- Provider name
|
||||
- Task classification (for example, Text Generation).
|
||||
Bedrock Ready badge (if relevant), suggesting that this model can be signed up with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to invoke the design<br>
|
||||
<br>5. Choose the design card to see the design details page.<br>
|
||||
<br>The model details page includes the following details:<br>
|
||||
<br>- The design name and supplier details.
|
||||
[Deploy button](https://gitea.mpc-web.jp) to release the model.
|
||||
About and Notebooks tabs with [detailed](https://119.29.170.147) details<br>
|
||||
<br>The About tab includes crucial details, such as:<br>
|
||||
<br>- Model description.
|
||||
- License details.
|
||||
- Technical requirements.
|
||||
- Usage guidelines<br>
|
||||
<br>Before you deploy the design, it's advised to review the design details and license terms to validate compatibility with your use case.<br>
|
||||
<br>6. Choose Deploy to proceed with release.<br>
|
||||
<br>7. For Endpoint name, utilize the immediately produced name or develop a custom one.
|
||||
8. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
|
||||
9. For Initial circumstances count, enter the variety of [circumstances](http://116.205.229.1963000) (default: 1).
|
||||
Selecting proper circumstances types and counts is crucial for expense and efficiency optimization. Monitor [setiathome.berkeley.edu](https://setiathome.berkeley.edu/view_profile.php?userid=11953342) your implementation to change these settings as needed.Under Inference type, Real-time inference is selected by default. This is enhanced for sustained traffic and low latency.
|
||||
10. Review all configurations for precision. For this design, we highly advise sticking to SageMaker JumpStart [default](https://vlogloop.com) settings and making certain that network isolation remains in [location](http://47.95.167.2493000).
|
||||
11. Choose Deploy to release the design.<br>
|
||||
<br>The release process can take a number of minutes to finish.<br>
|
||||
<br>When implementation is total, your endpoint status will change to InService. At this moment, the model is prepared to accept inference demands through the endpoint. You can keep an eye on the implementation development on the SageMaker console Endpoints page, which will [display](https://mission-telecom.com) pertinent metrics and status details. When the implementation is complete, you can invoke the model utilizing a SageMaker runtime customer and incorporate it with your applications.<br>
|
||||
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
|
||||
<br>To get begun with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to install 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 deploy and utilize DeepSeek-R1 for inference programmatically. The code for deploying the design is offered in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
|
||||
<br>You can run extra demands 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://pakfindjob.com) with your SageMaker JumpStart predictor. You can create a [guardrail utilizing](https://jollyday.club) the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
|
||||
<br>Clean up<br>
|
||||
<br>To avoid undesirable charges, finish the [actions](https://taar.me) in this area to tidy up your resources.<br>
|
||||
<br>Delete the [Amazon Bedrock](https://www.cowgirlboss.com) Marketplace implementation<br>
|
||||
<br>If you deployed the model utilizing Amazon Bedrock Marketplace, total the following actions:<br>
|
||||
<br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace implementations.
|
||||
2. In the Managed deployments area, find the endpoint you want 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 right deployment: 1. Endpoint name.
|
||||
2. Model name.
|
||||
3. [Endpoint](http://193.105.6.1673000) 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](https://fotobinge.pincandies.com) how you can access and release the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to start. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting started with Amazon SageMaker [JumpStart](https://git.io8.dev).<br>
|
||||
<br>About the Authors<br>
|
||||
<br>Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative [AI](https://gitea.v-box.cn) companies develop innovative solutions utilizing AWS services and accelerated calculate. Currently, he is focused on developing techniques for fine-tuning and optimizing the inference performance of large language designs. In his leisure time, Vivek takes pleasure in treking, watching motion pictures, and attempting various cuisines.<br>
|
||||
<br>Niithiyn Vijeaswaran is a Generative [AI](http://www.cl1024.online) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS [AI](https://www.imdipet-project.eu) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer [technology](http://47.105.104.2043000) and Bioinformatics.<br>
|
||||
<br>Jonathan Evans is an Expert Solutions Architect working on generative [AI](https://gitea.belanjaparts.com) with the Third-Party Model Science group at AWS.<br>
|
||||
<br>Banu Nagasundaram leads item, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://www.stormglobalanalytics.com) center. She is enthusiastic about constructing solutions that assist consumers accelerate their [AI](https://git.weingardt.dev) journey and unlock company worth.<br>
|
||||
Loading…
Reference in a new issue