bryonmaccarthy
/
jobedges
1
0
Code Issues Packages Projects Wiki

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

Bryon MacCarthy 2025-02-09 20:53:57 +08:00
commit c1db7ab406
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 delighted 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 deploy DeepSeek [AI](https://www.top5stockbroker.com)'s first-generation frontier model, DeepSeek-R1, together with the distilled variations ranging from 1.5 to 70 billion specifications to build, experiment, and properly scale your generative [AI](https://blkbook.blactive.com) ideas on AWS.<br>
<br>In this post, we show how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to release the distilled variations of the designs too.<br>
<br>Overview of DeepSeek-R1<br>
<br>DeepSeek-R1 is a large language model (LLM) established by DeepSeek [AI](http://e-kou.jp) that utilizes reinforcement finding out to boost reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key identifying feature is its reinforcement learning (RL) action, which was used to fine-tune the design's reactions beyond the basic pre-training and tweak process. By integrating RL, DeepSeek-R1 can adjust more effectively to user feedback and goals, ultimately boosting both importance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, indicating it's geared up to break down intricate queries and factor through them in a detailed way. This directed reasoning [process](https://ddsbyowner.com) permits the model to produce more accurate, transparent, and detailed answers. This design combines RL-based fine-tuning with CoT abilities, aiming to generate structured responses while [focusing](https://aloshigoto.jp) on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has actually recorded the market's attention as a [versatile](http://207.180.250.1143000) text-generation design that can be integrated into numerous workflows such as representatives, logical reasoning and information analysis tasks.<br>
<br>DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture enables activation of 37 billion criteria, enabling efficient reasoning by routing questions to the most appropriate expert "clusters." This technique allows the design to concentrate on various issue domains while maintaining overall performance. DeepSeek-R1 requires a minimum of 800 GB of [HBM memory](http://www.xn--he5bi2aboq18a.com) in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge circumstances to deploy the design. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.<br>
<br>DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 design to more effective architectures based upon popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller sized, more effective models to simulate the behavior and [reasoning patterns](https://git.rongxin.tech) of the bigger DeepSeek-R1 model, using it as an instructor design.<br>
<br>You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest releasing this design with [guardrails](https://mtglobalsolutionsinc.com) in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid [damaging](https://955x.com) content, and evaluate designs against essential security criteria. At the time of composing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create multiple guardrails tailored to various use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative [AI](http://106.15.235.242) applications.<br>
<br>Prerequisites<br>
<br>To release the DeepSeek-R1 model, you need access to an ml.p5e circumstances. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, select Amazon SageMaker, and confirm you're using ml.p5e.48 xlarge for endpoint usage. 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 increase, create a limitation increase request and reach out to your account team.<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) approvals to utilize Amazon Bedrock Guardrails. For guidelines, see Establish authorizations to use guardrails for material filtering.<br>
<br>Implementing guardrails with the ApplyGuardrail API<br>
<br>Amazon Bedrock Guardrails permits you to [introduce](https://git.cno.org.co) safeguards, avoid [hazardous](http://mirae.jdtsolution.kr) material, and assess designs against [key security](https://abadeez.com) criteria. You can carry out security procedures for the DeepSeek-R1 model using 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 develop a guardrail utilizing the Amazon [Bedrock console](https://www.com.listatto.ca) or the API. For the example code to produce the guardrail, see the GitHub repo.<br>
<br>The basic [circulation involves](http://modiyil.com) 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 design for inference. After receiving the model's output, another [guardrail check](https://blkbook.blactive.com) is used. If the output passes this last check, it's returned as the outcome. 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 demonstrate 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](https://tiwarempireprivatelimited.com). To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:<br>
<br>1. On the Amazon Bedrock console, [surgiteams.com](https://surgiteams.com/index.php/User:KaseyDees635) pick Model catalog under Foundation designs in the [navigation](http://www.sa1235.com) pane.
At the time of writing this post, you can utilize the InvokeModel API to invoke the design. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for [DeepSeek](https://4realrecords.com) as a [service provider](https://git.nothamor.com3000) and select the DeepSeek-R1 model.<br>
<br>The design detail page provides essential details about the model's abilities, rates structure, and implementation standards. You can find detailed usage directions, consisting of sample API calls and code bits for combination. The model supports numerous text generation jobs, consisting of content creation, code generation, and concern answering, using its reinforcement finding out optimization and CoT reasoning capabilities.
The page also includes release choices and licensing details to help you get going with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select 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, [disgaeawiki.info](https://disgaeawiki.info/index.php/User:KelleG0472) go into an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of instances, go into a variety of instances (between 1-100).
6. For example type, pick your instance type. For ideal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up advanced security and facilities settings, [including virtual](https://ai.ceo) personal cloud (VPC) networking, service role permissions, and file encryption settings. For many utilize cases, the default settings will work well. However, for production deployments, you might want to examine these settings to align with your organization's security and compliance requirements.
7. Choose Deploy to start utilizing the design.<br>
<br>When the deployment is complete, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock play ground.
8. Choose Open in play ground to access an interactive user interface where you can try out various prompts and change model specifications like temperature and optimum length.
When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimum results. For instance, material for inference.<br>
<br>This is an excellent way to check out the model's reasoning and text generation abilities before integrating it into your applications. The play area provides immediate feedback, helping you comprehend how the design reacts to various inputs and letting you tweak your prompts for ideal outcomes.<br>
<br>You can [rapidly](http://git.mcanet.com.ar) test the design in the playground through the UI. However, to conjure up the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.<br>
<br>Run inference using guardrails with the [released](http://president-park.co.kr) DeepSeek-R1 endpoint<br>
<br>The following code example shows how to carry out inference utilizing a deployed DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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 developed the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning criteria, and sends out a demand to produce text based on a user prompt.<br>
<br>Deploy DeepSeek-R1 with SageMaker JumpStart<br>
<br>SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and prebuilt ML solutions that you can release with just a couple of clicks. With JumpStart, you can tailor pre-trained models to your use case, with your data, and release them into production utilizing either the UI or SDK.<br>
<br>Deploying DeepSeek-R1 model through SageMaker JumpStart uses 2 hassle-free techniques: utilizing the instinctive SageMaker JumpStart UI or [carrying](https://whotube.great-site.net) out programmatically through the SageMaker Python SDK. Let's check out both methods to help you select the method that best fits your requirements.<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, select Studio in the [navigation pane](https://professionpartners.co.uk).
2. First-time users will be prompted to produce a domain.
3. On the SageMaker Studio console, choose [JumpStart](http://41.111.206.1753000) in the navigation pane.<br>
<br>The model internet browser displays available models, with details like the company name and model abilities.<br>
<br>4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card shows crucial details, [consisting](https://www.opad.biz) of:<br>
<br>- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if suitable), [suggesting](https://git.wo.ai) that this model can be signed up with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to invoke the model<br>
<br>5. Choose the design card to view the design details page.<br>
<br>The design details page includes the following details:<br>
<br>- The design name and service provider details.
Deploy button to release the model.
About and Notebooks tabs with detailed details<br>
<br>The About tab includes important details, such as:<br>
<br>- Model description.
- License details.
- Technical requirements.
- Usage guidelines<br>
<br>Before you deploy the design, it's suggested to evaluate the design details and license terms to confirm compatibility with your usage case.<br>
<br>6. Choose Deploy to continue with release.<br>
<br>7. For Endpoint name, [raovatonline.org](https://raovatonline.org/author/namchism044/) utilize the immediately generated name or develop a custom-made one.
8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the number of instances (default: 1).
Selecting proper circumstances types and counts is vital for cost and efficiency optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, Real-time inference is chosen by default. This is [optimized](http://git.jaxc.cn) for sustained traffic and low latency.
10. Review all configurations for accuracy. For this model, we strongly recommend sticking 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 procedure can take a number of minutes to finish.<br>
<br>When deployment is total, your [endpoint status](https://x-like.ir) will alter to InService. At this point, the model is ready to accept inference requests through the endpoint. You can keep track of the release development on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the implementation is total, you can conjure up the model using a SageMaker runtime client and incorporate it with your applications.<br>
<br>Deploy DeepSeek-R1 using the SageMaker Python SDK<br>
<br>To begin 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 approvals and environment setup. The following is a detailed code example that shows how to release and utilize DeepSeek-R1 for reasoning programmatically. The code for [deploying](https://xn--v69atsro52ncsg2uqd74apxb.com) the design is provided 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 [inference](https://jobskhata.com) 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, and execute it as displayed in the following code:<br>
<br>Tidy up<br>
<br>To prevent unwanted 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 model utilizing Amazon Bedrock Marketplace, complete the following steps:<br>
<br>1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace implementations.
2. In the Managed releases area, locate the endpoint 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](https://www.keeperexchange.org) you deployed will sustain costs if you leave it running. Use the following code to erase 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 release the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock [Marketplace](https://git.selfmade.ninja) now to begin. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting with [Amazon SageMaker](https://wiki.rrtn.org) 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](http://gogs.efunbox.cn) business build innovative options utilizing AWS services and accelerated compute. Currently, he is concentrated on establishing techniques for fine-tuning and optimizing the reasoning efficiency of large language designs. In his free time, Vivek delights in treking, watching motion pictures, and trying different cuisines.<br>
<br>Niithiyn Vijeaswaran is a Generative [AI](https://tawtheaf.com) Specialist Solutions [Architect](https://melaninbook.com) with the Third-Party Model [Science](https://gitea.sync-web.jp) team at AWS. His area of focus is AWS [AI](http://www.origtek.com:2999) 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](http://203.171.20.94:3000) with the Third-Party Model Science team at AWS.<br>
<br>Banu Nagasundaram leads product, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative [AI](https://sugardaddyschile.cl) center. She is enthusiastic about constructing services that [assist consumers](http://47.98.226.2403000) accelerate their [AI](https://optimaplacement.com) journey and unlock service worth.<br>