aishahateley3/gps-hunter
1
0
Code Issues Actions Packages Projects Wiki

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

Aisha Hateley 2025-04-10 04:10:17 +08:00
commit df92cf036b
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 announce that DeepSeek R1 distilled Llama and Qwen designs are available through [Amazon Bedrock](https://upmasty.com) Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://121.36.37.70:15501)'s first-generation frontier model, DeepSeek-R1, in addition to the distilled variations ranging from 1.5 to 70 billion [specifications](https://hortpeople.com) to develop, experiment, and properly scale your [generative](http://pyfup.com3000) [AI](https://fassen.net) [concepts](http://zaxx.co.jp) 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 versions of the models as well.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) developed by DeepSeek [AI](https://startuptube.xyz) that uses reinforcement learning to enhance reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A crucial differentiating function is its reinforcement knowing (RL) step, which was used to improve the design's actions beyond the standard pre-training and tweak procedure. By incorporating RL, DeepSeek-R1 can adapt more effectively to user feedback and goals, ultimately enhancing both importance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) technique, implying it's geared up to break down intricate questions and factor through them in a detailed way. This directed reasoning procedure permits the model to produce more precise, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT capabilities, aiming to generate structured responses while concentrating on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has actually captured the industry's attention as a versatile text-generation model that can be incorporated into different workflows such as representatives, rational reasoning and data interpretation tasks.<br>
<br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture allows activation of 37 billion specifications, allowing effective reasoning by routing queries to the most appropriate specialist "clusters." This approach allows the design to specialize in various problem domains while maintaining overall performance. DeepSeek-R1 requires at least 800 GB of [HBM memory](https://careerworksource.org) in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge circumstances to deploy the model. ml.p5e.48 xlarge features 8 Nvidia H200 [GPUs providing](http://194.87.97.823000) 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 design to more effective architectures based upon popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more efficient models to mimic the behavior and thinking patterns of the larger DeepSeek-R1 design, utilizing it as a teacher model.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we advise releasing this design with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous material, and assess designs against essential security requirements. At the time of writing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing safety controls throughout your generative [AI](https://camtalking.com) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 design, you require access to an ml.p5e instance. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, select Amazon SageMaker, and validate you're utilizing 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 deploying. To request a limit increase, create a limit increase request and reach out to your account team.<br>
<br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the appropriate AWS [Identity](https://git.watchmenclan.com) and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For guidelines, see Establish permissions to use guardrails for material filtering.<br>
<br>Implementing [guardrails](https://ckzink.com) with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails allows you to present safeguards, prevent hazardous material, and evaluate designs against essential safety requirements. You can implement precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to assess user inputs and design responses deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo.<br>
<br>The basic flow includes the following steps: First, the system gets an input for the design. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent to the model for reasoning. After getting the model's output, another guardrail check is applied. If the output passes this final check, it's returned as the [outcome](https://www.tiger-teas.com). However, if either the input or output is stepped in by the guardrail, a message is returned indicating the nature of the [intervention](https://lius.familyds.org3000) and whether it occurred at the input or [output stage](https://infinirealm.com). The [examples](http://lophas.com) showcased in the following sections demonstrate [reasoning](https://gitea.sprint-pay.com) 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 foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, select Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can use the InvokeModel API to [conjure](https://pediascape.science) up the design. It does not support Converse APIs and other Amazon Bedrock [tooling](https://codes.tools.asitavsen.com).
2. Filter for DeepSeek as a company and pick the DeepSeek-R1 design.<br>
<br>The design detail page offers necessary details about the design's capabilities, pricing structure, and application guidelines. You can discover detailed use instructions, consisting of sample API calls and code bits for combination. The [design supports](https://tubevieu.com) different text generation jobs, including content production, code generation, and question answering, using its reinforcement learning optimization and CoT reasoning capabilities.
The page likewise includes deployment alternatives and licensing details to help you begin with DeepSeek-R1 in your [applications](https://westzoneimmigrations.com).
3. To begin using DeepSeek-R1, choose 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 name, go into an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of instances, get in a number of circumstances (between 1-100).
6. For example type, choose your instance type. For ideal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up advanced security and facilities settings, consisting of virtual personal cloud (VPC) networking, service role consents, and file encryption settings. For a lot of utilize cases, the default settings will work well. However, for production deployments, you may wish to review these settings to line up with your company's security and [compliance requirements](https://fogel-finance.org).
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 play ground to access an interactive user interface where you can experiment with different prompts and adjust design parameters like temperature level and maximum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimum results. For example, material for inference.<br>
<br>This is an excellent method to check out the model's thinking and text generation capabilities before incorporating it into your applications. The play ground offers instant feedback, helping you understand how the model reacts to different inputs and letting you fine-tune your triggers for ideal results.<br>
<br>You can quickly check the model in the play ground through the UI. However, to conjure up the released design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example shows how to perform reasoning utilizing a deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can [produce](https://ipmanage.sumedangkab.go.id) a guardrail using the Amazon Bedrock console or [wavedream.wiki](https://wavedream.wiki/index.php/User:Jada43H59015) the API. For the example code to create the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to carry out guardrails. The script initializes the bedrock_runtime customer, sets up reasoning parameters, and sends a request to create text based on a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) center with FMs, [built-in](http://192.241.211.111) algorithms, and prebuilt ML options that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your information, and release them into production using either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart offers 2 hassle-free techniques: utilizing the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's explore both methods to help you choose the approach that best suits your requirements.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following actions to deploy DeepSeek-R1 using SageMaker JumpStart:<br>
<br>1. On the SageMaker console, pick Studio in the navigation pane.
2. First-time users will be triggered to develop a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
<br>The model browser shows available models, with details like the provider name and design capabilities.<br>
<br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each design card reveals key details, including:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if appropriate), suggesting that this design can be registered with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to [conjure](http://sgvalley.co.kr) up the design<br>
<br>5. Choose the design card to view the design details page.<br>
<br>The design details page includes the following details:<br>
<br>- The model name and service provider .
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](https://git.muehlberg.net).
- Technical specs.
- Usage guidelines<br>
<br>Before you release the model, it's recommended to evaluate the design details and license terms to verify compatibility with your use case.<br>
<br>6. Choose Deploy to [continue](https://iamzoyah.com) with release.<br>
<br>7. For [Endpoint](http://wp10476777.server-he.de) name, utilize the immediately produced name or create a custom one.
8. For Instance type ¸ select an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the number of circumstances (default: 1).
Selecting appropriate circumstances types and counts is important for expense and efficiency optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is optimized for sustained traffic and low latency.
10. Review all setups for precision. For this design, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network isolation remains in place.
11. Choose Deploy to deploy the design.<br>
<br>The release procedure can take numerous minutes to finish.<br>
<br>When implementation is complete, your endpoint status will alter to InService. At this point, the model is prepared to accept reasoning requests through the endpoint. You can monitor the implementation development on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the implementation is complete, you can conjure up the design using a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using 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 essential 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 range from SageMaker Studio.<br>
<br>You can run additional demands against the predictor:<br>
<br>Implement guardrails and run inference with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail using the Amazon Bedrock console or the API, and execute it as revealed in the following code:<br>
<br>Tidy up<br>
<br>To [prevent unwanted](https://smaphofilm.com) charges, complete the steps in this section to tidy up your [resources](https://demo.playtubescript.com).<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you released the design 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 implementations.
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 deleting the right deployment: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The [SageMaker JumpStart](http://47.97.161.14010080) design you released will sustain costs if you leave it running. Use the following code to delete 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 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 start. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, [SageMaker JumpStart](https://161.97.85.50) pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going 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://mastercare.care) companies build ingenious services using AWS services and sped up compute. Currently, he is focused on establishing techniques for fine-tuning and enhancing the reasoning performance of big language models. In his totally free time, Vivek takes pleasure in hiking, enjoying films, and attempting different cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://videobox.rpz24.ir) Specialist Solutions Architect with the [Third-Party Model](https://phoebe.roshka.com) Science team at AWS. His location of focus is AWS [AI](https://kiwiboom.com) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.<br>
<br>Jonathan Evans is a Specialist Solutions Architect dealing with generative [AI](http://charmjoeun.com) with the Third-Party Model Science team at AWS.<br>
<br>[Banu Nagasundaram](https://gitlab.oc3.ru) leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, [forum.pinoo.com.tr](http://forum.pinoo.com.tr/profile.php?id=1330524) SageMaker's artificial intelligence and generative [AI](http://128.199.175.152:9000) center. She is enthusiastic about developing services that help customers accelerate their [AI](https://thestylehitch.com) journey and unlock business worth.<br>