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

2025-04-03 01:59:47 +08:00 · 2025-04-03 01:59:47 +08:00 · 148c8b2dc2
commit 148c8b2dc2
parent 4ec437d127
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 announce that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](http://sdongha.com)'s first-generation frontier model, DeepSeek-R1, in addition to the distilled versions varying from 1.5 to 70 billion criteria to develop, experiment, and responsibly scale your generative [AI](https://sublimejobs.co.za) ideas on AWS.<br>
 <br>In this post, we show how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable actions to deploy the distilled versions of the designs too.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a large language model (LLM) developed by DeepSeek [AI](http://stream.appliedanalytics.tech) that utilizes support finding out to improve reasoning capabilities through a multi-stage training [process](https://rosaparks-ci.com) from a DeepSeek-V3-Base structure. A crucial differentiating function is its support learning (RL) step, which was used to fine-tune the design's actions beyond the standard pre-training and tweak procedure. By including RL, DeepSeek-R1 can adjust more successfully to user [feedback](https://truejob.co) and goals, [eventually boosting](http://114.115.138.988900) both [relevance](https://git.iidx.ca) and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) approach,  [pediascape.science](https://pediascape.science/wiki/User:JosephCreswick1) implying it's geared up to break down complicated inquiries and reason through them in a detailed way. This assisted thinking process enables the model to produce more accurate, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT capabilities, aiming to generate structured actions while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has recorded the industry's attention as a versatile text-generation design that can be integrated into different workflows such as agents, sensible reasoning and information interpretation jobs.<br>
 <br>DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion parameters, [allowing effective](https://gogs.les-refugies.fr) reasoning by routing queries to the most relevant specialist "clusters." This technique permits the design to concentrate on various issue domains while maintaining overall efficiency. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for inference. 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 offering 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 model to more effective architectures based on popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a [process](https://ari-sound.aurumai.io) of training smaller sized, more efficient designs to mimic the behavior and thinking patterns of the bigger DeepSeek-R1 model, utilizing it as an instructor model.<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, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid harmful content, and evaluate designs against essential security criteria. At the time of composing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop numerous guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls throughout your [generative](https://47.98.175.161) [AI](https://www.tmip.com.tr) applications.<br>
 <br>Prerequisites<br>
 <br>To release the DeepSeek-R1 model, you require access to an ml.p5e instance. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose 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 circumstances in the AWS Region you are releasing. To ask for a limitation increase, develop a limitation boost demand and reach out to your account group.<br>
 <br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) authorizations to utilize Amazon Bedrock Guardrails. For instructions, see Set up permissions to use guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails enables you to present safeguards, prevent harmful content, and examine designs against essential security requirements. You can carry out safety procedures for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to [apply guardrails](https://followmylive.com) to assess user inputs and design actions released on [Amazon Bedrock](https://code.linkown.com) Marketplace and SageMaker JumpStart. You can develop 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 includes the following actions: First, the system gets an input for the model. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the design for inference. After getting the design's output, another guardrail check is used. If the output passes this last check, it's returned as the final outcome. However, if either the input or output is intervened by the guardrail, a message is [returned](https://drshirvany.ir) showing the nature of the intervention and whether it occurred 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 Marketplace<br>
 <br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized foundation designs (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, pick Model brochure under Foundation designs in the navigation pane.
 At the time of composing this post, you can utilize the InvokeModel API to conjure up the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
 2. Filter for DeepSeek as a company and pick the DeepSeek-R1 model.<br>
 <br>The model detail page provides important [details](https://www.mudlog.net) about the design's abilities, prices structure, and execution guidelines. You can [discover](https://ratemywifey.com) detailed use directions, including sample API calls and code snippets for integration. The model supports different text generation jobs, consisting of content creation, code generation, and question answering, utilizing its reinforcement finding out optimization and CoT thinking abilities.
 The page likewise includes deployment options and licensing details to assist you start with DeepSeek-R1 in your applications.
 3. To begin using DeepSeek-R1, choose Deploy.<br>
 <br>You will be triggered to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
 5. For Variety of circumstances, enter a number of instances (in between 1-100).
 6. For Instance type, choose your instance type. For ideal [performance](http://release.rupeetracker.in) with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
 Optionally, you can set up innovative security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service function consents, and encryption settings. For many use cases, the default settings will work well. However, for production implementations, you may want to review these [settings](http://8.130.52.45) to align with your company's security and compliance requirements.
 7. Choose Deploy to start utilizing the model.<br>
 <br>When the release is total, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
 8. Choose Open in playground to access an interactive interface where you can try out different triggers and adjust model specifications like temperature level and optimum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimum outcomes. For instance, material for inference.<br>
 <br>This is an excellent method to check out the design's reasoning and  [wakewiki.de](https://www.wakewiki.de/index.php?title=Benutzer:AlexWoolnough3) text generation capabilities before integrating it into your applications. The play ground supplies instant feedback, helping you comprehend how the design reacts to different inputs and letting you fine-tune your prompts for ideal outcomes.<br>
 <br>You can rapidly test the model in the play ground through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
 <br>Run [inference utilizing](http://180.76.133.25316300) guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to carry out reasoning using 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 [develop](http://gitlab.together.social) the guardrail, see the GitHub repo. After you have actually produced the guardrail, use the following code to implement guardrails. The script initializes the bedrock_runtime customer, sets up reasoning specifications, and sends out a demand 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 algorithms, and prebuilt ML solutions that you can release with just a few clicks. With SageMaker JumpStart, you can [tailor pre-trained](http://112.124.19.388080) models to your use 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 2 convenient techniques: using the user-friendly SageMaker [JumpStart UI](http://xn--o39aoby1e85nw4rx0fwvcmubsl71ekzf4w4a.kr) or executing programmatically through the [SageMaker Python](http://www.jedge.top3000) SDK. Let's explore both techniques to help you select the [approach](http://47.107.80.2363000) that finest matches your needs.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following actions to deploy DeepSeek-R1 utilizing SageMaker JumpStart:<br>
 <br>1. On the SageMaker console, select Studio in the navigation pane.
 2. First-time users will be triggered to create a domain.
 3. On the SageMaker Studio console, select JumpStart in the navigation pane.<br>
 <br>The model web browser displays available designs, with details like the company name and model abilities.<br>
 <br>4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card.
 Each model card reveals key details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task classification (for example, Text Generation).
 Bedrock Ready badge (if suitable), suggesting that this model can be registered with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to conjure up the model<br>
 <br>5. Choose the design card to view the design details page.<br>
 <br>The design details page consists of the following details:<br>
 <br>- The design name and company details.
 Deploy button to release the model.
 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 recommended to examine the model details and license terms to confirm compatibility with your use case.<br>
 <br>6. Choose Deploy to proceed with implementation.<br>
 <br>7. For Endpoint name, utilize the automatically created name or create a custom-made one.
 8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, go into the number of circumstances (default: 1).
 Selecting suitable instance types and counts is vital for expense and performance optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time reasoning is chosen by . This is enhanced for [sustained traffic](http://destruct82.direct.quickconnect.to3000) and low latency.
 10. Review all setups for accuracy. For this model, we strongly recommend 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 deployment process can take several minutes to complete.<br>
 <br>When [deployment](http://162.14.117.2343000) is complete, your endpoint status will alter to InService. At this point, the model is all set to accept inference demands through the endpoint. You can keep an eye on the implementation 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 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](http://www.thynkjobs.com) to set up the SageMaker Python SDK and make certain you have the necessary AWS consents 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](https://www.teacircle.co.in) 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 also utilize 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 displayed in the following code:<br>
 <br>Tidy up<br>
 <br>To avoid undesirable charges, complete the actions in this section to tidy up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace release<br>
 <br>If you released the model using Amazon Bedrock Marketplace, complete 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 deployments section, locate 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 erasing 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 costs if you leave it [running](https://germanjob.eu). Use the following code to delete the endpoint if you want to stop [sustaining charges](https://git.esc-plus.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 deploy 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 pretrained models, Amazon SageMaker JumpStart Foundation Models, [Amazon Bedrock](http://www.xn--1-2n1f41hm3fn0i3wcd3gi8ldhk.com) 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://git.novisync.com) business build ingenious options utilizing AWS services and sped up calculate. Currently,  [wakewiki.de](https://www.wakewiki.de/index.php?title=Benutzer:ErnieHollins) he is concentrated on establishing methods for fine-tuning and enhancing the reasoning performance of big language models. In his leisure time, Vivek enjoys hiking, enjoying movies, and [attempting](https://www.punajuaj.com) various foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://www.a34z.com) Specialist Solutions Architect with the Third-Party Model [Science team](https://webloadedsolutions.com) at AWS. His area of focus is AWS [AI](https://integramais.com.br) 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://git.lolilove.rs) with the Third-Party Model [Science](https://teba.timbaktuu.com) group at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon [SageMaker](http://8.137.58.203000) JumpStart, SageMaker's artificial intelligence and generative [AI](https://git.emalm.com) center. She is enthusiastic about developing options that help consumers accelerate their [AI](http://47.90.83.132:3000) journey and unlock organization value.<br>