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

2025-02-07 01:50:55 +08:00 · 2025-02-07 01:50:55 +08:00 · 71e382daac
commit 71e382daac
1 changed files with 93 additions and 0 deletions
--- a/JumpStart.-.md
+++ b/JumpStart.-.md
@ -0,0 +1,93 @@
 <br>Today, we are excited to announce that DeepSeek R1 [distilled Llama](https://www.ajirazetu.tz) and Qwen models are available through Amazon Bedrock [Marketplace](https://gitlab.radioecca.org) and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](https://kaamdekho.co.in)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled versions varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative [AI](http://vk-mix.ru) [concepts](https://sossdate.com) 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 similar actions to release the distilled versions of the models too.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a big language model (LLM) developed by DeepSeek [AI](https://git.fpghoti.com) that uses reinforcement discovering to improve thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential differentiating feature is its support knowing (RL) step, which was utilized to fine-tune the model's responses beyond the standard pre-training and fine-tuning process. By incorporating RL, DeepSeek-R1 can adapt better to user feedback and goals, ultimately boosting both relevance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, implying it's equipped to break down complicated inquiries and factor through them in a detailed way. This assisted reasoning process permits the model to produce more precise, transparent, and detailed responses. This design combines RL-based fine-tuning with CoT capabilities, aiming to generate structured [reactions](http://git.z-lucky.com90) while focusing on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has captured the market's attention as a flexible text-generation design that can be integrated into numerous workflows such as agents, logical thinking and [data interpretation](http://orcz.com) jobs.<br>
 <br>DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion specifications, enabling efficient reasoning by routing inquiries to the most relevant expert "clusters." This technique permits the design to concentrate on various problem domains while [maintaining](https://jobdd.de) 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](https://git.uucloud.top) to deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled designs bring the reasoning abilities of the main R1 design to more efficient architectures based upon popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and  [genbecle.com](https://www.genbecle.com/index.php?title=Utilisateur:JulieBrower730) Llama (8B and 70B). Distillation describes a process of training smaller sized, more efficient designs to mimic the behavior and thinking patterns of the bigger DeepSeek-R1 design, using it as a teacher model.<br>
 <br>You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend releasing this model with guardrails in location. In this blog site, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging content, and examine designs against crucial safety requirements. At the time of composing this blog site, for DeepSeek-R1 deployments on [SageMaker JumpStart](https://git.xutils.co) and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create several guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls throughout your generative [AI](https://manchesterunitedfansclub.com) [applications](https://dztrader.com).<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 model, you need access to an ml.p5e instance. To inspect 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 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](https://gitlab.ucc.asn.au) this model with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To [Management](https://git.limework.net) (IAM) permissions to [utilize Amazon](https://git.guaranteedstruggle.host) Bedrock Guardrails. For instructions, see Set up permissions 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 damaging content, and assess models against crucial security [criteria](http://193.200.130.1863000). You can carry out safety steps for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to evaluate user inputs and design reactions 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 general flow involves the following actions: First, the system receives an input for the model. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent 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 final result. However, if either the input or output is stepped in by the guardrail,  [bytes-the-dust.com](https://bytes-the-dust.com/index.php/User:LindseyWalstab9) a message is returned suggesting the nature of the intervention and whether it took place at the input or output stage. The examples [showcased](https://git.guaranteedstruggle.host) in the following sections demonstrate [reasoning utilizing](http://39.99.134.1658123) this API.<br>
 <br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
 <br>Amazon Bedrock Marketplace provides you access to over 100 popular, emerging,  [surgiteams.com](https://surgiteams.com/index.php/User:EdenCota769) and specialized foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:<br>
 <br>1. On the Amazon Bedrock console, select Model catalog under Foundation designs in the navigation pane.
 At the time of composing this post, you can use the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock [tooling](http://ieye.xyz5080).
 2. Filter for DeepSeek as a supplier and pick the DeepSeek-R1 design.<br>
 <br>The model detail page offers essential details about the design's capabilities, rates structure, and implementation standards. You can find detailed usage directions, consisting of sample API calls and code bits for combination. The design supports various text  tasks, consisting of content creation, code generation, and concern answering, utilizing its support learning optimization and CoT thinking capabilities.
 The page also includes release options and licensing details to assist you get going with DeepSeek-R1 in your applications.
 3. To start utilizing DeepSeek-R1, choose Deploy.<br>
 <br>You will be prompted to configure the [deployment details](http://89.234.183.973000) for DeepSeek-R1. The design ID will be pre-populated.
 4. For Endpoint name, get in an endpoint name (in between 1-50 alphanumeric characters).
 5. For Number of instances, go into a variety of instances (in between 1-100).
 6. For example type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
 Optionally, you can set up sophisticated security and facilities settings, consisting of virtual personal cloud (VPC) networking, service function 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 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 release is total, you can evaluate DeepSeek-R1's capabilities straight in the Amazon Bedrock playground.
 8. Choose Open in play ground to access an interactive interface where you can try out different triggers and change model parameters like temperature and maximum length.
 When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for ideal outcomes. For instance, material for inference.<br>
 <br>This is an outstanding way to explore the design's reasoning and text generation abilities before incorporating it into your applications. The play ground supplies immediate feedback, helping you understand how the model reacts to numerous inputs and [letting](http://betterlifenija.org.ng) you fine-tune your triggers for ideal results.<br>
 <br>You can rapidly check the design in the play ground 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 inference utilizing guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example demonstrates how to carry out inference using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and [ApplyGuardrail API](https://ruraltv.in). 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 created the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures reasoning criteria, and sends a demand to produce 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, integrated algorithms, and prebuilt ML solutions that you can release with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your usage case, with your information, and release them into [production](https://rna.link) using either the UI or SDK.<br>
 <br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 convenient approaches: utilizing the instinctive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both techniques to assist you pick the approach that [finest fits](https://pittsburghtribune.org) your needs.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following actions to release DeepSeek-R1 utilizing 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, pick JumpStart in the navigation pane.<br>
 <br>The model browser displays available designs, with details like the supplier name and model capabilities.<br>
 <br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
 Each model card reveals essential details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task classification (for instance, Text Generation).
 [Bedrock Ready](https://git.vhdltool.com) badge (if relevant), suggesting that this design can be registered with Amazon Bedrock, [enabling](https://analyticsjobs.in) you to utilize Amazon Bedrock APIs to invoke the design<br>
 <br>5. Choose the model card to see the design details page.<br>
 <br>The design details page consists of the following details:<br>
 <br>- The design name and service provider details.
 Deploy button to deploy the model.
 About and Notebooks tabs with detailed details<br>
 <br>The About tab consists of crucial details, such as:<br>
 <br>- Model description.
 - License details.
 - Technical specifications.
 - Usage standards<br>
 <br>Before you deploy the model, it's recommended to review the [design details](http://59.110.125.1643062) and license terms to validate compatibility with your usage case.<br>
 <br>6. Choose Deploy to continue with implementation.<br>
 <br>7. For Endpoint name, utilize the immediately created name or create a custom one.
 8. For example type ¸ select an instance type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, enter the [variety](http://47.97.161.14010080) of instances (default: 1).
 Selecting appropriate circumstances types and counts is vital for cost and performance optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time inference is picked by default. This is optimized for sustained traffic and low latency.
 10. Review all configurations for precision. For this model, we highly advise [sticking](http://git.keliuyun.com55676) to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
 11. Choose Deploy to release the design.<br>
 <br>The release procedure can take a number of minutes to complete.<br>
 <br>When release is complete, your endpoint status will change to InService. At this moment, the model is prepared to accept inference demands through the endpoint. You can keep track of the implementation progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the deployment is complete, you can invoke the design utilizing a SageMaker runtime customer and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 utilizing the SageMaker Python SDK<br>
 <br>To get started with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to set up 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 inference programmatically. The code for releasing the model is supplied in the Github here. You can clone the note pad and range from SageMaker Studio.<br>
 <br>You can run extra demands against the predictor:<br>
 <br>Implement [guardrails](https://wiki.eqoarevival.com) and run reasoning with your SageMaker JumpStart predictor<br>
 <br>Similar to Amazon Bedrock, you can likewise use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail utilizing the Amazon Bedrock console or  [wiki.dulovic.tech](https://wiki.dulovic.tech/index.php/User:FidelBatt531106) the API, and implement it as shown in the following code:<br>
 <br>Tidy up<br>
 <br>To prevent unwanted charges, finish the steps in this area to tidy up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace deployment<br>
 <br>If you deployed the design using Amazon Bedrock Marketplace, complete the following actions:<br>
 <br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
 2. In the Managed releases section, locate the endpoint you desire 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 proper deployment: 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. Use the following code to delete the endpoint if you want 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 deploy the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, 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 helps emerging generative [AI](https://suprabullion.com) business construct innovative services using AWS services and accelerated calculate. Currently, he is concentrated on [developing strategies](http://124.221.76.2813000) for fine-tuning and optimizing the reasoning performance of large language models. In his leisure time, Vivek takes pleasure in hiking, viewing films, and trying different foods.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](https://vids.nickivey.com) Specialist Solutions Architect with the [Third-Party Model](https://git.rungyun.cn) [Science](http://orcz.com) group at AWS. His area of focus is AWS [AI](http://team.pocketuniversity.cn) 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://analyticsjobs.in) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and [generative](https://letustalk.co.in) [AI](https://www.noagagu.kr) center. She is passionate about constructing solutions that help clients accelerate their [AI](https://git.muehlberg.net) journey and unlock company worth.<br>