lillycountryma
/
kibistudio
1
0
Code Issues Packages Projects Wiki

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

Lilly Countryman 2025-02-17 10:19:02 +08:00
commit a0490d0b16
1 changed files with 93 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart.-.md Normal file

@ -0,0 +1,93 @@
<br>Today, we are thrilled to announce that DeepSeek R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek [AI](http://test.wefanbot.com:3000)'s first-generation frontier design, DeepSeek-R1, in addition to the distilled variations ranging from 1.5 to 70 billion specifications to construct, experiment, and properly scale your generative [AI](http://111.8.36.180:3000) ideas on AWS.<br>
<br>In this post, we show how to get started with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled versions of the designs also.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a big language model (LLM) established by DeepSeek [AI](https://ozoms.com) that uses support learning to boost thinking abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key distinguishing function is its support knowing (RL) action, which was used to refine the model's reactions beyond the basic pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adjust more successfully to user feedback and goals, ultimately boosting both relevance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) technique, indicating it's geared up to break down intricate inquiries and reason through them in a detailed way. This directed reasoning process [enables](http://doosung1.co.kr) the model to produce more accurate, transparent, and [gratisafhalen.be](https://gratisafhalen.be/author/tamikalaf18/) detailed responses. This design combines RL-based fine-tuning with CoT capabilities, aiming to create structured reactions while concentrating on interpretability and user [interaction](http://euhope.com). With its wide-ranging abilities DeepSeek-R1 has actually recorded the market's attention as a flexible text-generation model that can be integrated into different workflows such as agents, rational reasoning and information analysis jobs.<br>
<br>DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture allows activation of 37 billion parameters, enabling effective inference by routing questions to the most relevant expert "clusters." This technique allows the design to concentrate 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 use an ml.p5e.48 xlarge instance to release the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled models bring the thinking abilities 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 refers to a process of [training](https://blazblue.wiki) smaller, more efficient designs to mimic the behavior and thinking patterns of the larger DeepSeek-R1 model, 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 suggest releasing this model with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid damaging material, and assess designs against essential security criteria. At the time of writing this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create several guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, enhancing user experiences and [standardizing safety](https://www.yourtalentvisa.com) controls throughout your generative [AI](http://47.108.94.35) applications.<br>
<br>Prerequisites<br>
<br>To deploy the DeepSeek-R1 model, you require access to an ml.p5e [circumstances](http://119.3.29.1773000). To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and verify you're using 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](https://gitea.pi.cr4.live). To ask for a limitation boost, develop a limit boost request and connect to your account group.<br>
<br>Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the correct AWS Identity and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For directions, see Set up approvals to use guardrails for content filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock [Guardrails permits](http://dating.instaawork.com) you to introduce safeguards, prevent damaging material, and examine designs against [crucial](https://semtleware.com) security requirements. You can carry out security measures for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to evaluate user inputs and [design reactions](http://koceco.co.kr) deployed on Amazon Bedrock [Marketplace](https://www.wow-z.com) and SageMaker JumpStart. You can create a the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.<br>
<br>The general flow 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 model 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 result. However, if either the input or output is intervened by the guardrail, a message is returned suggesting the nature of the intervention and whether it happened at the input or output phase. The examples showcased in the following areas show reasoning using this API.<br>
<br>Deploy DeepSeek-R1 in Amazon Bedrock Marketplace<br>
<br>Amazon Bedrock Marketplace offers you access to over 100 popular, emerging, and specialized foundation designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:<br>
<br>1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and choose the DeepSeek-R1 design.<br>
<br>The design detail page [supplies essential](https://karis.id) details about the model's capabilities, pricing structure, and application standards. You can discover detailed usage guidelines, consisting of sample API calls and code snippets for [integration](http://git.agentum.beget.tech). The model supports numerous text generation tasks, consisting of content creation, code generation, and question answering, using its support learning optimization and CoT thinking abilities.
The page also includes implementation options and licensing details to help you start with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, select Deploy.<br>
<br>You will be prompted to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
5. For Number of instances, go into a number of [instances](https://gitlab.ccc.org.co) (in between 1-100).
6. For Instance type, select your instance type. For optimum efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised.
Optionally, you can [configure advanced](https://matchpet.es) security and facilities settings, including virtual personal cloud (VPC) networking, service function authorizations, and file encryption [settings](https://lab.chocomart.kz). For many utilize cases, the [default settings](http://47.119.20.138300) will work well. However, for production implementations, you might wish to review these settings to align with your company's security and compliance requirements.
7. Choose Deploy to begin using the design.<br>
<br>When the deployment is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock playground.
8. Choose Open in play area to access an interactive user interface where you can experiment with different triggers and adjust design criteria like temperature and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For instance, material for inference.<br>
<br>This is an exceptional method to explore the design's reasoning and text generation abilities before integrating it into your applications. The playground supplies instant feedback, assisting you understand how the [design reacts](http://39.98.79.181) to different inputs and letting you [fine-tune](https://dev.fleeped.com) your prompts for ideal outcomes.<br>
<br>You can rapidly evaluate the design in the [playground](https://samman-co.com) through the UI. However, to conjure up the [released model](https://lubuzz.com) programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.<br>
<br>Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint<br>
<br>The following code example demonstrates how to perform reasoning utilizing a released 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 create 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 parameters, and sends a demand to create text based upon a user timely.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub 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 models to your use case, with your information, and deploy them into [production utilizing](https://one2train.net) either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 convenient approaches: utilizing the intuitive SageMaker JumpStart UI or implementing programmatically through the [SageMaker](https://www.viewtubs.com) Python SDK. Let's explore both techniques to help you pick the method that best matches your requirements.<br>
<br>Deploy DeepSeek-R1 through SageMaker JumpStart UI<br>
<br>Complete the following steps 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 develop a domain.
3. On the SageMaker Studio console, select [JumpStart](http://www.raverecruiter.com) in the navigation pane.<br>
<br>The model browser displays available designs, with details like the service provider name and design capabilities.<br>
<br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each [design card](https://sos.shinhan.ac.kr) shows essential details, consisting of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if relevant), indicating that this design can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to invoke the design<br>
<br>5. Choose the model card to see the model details page.<br>
<br>The model details page includes the following details:<br>
<br>- The model name and provider details.
Deploy button to release the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab includes crucial details, such as:<br>
<br>- Model description.
- License details.
- Technical requirements.
- Usage standards<br>
<br>Before you deploy the design, it's recommended to examine the design details and license terms to confirm compatibility with your use case.<br>
<br>6. Choose Deploy to continue with implementation.<br>
<br>7. For Endpoint name, utilize the instantly created name or develop a custom-made one.
8. For example type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the number of instances (default: 1).
Selecting suitable [instance](http://svn.ouj.com) types and counts is crucial for cost and efficiency optimization. Monitor your release to change these settings as needed.Under Inference type, Real-time inference is chosen by default. This is enhanced for sustained traffic and low latency.
10. Review all configurations for precision. For this design, we highly recommend adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the design.<br>
<br>The release process can take several minutes to complete.<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. You can keep an eye on the release development on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the implementation is total, you can invoke the design utilizing a SageMaker runtime client and integrate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To begin with DeepSeek-R1 using the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the required AWS approvals and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for [higgledy-piggledy.xyz](https://higgledy-piggledy.xyz/index.php/User:XXBCorine49) inference programmatically. The code for releasing the design is provided in the Github here. You can clone the notebook and run from SageMaker Studio.<br>
<br>You can run extra demands against the predictor:<br>
<br>Implement guardrails and run reasoning with your SageMaker JumpStart predictor<br>
<br>Similar to Amazon Bedrock, you can likewise utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail using the Amazon Bedrock console or the API, [wiki.whenparked.com](https://wiki.whenparked.com/User:AlejandrinaVanno) and execute it as shown in the following code:<br>
<br>Tidy up<br>
<br>To prevent unwanted charges, complete the steps in this section to tidy up your resources.<br>
<br>Delete the Amazon Bedrock Marketplace deployment<br>
<br>If you deployed the model 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 releases.
2. In the Managed implementations area, find the [endpoint](https://body-positivity.org) you wish to erase.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're erasing the proper release: 1. Endpoint name.
2. Model name.
3. Endpoint status<br>
<br>Delete the SageMaker JumpStart predictor<br>
<br>The SageMaker JumpStart model you released will sustain costs if you leave it running. Use the following code to erase 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 checked out 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 now to get started. 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 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://topstours.com) companies develop ingenious options utilizing AWS services and accelerated compute. Currently, he is focused on developing strategies for fine-tuning and enhancing the reasoning efficiency of big [language](http://45.45.238.983000) models. In his downtime, [Vivek delights](https://git.mintmuse.com) in hiking, viewing films, and attempting different foods.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://gitlab.dev.cpscz.site) Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS [AI](http://hrplus.com.vn) 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://apps365.jobs) with the Third-Party Model Science group at AWS.<br>
<br>Banu Nagasundaram leads item, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://edujobs.itpcrm.net) hub. She is [passionate](https://qdate.ru) about building solutions that help clients accelerate their [AI](http://111.160.87.82:8004) journey and unlock company value.<br>