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

2025-02-17 04:14:58 +08:00 · 2025-02-17 04:14:58 +08:00 · d0c2ab864f
commit d0c2ab864f
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are thrilled to reveal that DeepSeek R1 distilled Llama and [Qwen designs](https://git.torrents-csv.com) are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://kuma.wisilicon.com:4000)'s first-generation frontier model, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion specifications to develop, experiment, and properly scale your generative [AI](https://git.hichinatravel.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 similar steps to deploy the distilled variations of the designs as well.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language design (LLM) established by DeepSeek [AI](https://gitlab-mirror.scale.sc) that uses support discovering to enhance thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. A crucial distinguishing feature is its support knowing (RL) step, which was utilized to improve the design's reactions beyond the standard pre-training and tweak process. By integrating RL, DeepSeek-R1 can adjust more successfully to user feedback and objectives, eventually boosting both significance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) technique, indicating it's equipped to break down intricate queries and reason through them in a detailed way. This assisted reasoning  allows the model to produce more accurate, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT abilities, aiming to produce structured reactions while concentrating on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has actually recorded the industry's attention as a versatile text-generation design that can be incorporated into various workflows such as representatives, rational reasoning and data interpretation jobs.<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 inference by routing inquiries to the most relevant specialist "clusters." This technique enables the model to focus on 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](http://www.isexsex.com) an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled designs bring the thinking [capabilities](https://oerdigamers.info) of the main R1 model to more efficient architectures based on [popular](http://163.66.95.1883001) open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller, more efficient designs to imitate the behavior and thinking patterns of the larger DeepSeek-R1 model, utilizing it as an instructor model.<br>
 <br>You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we recommend deploying this design with guardrails in location. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid harmful material, and [assess models](https://git.juxiong.net) against key security requirements. At the time of [writing](https://git.toolhub.cc) this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce multiple guardrails tailored to different use cases and  [surgiteams.com](https://surgiteams.com/index.php/User:Neville18E) use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative [AI](https://www.characterlist.com) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 design, you require access to an ml.p5e instance. To check if you have quotas for P5e, open the [Service Quotas](http://git.magic-beans.cn3000) console and under AWS Services,  [oeclub.org](https://oeclub.org/index.php/User:CarltonEichmann) choose Amazon SageMaker, and verify you're utilizing ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are deploying. To ask for a limitation boost, produce a limitation increase demand and connect to your account group.<br>
 <br>Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For guidelines, see Set up approvals to utilize guardrails for material filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>[Amazon Bedrock](https://peekz.eu) Guardrails allows you to present safeguards, avoid [damaging](http://168.100.224.793000) content, and examine models against key safety requirements. You can carry out precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and model responses released 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 circulation involves the following actions: First, the system receives 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 model for inference. After receiving the design's output, another [guardrail check](https://git.parat.swiss) is used. If the output passes this final check, it's returned as the [final result](https://body-positivity.org). However, if either the input or output is intervened by the guardrail,  [disgaeawiki.info](https://disgaeawiki.info/index.php/User:ShayV68172485519) a message is returned suggesting the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following sections demonstrate reasoning using this API.<br>
 <br>Deploy DeepSeek-R1 in [Amazon Bedrock](https://21fun.app) 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, 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 composing this post, you can use 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](https://gitlab.damage.run) and pick the DeepSeek-R1 model.<br>
 <br>The design detail page provides essential details about the design's capabilities, prices structure, and implementation guidelines. You can [discover](http://swwwwiki.coresv.net) detailed use instructions, including sample API calls and code snippets for combination. The model supports different text generation tasks, including material production, code generation, and question answering, using its support finding out optimization and CoT thinking capabilities.
 The page likewise includes deployment choices and licensing details to assist you get going with DeepSeek-R1 in your applications.
 3. To begin utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be [prompted](https://careers.indianschoolsoman.com) to configure the release details for DeepSeek-R1. The design ID will be pre-populated.
 4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
 5. For Variety of circumstances, enter a variety of circumstances (between 1-100).
 6. For example type, choose your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
 Optionally, you can set up advanced security and facilities settings, consisting of [virtual personal](https://papersoc.com) cloud (VPC) networking, service role permissions, and file encryption settings. For the [majority](https://www.hrdemployment.com) of utilize cases, the default settings will work well. However,  [yewiki.org](https://www.yewiki.org/User:IvyPerkin5053) for production deployments, you might desire to examine these settings to align with your organization's security and [compliance requirements](https://labz.biz).
 7. Choose Deploy to start using the design.<br>
 <br>When the implementation is complete, you can test DeepSeek-R1's capabilities straight in the Amazon Bedrock play area.
 8. Choose Open in play ground to access an interactive user interface where you can try out different triggers and adjust design parameters like temperature and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal results. For example, content for inference.<br>
 <br>This is an exceptional way to explore the model's reasoning and text generation abilities before integrating it into your applications. The playground provides instant feedback, assisting you understand how the model reacts to different inputs and letting you tweak your [prompts](http://47.119.128.713000) for optimal outcomes.<br>
 <br>You can rapidly test 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 reasoning utilizing guardrails with the [deployed](https://git.ombreport.info) DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to perform reasoning using a deployed DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can create a guardrail using 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, use the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures inference 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](https://ideezy.com) (ML) hub with FMs, integrated algorithms, and prebuilt ML services that you can release with simply a couple of clicks. With SageMaker JumpStart, you can [tailor pre-trained](https://demo.titikkata.id) designs to your usage case, with your data, and deploy them into production utilizing either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides two hassle-free approaches: using the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both techniques to assist you pick the technique that [finest matches](http://www.aiki-evolution.jp) 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 produce a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The model web browser shows available models, with details like the service provider name and model capabilities.<br>
 <br>4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card.
 Each model card reveals essential details, including:<br>
 <br>- Model name
 - Provider name
 - Task category (for example, Text Generation).
 Bedrock Ready badge (if appropriate), suggesting that this design can be registered with Amazon Bedrock, enabling you to use [Amazon Bedrock](http://modulysa.com) APIs to invoke the design<br>
 <br>5. Choose the model card to view the model details page.<br>
 <br>The design details page includes the following details:<br>
 <br>- The model name and provider details.
 Deploy button to deploy the model.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab consists of essential details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical specifications.
 - Usage guidelines<br>
 <br>Before you release the design, it's recommended to review the [model details](http://modulysa.com) and license terms to validate compatibility with your usage case.<br>
 <br>6. Choose Deploy to proceed with release.<br>
 <br>7. For [Endpoint](https://www.cdlcruzdasalmas.com.br) name, utilize the instantly generated name or produce a customized one.
 8. For example type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial circumstances count, get in the number of instances (default: 1).
 Selecting suitable instance types and counts is crucial for cost and efficiency optimization. Monitor 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 model, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
 11. Choose Deploy to deploy the design.<br>
 <br>The deployment process can take numerous minutes to finish.<br>
 <br>When release is total, your endpoint status will alter to InService. At this moment, the design is all set to accept inference requests through the [endpoint](https://test1.tlogsir.com). You can monitor the [implementation development](http://47.100.72.853000) on the SageMaker console Endpoints page, which will show 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 utilizing the [SageMaker Python](http://47.109.30.1948888) SDK<br>
 <br>To start with DeepSeek-R1 using the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the necessary AWS approvals and environment setup. The following is a detailed code example that demonstrates how to release and utilize DeepSeek-R1 for reasoning programmatically. The code for [deploying](http://106.15.41.156) the design is supplied in the Github here. You can clone the note pad and run from SageMaker Studio.<br>
 <br>You can run extra requests against the predictor:<br>
 <br>Implement guardrails and run inference with your SageMaker JumpStart predictor<br>
 <br>Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and [implement](https://git.i2edu.net) it as displayed in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent undesirable charges, finish the actions in this section to tidy up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace deployment<br>
 <br>If you released the design utilizing [Amazon Bedrock](http://122.51.51.353000) Marketplace, complete the following actions:<br>
 <br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace releases.
 2. In the [Managed implementations](https://git-dev.xyue.zip8443) section,  [wiki.whenparked.com](https://wiki.whenparked.com/User:LourdesJuergens) 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 deleting the appropriate release: 1. Endpoint name.
 2. Model name.
 3. Endpoint 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 delete 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](http://n-f-l.jp) how you can access and deploy the DeepSeek-R1 design utilizing [Bedrock Marketplace](https://radiothamkin.com) and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. 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 Starting with Amazon SageMaker JumpStart.<br>
 <br>About the Authors<br>
 <br>Vivek Gangasani is a Lead Specialist Solutions Architect for  [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:KatrinaPolding1) Inference at AWS. He assists emerging generative [AI](https://shareru.jp) business build ingenious services utilizing AWS services and sped up calculate. Currently, he is concentrated on developing methods for fine-tuning and optimizing the reasoning performance of big [language](http://gitlab.awcls.com) models. In his downtime, Vivek enjoys hiking, seeing movies, and attempting different cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://116.62.115.84:3000) Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area of focus is AWS [AI](https://gogs.xinziying.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](https://gmstaffingsolutions.com) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial [intelligence](https://git.owlhosting.cloud) and generative [AI](http://work.diqian.com:3000) center. She is enthusiastic about building solutions that assist consumers accelerate their [AI](http://git.365zuoye.com) journey and unlock service worth.<br>