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

master
Ada Wiles 2025-04-03 12:23:36 +00:00
parent 604cefb8dd
commit e61ac7d090
1 changed files with 93 additions and 0 deletions

@ -0,0 +1,93 @@
<br>Today, we are delighted to announce that DeepSeek R1 distilled Llama and Qwen designs are available through [Amazon Bedrock](http://121.37.208.1923000) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](https://93.177.65.216)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions ranging from 1.5 to 70 billion specifications to build, experiment, and responsibly scale your generative [AI](http://president-park.co.kr) [concepts](https://www.passadforbundet.se) 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 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://www.paradigmrecruitment.ca) that utilizes reinforcement discovering to boost reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key identifying feature is its reinforcement knowing (RL) action, which was utilized to refine the model's reactions beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adapt more effectively to user [feedback](https://guyanajob.com) and goals, eventually improving both importance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, implying it's geared up to break down complex queries and reason through them in a detailed way. This assisted reasoning process permits the design to produce more precise, transparent, and [detailed answers](http://gogs.kexiaoshuang.com). This model integrates RL-based fine-tuning with CoT abilities, aiming to produce structured responses while concentrating on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has recorded the market's attention as a flexible text-generation model that can be integrated into numerous workflows such as representatives, logical reasoning and information interpretation jobs.<br>
<br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion criteria, making it possible for efficient reasoning by routing queries to the most relevant expert "clusters." This method enables the model to concentrate on different problem domains while maintaining overall effectiveness. 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 model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the reasoning capabilities of the main R1 model to more efficient architectures based upon popular open models like Qwen (1.5 B, [wiki.lafabriquedelalogistique.fr](https://wiki.lafabriquedelalogistique.fr/Discussion_utilisateur:ColumbusOden971) 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller, more efficient models to mimic the behavior and reasoning 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 model, we advise releasing this model with guardrails in location. In this blog, we will use Amazon Bedrock [Guardrails](http://dev.nextreal.cn) to present safeguards, prevent hazardous content, and examine designs against essential safety 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](http://api.cenhuy.com3000) several guardrails tailored to different use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing security controls throughout your generative [AI](https://fewa.hudutech.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you require access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas [console](http://120.24.213.2533000) and under AWS Services, select Amazon SageMaker, and confirm 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](http://193.105.6.1673000). To ask for a limitation increase, create a limitation increase request and reach out to your account team.<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](https://www.hb9lc.org) (IAM) consents to utilize Amazon Bedrock Guardrails. For guidelines, see Establish authorizations to use guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails enables you to present safeguards, [prevent](https://tageeapp.com) damaging material, and [evaluate models](http://gitlab.adintl.cn) against essential security requirements. You can execute safety [procedures](https://uconnect.ae) for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to evaluate user inputs and model actions deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create 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 receives an input for the design. This input is then processed through the [ApplyGuardrail API](https://gitea.phywyj.dynv6.net). If the input passes the guardrail check, it's sent out to the design for inference. After receiving the design's output, another guardrail check is used. If the output passes this final check, it's returned as the outcome. However, if either the input or output is [stepped](https://jandlfabricating.com) in by the guardrail, a message is returned showing the nature of the intervention and whether it occurred at the input or [output phase](https://test.manishrijal.com.np). The examples showcased in the following sections show inference utilizing this API.<br>
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
<br>Amazon Bedrock Marketplace gives 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 actions:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can utilize the [InvokeModel API](http://git.bplt.ru) to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a [supplier](https://pojelaime.net) and choose the DeepSeek-R1 model.<br>
<br>The model detail page offers vital details about the design's capabilities, pricing structure, and execution standards. You can discover detailed use directions, consisting of sample API calls and code snippets for integration. The design supports different text generation jobs, consisting of content development, code generation, and concern answering, utilizing its support discovering optimization and CoT reasoning abilities.
The page also consists of implementation alternatives and licensing details to assist you get begun with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, pick Deploy.<br>
<br>You will be prompted to configure the release details for DeepSeek-R1. The design ID will be pre-populated.
4. For [Endpoint](http://chichichichichi.top9000) name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of instances, enter a variety of circumstances (between 1-100).
6. For Instance type, choose your instance type. For optimum performance with DeepSeek-R1, a [GPU-based circumstances](http://haiji.qnoddns.org.cn3000) type like ml.p5e.48 xlarge is suggested.
Optionally, you can set up advanced security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service role consents, and file encryption settings. For many use cases, the default settings will work well. However, for production implementations, you might desire to examine these settings to line up 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 evaluate 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 triggers and adjust design specifications like temperature level and maximum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for ideal results. For example, material for reasoning.<br>
<br>This is an excellent way to check out the model's thinking and text generation capabilities before integrating it into your applications. The playground offers instant feedback, assisting you understand how the design reacts to numerous inputs and letting you tweak your prompts for optimal results.<br>
<br>You can [rapidly test](https://rca.co.id) the design in the play area through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run reasoning using guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform inference using a [released](https://guyanajob.com) DeepSeek-R1 design 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 develop the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning parameters, and sends out a demand to create text 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, built-in algorithms, and prebuilt ML options that you can release with just a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your data, and deploy them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart uses two convenient methods: utilizing the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you choose the technique that best fits your requirements.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps 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 create a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.<br>
<br>The design internet browser displays available models, with details like the service provider name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 design card.
Each design card reveals crucial details, including:<br>
<br> name
- Provider name
- [Task classification](https://www.thewaitersacademy.com) (for example, Text Generation).
Bedrock Ready badge (if appropriate), showing that this model can be signed up with Amazon Bedrock, enabling you to utilize Amazon Bedrock APIs to conjure up the model<br>
<br>5. Choose the design card to see the design details page.<br>
<br>The [design details](http://124.71.40.413000) page includes the following details:<br>
<br>- The design name and company details.
Deploy button to release the design.
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 release the design, it's recommended to evaluate the model details and license terms to confirm compatibility with your use case.<br>
<br>6. Choose Deploy to proceed with deployment.<br>
<br>7. For Endpoint name, use the automatically generated name or produce a customized one.
8. For example type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the variety of instances (default: 1).
Selecting proper [circumstances](https://twitemedia.com) types and counts is important for expense and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference type, Real-time reasoning is picked by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for accuracy. For this model, we highly suggest sticking to [SageMaker JumpStart](http://poscotech.co.kr) default settings and making certain that network isolation remains in place.
11. Choose Deploy to release the model.<br>
<br>The implementation procedure can take several minutes to finish.<br>
<br>When release is total, your [endpoint status](https://code.nwcomputermuseum.org.uk) will change to InService. At this point, the design is all set to accept inference demands through the [endpoint](https://seconddialog.com). You can keep an eye on the deployment progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the deployment is complete, you can conjure up the model utilizing a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To get begun with DeepSeek-R1 using the SageMaker Python SDK, [hb9lc.org](https://www.hb9lc.org/wiki/index.php/User:BiancaRosenberge) you will require to set up the SageMaker Python SDK and make certain you have the needed AWS permissions and environment setup. The following is a detailed code example that demonstrates how to release and use DeepSeek-R1 for reasoning programmatically. The code for releasing 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 reasoning 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 produce a [guardrail utilizing](http://git.meloinfo.com) the Amazon Bedrock console or the API, and execute it as displayed in the following code:<br>
<br>Clean up<br>
<br>To prevent unwanted charges, complete the actions in this section to clean up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you deployed the design utilizing Amazon Bedrock Marketplace, total the following actions:<br>
<br>1. On the Amazon [Bedrock](http://49.50.103.174) console, under Foundation designs in the navigation pane, choose Marketplace releases.
2. In the Managed deployments section, locate the endpoint you want to erase.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the appropriate implementation: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you released will sustain expenses if you leave it running. Use the following code to erase the endpoint if you want to stop sustaining charges. For more details, see [Delete Endpoints](https://wiki.openwater.health) and Resources.<br>
<br>Conclusion<br>
<br>In this post, we checked out 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 get begun. 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](http://106.15.48.1323880) Solutions Architect for Inference at AWS. He helps emerging generative [AI](http://kyeongsan.co.kr) companies build ingenious options utilizing AWS services and accelerated compute. Currently, he is concentrated on establishing strategies for fine-tuning and enhancing the reasoning efficiency of big language models. In his complimentary time, [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:BrandyGriffiths) Vivek takes pleasure in treking, watching movies, and trying different cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](http://94.191.73.38:3000) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](http://www.grainfather.de) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect working on generative [AI](https://git.ombreport.info) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://carrieresecurite.fr) hub. She is enthusiastic about developing services that help customers accelerate their [AI](https://aji.ghar.ku.jaldi.nai.aana.ba.tume.dont.tach.me) journey and unlock organization value.<br>