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

master
Ashleigh Devine 2025-03-05 04:17:02 +08:00
commit c89120443f
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are thrilled to announce that DeepSeek R1 distilled Llama and Qwen models are available through [Amazon Bedrock](http://zhangsheng1993.tpddns.cn3000) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://lty.co.kr)'s first-generation [frontier](http://2.47.57.152) model, DeepSeek-R1, together with the distilled variations ranging from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative [AI](https://forum.tinycircuits.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 actions to release the distilled versions of the models too.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://wiki.rrtn.org) that uses support learning to [enhance](https://www.groceryshopping.co.za) reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential differentiating function is its support knowing (RL) action, which was used to fine-tune the design's actions beyond the standard pre-training and tweak process. By incorporating RL, [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:ShanelBergman33) DeepSeek-R1 can adjust more successfully to user feedback and objectives, [eventually boosting](http://47.119.175.53000) both significance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) technique, meaning it's equipped to break down complex inquiries and reason through them in a detailed manner. This assisted thinking process permits the model to produce more accurate, transparent, and [detailed responses](https://callingirls.com). This design combines RL-based fine-tuning with CoT capabilities, aiming to generate structured reactions while focusing on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has actually recorded the market's attention as a versatile text-generation model that can be incorporated into various workflows such as representatives, logical reasoning and data interpretation jobs.<br>
<br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture permits activation of 37 billion criteria, [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:TAHRena195267306) allowing efficient inference by routing queries to the most relevant expert "clusters." This method permits the model to focus on different problem 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 features 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning abilities 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 refers to a process of training smaller sized, [it-viking.ch](http://it-viking.ch/index.php/User:LillieYup4258164) more efficient models to mimic the habits and reasoning patterns of the bigger DeepSeek-R1 design, using 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 recommend releasing this design with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to [introduce](http://gogs.black-art.cn) safeguards, avoid hazardous material, and examine designs against essential security requirements. At the time of writing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, [Bedrock Guardrails](https://syndromez.ai) supports only the ApplyGuardrail API. You can create numerous guardrails tailored to various use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing security controls throughout your generative [AI](http://energonspeeches.com) applications.<br>
<br>Prerequisites<br>
<br>To deploy 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 verify you're using ml.p5e.48 xlarge for [endpoint usage](http://engineerring.net). 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, create a limitation boost demand and connect to your account team.<br>
<br>Because you will be [deploying](http://47.108.92.883000) this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) approvals to utilize Amazon Bedrock Guardrails. For guidelines, see Establish authorizations to use guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to present safeguards, prevent damaging material, and examine models against [essential](https://www.pakgovtnaukri.pk) security requirements. You can execute security measures for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This enables you to use guardrails to examine user inputs and design actions deployed 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 general flow [involves](https://www.hireprow.com) the following actions: First, the system gets an input for the design. This input is then processed through the [ApplyGuardrail API](https://job.duttainnovations.com). If the input passes the guardrail check, it's sent to the model for inference. After [receiving](http://zerovalueentertainment.com3000) the design's output, another [guardrail check](http://112.125.122.2143000) is used. If the output passes this final check, it's returned as the last [outcome](http://duberfly.com). However, if either the input or output is stepped in by the guardrail, a message is returned showing 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](https://taar.me) Marketplace<br>
<br>Amazon Bedrock Marketplace offers you access to over 100 popular, emerging, and specialized structure 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, [pick Model](https://novashop6.com) catalog 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](http://47.93.56.668080) APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and choose the DeepSeek-R1 model.<br>
<br>The model detail page offers essential details about the design's abilities, prices structure, and [implementation standards](https://www.goodbodyschool.co.kr). You can discover detailed use instructions, including sample API calls and code snippets for combination. The model supports different text generation jobs, consisting of material creation, code generation, and question answering, using its reinforcement learning optimization and CoT thinking abilities.
The page also consists of deployment options and licensing details to assist you start with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, pick Deploy.<br>
<br>You will be prompted to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (between 1-50 characters).
5. For Number of instances, enter a variety of circumstances (in between 1-100).
6. For Instance type, select your instance type. For optimum performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised.
Optionally, you can set up sophisticated security and [infrastructure](https://www.huntsrecruitment.com) settings, including virtual personal cloud (VPC) networking, service role consents, and encryption settings. For many utilize cases, the default settings will work well. However, for production implementations, you might want to examine these settings to align with your company's security and compliance requirements.
7. Choose Deploy to start utilizing the design.<br>
<br>When the deployment is complete, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
8. Choose Open in play area to access an interactive interface where you can experiment with different prompts and adjust design specifications like temperature and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum outcomes. For example, material for reasoning.<br>
<br>This is an excellent method to explore the model's thinking and [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:Alejandrina91B) text generation capabilities before incorporating it into your applications. The play area offers instant feedback, assisting you understand how the model reacts to numerous inputs and letting you fine-tune your triggers for ideal outcomes.<br>
<br>You can quickly evaluate the model in the play ground through the UI. However, to conjure up the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform inference utilizing a deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have actually created the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures inference parameters, and sends a demand to create text based upon a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and [wiki.snooze-hotelsoftware.de](https://wiki.snooze-hotelsoftware.de/index.php?title=Benutzer:AlexandriaSpina) prebuilt ML options that you can release with simply a couple of 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 offers two hassle-free methods: utilizing the intuitive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both techniques to assist you pick the approach that best matches your needs.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart 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 produce a domain.
3. On the SageMaker Studio console, select 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 model card.
Each design card shows crucial details, including:<br>
<br>- Model name
- Provider name
- Task category (for example, Text Generation).
[Bedrock Ready](https://lifefriendsurance.com) badge (if appropriate), indicating that this design can be registered with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the design card to view the design details page.<br>
<br>The model details page includes the following details:<br>
<br>- The model name and provider details.
Deploy button to release the design.
About and Notebooks tabs with detailed details<br>
<br>The About tab includes 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 evaluate the model details and license terms to verify compatibility with your usage case.<br>
<br>6. Choose Deploy to proceed with release.<br>
<br>7. For Endpoint name, utilize the instantly created name or produce a custom one.
8. For [Instance type](http://team.pocketuniversity.cn) ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, go into the number of instances (default: 1).
Selecting suitable circumstances types and counts is essential for cost and efficiency optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time inference is chosen by default. This is optimized for sustained traffic and [89u89.com](https://www.89u89.com/author/anh25846135/) low [latency](https://selfloveaffirmations.net).
10. Review all setups for accuracy. For this model, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to release the design.<br>
<br>The release procedure can take a number of minutes to finish.<br>
<br>When deployment is total, your endpoint status will alter to InService. At this point, the model is [prepared](https://shiatube.org) to accept reasoning demands through the endpoint. You can monitor the implementation progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the [release](https://mediawiki1334.00web.net) is total, you can conjure up the model utilizing a SageMaker runtime customer and incorporate it with your [applications](http://engineerring.net).<br>
<br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
<br>To start with DeepSeek-R1 using the SageMaker Python SDK, you will require 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 deploy and utilize DeepSeek-R1 for reasoning programmatically. The code for releasing the model is supplied in the Github here. You can clone the note pad and run from SageMaker Studio.<br>
<br>You can run additional demands against the predictor:<br>
<br>Implement guardrails and [yewiki.org](https://www.yewiki.org/User:EdwinaMcintire3) run [reasoning](http://111.160.87.828004) 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 create a guardrail using the Amazon Bedrock console or the API, and implement it as [revealed](http://rm.runfox.com) in the following code:<br>
<br>Tidy up<br>
<br>To prevent unwanted charges, complete the steps in this section to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace implementation<br>
<br>If you deployed 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, choose Marketplace releases.
2. In the Managed implementations section, find the endpoint you want to erase.
3. Select the endpoint, and on the Actions menu, [choose Delete](https://bethanycareer.com).
4. Verify the endpoint details to make certain you're erasing the appropriate deployment: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you deployed will sustain costs if you leave it running. Use the following code to erase 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 explored how you can access and release the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock [Marketplace](https://git.desearch.cc) now to start. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart [Foundation](https://wikitravel.org) 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://www.groceryshopping.co.za) business build [ingenious solutions](https://git.qingbs.com) using AWS services and sped up compute. Currently, he is concentrated on establishing techniques for fine-tuning and enhancing the inference efficiency of big language models. In his downtime, Vivek delights in treking, watching films, and trying different foods.<br>
<br>Niithiyn Vijeaswaran is a [Generative](https://bld.lat) [AI](https://223.130.175.147:6501) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](https://www.jobsalert.ai) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Professional Solutions Architect working on generative [AI](https://git.easytelecoms.fr) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://members.mcafeeinstitute.com) center. She is passionate about constructing options that assist clients accelerate their [AI](https://blogram.online) journey and unlock service value.<br>