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

2025-04-07 01:58:23 +08:00
parent d4dacb2633
commit 38629e880d
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are delighted to reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://www.tcrew.be)'s first-generation frontier model, DeepSeek-R1, in addition to the distilled versions varying from 1.5 to 70 billion [specifications](https://bitca.cn) to develop,  [photorum.eclat-mauve.fr](http://photorum.eclat-mauve.fr/profile.php?id=222535) experiment, and responsibly scale your generative [AI](https://git.yinas.cn) 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 deploy the distilled versions of the models as well.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](https://www.meditationgoodtip.com) that uses support learning to improve thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base [structure](https://codecraftdb.eu). A key identifying function is its support knowing (RL) action, which was utilized to fine-tune the design's responses beyond the standard pre-training and fine-tuning procedure. By integrating RL, DeepSeek-R1 can adjust more efficiently to user [feedback](https://www.pkgovtjobz.site) and goals, eventually improving both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, implying it's equipped to break down intricate queries and factor through them in a detailed manner. This directed thinking procedure permits the design to produce more accurate, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured responses while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually captured the [market's attention](https://sound.descreated.com) as a flexible text-generation model that can be integrated into different workflows such as agents, sensible reasoning and data interpretation tasks.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture enables activation of 37 billion parameters, making it possible for [efficient inference](https://kittelartscollege.com) by routing inquiries to the most relevant specialist "clusters." This approach enables the model to focus on different issue domains while maintaining total efficiency. DeepSeek-R1 requires 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 model. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 model to more efficient architectures based on 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 effective designs to mimic the [behavior](https://code.lanakk.com) and  [wiki.snooze-hotelsoftware.de](https://wiki.snooze-hotelsoftware.de/index.php?title=Benutzer:FaustinoMayberry) reasoning patterns of the larger DeepSeek-R1 model, utilizing it as a teacher design.<br>
 <br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest deploying this model with guardrails in location. In this blog site, we will use Amazon Bedrock Guardrails to present safeguards, [prevent damaging](https://ezworkers.com) content, and assess models against key safety requirements. At the time of writing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing security controls throughout your generative [AI](https://hektips.com) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you need access to an ml.p5e instance. To inspect if you have quotas for P5e, open the Service Quotas [console](https://spudz.org) and under AWS Services, select Amazon SageMaker,  [forum.altaycoins.com](http://forum.altaycoins.com/profile.php?id=1089808) and [validate](http://lohashanji.com) you're utilizing 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 limit boost, [develop](https://gitea.oio.cat) a [limit increase](https://ourehelp.com) demand and reach out to your account team.<br>
 <br>Because you will be releasing this model with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) consents to utilize Amazon Bedrock Guardrails. For guidelines, see Establish approvals to utilize guardrails for material filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails allows you to present safeguards, avoid harmful content, and examine models against essential security criteria. You can execute precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to examine user inputs and design responses released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo.<br>
 <br>The general circulation 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 out to the design for reasoning. After receiving the model's output, another guardrail check is used. If the output passes this final check, it's returned as the result. However, if either the input or output is intervened by the guardrail, a message is returned showing the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following sections show reasoning using this API.<br>
 <br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
 <br>Amazon Bedrock  provides you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To [gain access](https://www.roednetwork.com) to DeepSeek-R1 in Amazon Bedrock, total the following actions:<br>
 <br>1. On the Amazon Bedrock console, pick Model catalog under Foundation models in the navigation pane.
 At the time of writing this post, you can utilize the InvokeModel API to invoke the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a provider and select the DeepSeek-R1 design.<br>
 <br>The model detail page offers essential details about the design's capabilities, rates structure, and application standards. You can discover detailed usage instructions, consisting of sample API calls and code snippets for integration. The model supports numerous [text generation](https://freelyhelp.com) tasks, including material creation, code generation, and [question](https://redmonde.es) answering, using its reinforcement discovering optimization and CoT reasoning abilities.
 The page likewise includes release options and licensing details to help you start with DeepSeek-R1 in your applications.
 3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be triggered to configure the release details for DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, go into an endpoint name (between 1-50 [alphanumeric](https://workforceselection.eu) characters).
 5. For Variety of instances, enter a number of instances (in between 1-100).
 6. For example type, select your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
 Optionally, you can set up innovative security and infrastructure settings, consisting of virtual private cloud (VPC) networking, service function permissions, and encryption [settings](http://121.43.99.1283000). For most utilize cases, the default settings will work well. However, for production implementations, you may desire to review these settings to align with your organization's security and compliance requirements.
 7. Choose Deploy to begin using the design.<br>
 <br>When the deployment is complete, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
 8. Choose Open in play ground to access an interactive interface where you can try out different prompts and adjust model parameters like temperature level and maximum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for ideal outcomes. For example, content for inference.<br>
 <br>This is an excellent way to explore the design's thinking and text generation capabilities before incorporating it into your applications. The playground provides instant feedback, assisting you comprehend how the model responds to different inputs and letting you fine-tune your prompts for optimal results.<br>
 <br>You can rapidly evaluate the model in the play area through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs,  [raovatonline.org](https://raovatonline.org/author/antoniocope/) 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 inference utilizing a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have [developed](https://alumni.myra.ac.in) the guardrail, use the following code to [implement guardrails](http://175.6.40.688081). The script initializes the bedrock_runtime customer, sets up reasoning parameters, and sends out a request to produce text based upon 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 [services](https://oros-git.regione.puglia.it) that you can [release](http://106.14.174.2413000) with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your usage case, with your information, and release them into production utilizing either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides two practical methods: utilizing the user-friendly SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you pick the approach that finest fits 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, choose Studio in the navigation pane.
 2. First-time users will be prompted to create a domain.
 3. On the SageMaker Studio console, choose JumpStart in the navigation pane.<br>
 <br>The design web browser shows available models, with details like the company name and model capabilities.<br>
 <br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
 Each design card shows essential details, including:<br>
 <br>- Model name
 - Provider name
 - [Task classification](http://xn--289an1ad92ak6p.com) (for instance, Text Generation).
 Bedrock Ready badge (if suitable), indicating that this model can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to conjure up the design<br>
 <br>5. Choose the model card to view the model details page.<br>
 <br>The design details page consists of the following details:<br>
 <br>- The model name and company details.
 Deploy button to release the design.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab consists of important details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical requirements.
 - 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 usage case.<br>
 <br>6. Choose Deploy to continue with implementation.<br>
 <br>7. For Endpoint name, utilize the automatically generated name or produce a customized one.
 8. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, enter the variety of instances (default: 1).
 Selecting suitable instance types and counts is important for cost and performance optimization. Monitor your deployment to change these settings as needed.Under [Inference](https://www.flughafen-jobs.com) type, [Real-time inference](http://122.51.17.902000) is chosen by [default](https://hotjobsng.com). This is optimized for sustained traffic and low latency.
 10. Review all setups for accuracy. For this model, we highly advise adhering to SageMaker JumpStart default settings and making certain that network isolation remains in place.
 11. Choose Deploy to release the model.<br>
 <br>The implementation process can take several minutes to complete.<br>
 <br>When deployment is total, your endpoint status will alter to InService. At this moment, the model is prepared to accept inference demands through the endpoint. You can monitor  [hb9lc.org](https://www.hb9lc.org/wiki/index.php/User:CoyFreehill) the implementation progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the implementation is total, you can conjure up the design using a SageMaker runtime customer and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To get going with DeepSeek-R1 using the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the required AWS [approvals](https://guridentwell.com) 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 notebook and run from SageMaker Studio.<br>
 <br>You can run [additional](https://code.karsttech.com) requests against the predictor:<br>
 <br>Implement guardrails and run reasoning 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 avoid unwanted charges, complete the steps in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace implementation<br>
 <br>If you released the model using Amazon Bedrock Marketplace, complete 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 section, locate the endpoint you want to delete.
 3. Select the endpoint, and on the Actions menu, [choose Delete](http://compass-framework.com3000).
 4. Verify the endpoint details to make certain you're deleting the appropriate implementation: 1. Endpoint name.
 2. Model name.
 3. Endpoint status<br>
 <br>Delete the [SageMaker JumpStart](http://modulysa.com) predictor<br>
 <br>The SageMaker JumpStart 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](https://www.diltexbrands.com). 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 design utilizing Bedrock Marketplace and SageMaker JumpStart. [Visit SageMaker](https://sportsprojobs.net) JumpStart in [SageMaker Studio](https://gitlab.informicus.ru) or Amazon Bedrock Marketplace now to begin. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Beginning 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](http://222.121.60.403000) generative [AI](https://git.amic.ru) business develop ingenious solutions using AWS services and sped up compute. Currently, he is focused on developing techniques for fine-tuning and optimizing the inference performance of big language models. In his complimentary time, Vivek takes pleasure in treking, enjoying films, and trying various foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://gitea.pi.cr4.live) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](http://124.222.85.139:3000) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is an Expert Solutions Architect dealing with generative [AI](https://diversitycrejobs.com) with the Third-Party Model [Science](https://drshirvany.ir) group at AWS.<br>
 <br>Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](http://jobshut.org) hub. She is passionate about developing options that assist customers accelerate their [AI](http://124.222.181.150:3000) journey and unlock company value.<br>