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

2025-02-17 04:15:09 +08:00 · 2025-02-17 04:15:09 +08:00 · 3b4abcc65f
commit 3b4abcc65f
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 designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek [AI](http://lohashanji.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled versions ranging from 1.5 to 70 billion specifications to build, experiment, and responsibly scale your generative [AI](https://cdltruckdrivingcareers.com) ideas on AWS.<br>
 <br>In this post, we demonstrate 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 as well.<br>
 <br>Overview of DeepSeek-R1<br>
 <br>DeepSeek-R1 is a large language design (LLM) established by DeepSeek [AI](https://dlya-nas.com) that uses reinforcement discovering to boost reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key [distinguishing feature](https://51.68.46.170) is its reinforcement learning (RL) action, which was utilized to fine-tune the design's responses beyond the basic pre-training and tweak [procedure](http://woorichat.com). By incorporating RL, DeepSeek-R1 can adjust more efficiently to user feedback and goals, ultimately enhancing both significance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) technique, implying it's equipped to break down intricate queries and factor through them in a detailed way. This guided thinking process 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 actions while focusing on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has captured the market's attention as a [versatile](https://63game.top) text-generation model that can be integrated into various workflows such as agents, sensible thinking and data interpretation jobs.<br>
 <br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion criteria, making it possible for effective inference by routing queries to the most appropriate specialist "clusters." This approach enables the model to concentrate on different issue domains while maintaining total performance. 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 instance to deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
 <br>DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 design to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller sized, more effective designs to [imitate](https://www.xafersjobs.com) the behavior and thinking 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 model, we advise releasing this model with guardrails in place. In this blog site, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid harmful content, and evaluate designs against crucial safety criteria. At the time of writing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create numerous guardrails tailored to different usage cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls across your generative [AI](https://asromafansclub.com) applications.<br>
 <br>Prerequisites<br>
 <br>To deploy the DeepSeek-R1 model, you require access to an ml.p5e [circumstances](http://120.92.38.24410880). To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and validate you're using ml.p5e.48 xlarge for [endpoint usage](https://posthaos.ru). Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To ask for a limitation boost, develop a limitation increase request and connect to your account group.<br>
 <br>Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the correct AWS [Identity](http://grainfather.co.uk) and Gain Access To [Management](https://avpro.cc) (IAM) approvals to use Amazon Bedrock Guardrails. For instructions, see Establish authorizations to utilize guardrails for content filtering.<br>
 <br>Implementing guardrails with the ApplyGuardrail API<br>
 <br>Amazon Bedrock Guardrails permits you to introduce safeguards, prevent harmful material, and examine models against crucial security criteria. You can implement precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to evaluate user inputs and design reactions 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 create the guardrail, see the [GitHub repo](https://code.oriolgomez.com).<br>
 <br>The general circulation includes the following actions: 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 inference. After receiving the design's output, another guardrail check is used. If the output passes this final check, it's returned as the last result. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the [intervention](https://bcde.ru) and whether it took place at the input or output phase. The examples showcased in the following sections 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 structure 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, select Model catalog under Foundation designs in the navigation pane.
 At the time of [writing](https://git.lodis.se) this post, you can utilize the InvokeModel API to conjure up the design. It doesn't support Converse APIs and other Amazon Bedrock [tooling](http://ecoreal.kr).
 2. Filter for DeepSeek as a service provider and select the DeepSeek-R1 model.<br>
 <br>The design detail page provides essential details about the model's abilities, pricing structure, and execution guidelines. You can discover detailed use instructions, including sample API calls and code snippets for integration. The design supports various text generation jobs, including content creation, code generation, and concern answering, using its reinforcement learning optimization and CoT reasoning abilities.
 The page also includes implementation options and licensing details to help you begin with DeepSeek-R1 in your applications.
 3. To start utilizing DeepSeek-R1, pick Deploy.<br>
 <br>You will be triggered to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
 4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters).
 5. For Number of instances, enter a number of instances (between 1-100).
 6. For example type, choose your circumstances type. For ideal performance with DeepSeek-R1, a [GPU-based instance](https://www.usbstaffing.com) type like ml.p5e.48 xlarge is suggested.
 Optionally, you can configure innovative [security](https://gitea.cisetech.com) and infrastructure settings, including virtual personal cloud (VPC) networking, service role consents, and encryption settings. For a lot of utilize cases, the default settings will work well. However, for production deployments, you might desire to examine these settings to align with your organization's security and  [pediascape.science](https://pediascape.science/wiki/User:EdytheIvory959) compliance requirements.
 7. Choose Deploy to start using the model.<br>
 <br>When the deployment is complete, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
 8. Choose Open in play ground to access an interactive user interface where you can explore various prompts and change design criteria like temperature level and optimum length.
 When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimum outcomes. For example, content for reasoning.<br>
 <br>This is an exceptional method to explore the [design's reasoning](https://haloentertainmentnetwork.com) and text generation abilities before incorporating it into your [applications](https://git.ascarion.org). The play area supplies instant feedback, assisting you understand how the design reacts to various inputs and letting you tweak your prompts for optimal outcomes.<br>
 <br>You can quickly check the design in the play area through the UI. However, to conjure up the released model programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
 <br>Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint<br>
 <br>The following code example shows how to perform reasoning utilizing a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can develop 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 produced the guardrail, utilize the following code to carry out guardrails. The script initializes the bedrock_runtime customer, configures inference specifications, and sends a request to generate text based upon 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 couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs 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 offers two convenient methods: using the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both techniques to help you pick the technique that finest fits your requirements.<br>
 <br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
 <br>Complete the following steps to release DeepSeek-R1 using [SageMaker](http://mao2000.com3000) 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 model internet browser displays available models, with details like the supplier name and model abilities.<br>
 <br>4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
 Each design card reveals crucial details, consisting of:<br>
 <br>- Model name
 - Provider name
 - Task category (for example, Text Generation).
 Bedrock Ready badge (if appropriate), indicating that this design can be signed up with Amazon Bedrock, enabling you to utilize Amazon Bedrock APIs to invoke the model<br>
 <br>5. Choose the design card to view the model details page.<br>
 <br>The design details page consists of the following details:<br>
 <br>- The design name and supplier details.
 Deploy button to deploy the design.
 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 requirements.
 - Usage guidelines<br>
 <br>Before you deploy the model, it's suggested to review the model details and license terms to verify compatibility with your use case.<br>
 <br>6. Choose Deploy to proceed with release.<br>
 <br>7. For Endpoint name, utilize the instantly produced name or develop a [custom-made](https://git.dev-store.xyz) one.
 8. For example [type ¸](http://1.14.125.63000) pick an instance type (default: ml.p5e.48 xlarge).
 9. For Initial instance count, get in the number of circumstances (default: 1).
 Selecting appropriate circumstances types and counts is essential for cost and efficiency optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time reasoning is selected by default. This is optimized for sustained traffic and low latency.
 10. Review all configurations for accuracy. For this design, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network isolation remains in location.
 11. Choose Deploy to release the design.<br>
 <br>The implementation procedure can take several minutes to finish.<br>
 <br>When deployment is complete, your endpoint status will change to InService. At this moment, the design is prepared to accept reasoning requests through the [endpoint](https://owangee.com). You can keep track of the deployment development on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the deployment is total, you can invoke the design utilizing a SageMaker runtime client and incorporate it with your applications.<br>
 <br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
 <br>To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the required AWS authorizations and environment setup. The following is a detailed code example that demonstrates how to deploy and use DeepSeek-R1 for [reasoning programmatically](https://www.trappmasters.com). The code for deploying the model is offered in the Github here. You can clone the note pad and run from SageMaker Studio.<br>
 <br>You can run additional 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 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 prevent unwanted charges, complete the actions in this area to clean up your resources.<br>
 <br>Delete the Amazon Bedrock Marketplace release<br>
 <br>If you deployed the design using Amazon Bedrock Marketplace, total the following actions:<br>
 <br>1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace implementations.
 2. In the Managed releases area, find the endpoint you wish to erase.
 3. Select the endpoint, and on the Actions menu, [select Delete](https://edenhazardclub.com).
 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](https://videofrica.com) 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 explored how you can access and release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock [Marketplace](http://101.34.87.71) now to get started. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon [Bedrock](http://git.szchuanxia.cn) Marketplace, and Getting begun 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://dandaelitetransportllc.com) companies build innovative solutions utilizing  and sped up [compute](https://gitea.dokm.xyz). Currently, he is focused on developing methods for fine-tuning and optimizing the inference performance of large language models. In his downtime, Vivek takes pleasure in treking, viewing films, and trying various cuisines.<br>
 <br>Niithiyn Vijeaswaran is a Generative [AI](http://8.134.253.221:8088) Specialist Solutions [Architect](https://axc.duckdns.org8091) with the Third-Party Model [Science](http://drive.ru-drive.com) team at AWS. His area of focus is AWS [AI](https://arbeitswerk-premium.de) accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.<br>
 <br>Jonathan Evans is a Professional Solutions Architect working on generative [AI](https://forum.petstory.ge) with the Third-Party Model Science team at AWS.<br>
 <br>Banu Nagasundaram leads product, engineering, and [strategic partnerships](http://8.141.83.2233000) for Amazon SageMaker JumpStart, [SageMaker's](http://139.9.60.29) artificial intelligence and generative [AI](https://oakrecruitment.uk) hub. She is passionate about constructing options that assist clients accelerate their [AI](https://allcollars.com) journey and unlock business worth.<br>