DeepSeek-R1 Model now Av... 投稿者：ai 投稿日：2025/12/13(Sat) 17:40 No.760634 
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's first-generation frontier design, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion parameters to develop, experiment, and properly scale your generative AI concepts on AWS.
In this post, we show how to begin with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable actions to deploy the distilled variations of the models also.
Overview of DeepSeek-R1
DeepSeek-R1 is a big language model (LLM) established by DeepSeek AI that utilizes reinforcement learning to enhance thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential differentiating function is its support knowing (RL) step, which was used to fine-tune the model's reactions beyond the basic pre-training and fine-tuning process. By incorporating RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately enhancing both relevance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, meaning it's geared up to break down intricate inquiries and reason through them in a detailed way. This directed reasoning procedure permits the design 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 capabilities DeepSeek-R1 has actually recorded the industry's attention as a versatile text-generation model that can be integrated into numerous workflows such as representatives, rational thinking and data analysis tasks.
DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, enabling effective reasoning by routing questions to the most pertinent specialist "clusters." This method permits the design to concentrate on various problem domains while maintaining general performance. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge circumstances to release the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.
DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 model 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, more effective models to imitate the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as a teacher design.
You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend releasing this model with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, prevent damaging material, and assess designs against key security requirements. At the time of writing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop numerous guardrails tailored to different use cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls throughout your generative AI applications.
Prerequisites
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 confirm you're utilizing 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. To ask for a limitation boost, produce a limit boost demand and reach out to your account group.
Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For guidelines, see Set up authorizations to utilize guardrails for material filtering.
Implementing guardrails with the ApplyGuardrail API
Amazon Bedrock Guardrails allows you to introduce safeguards, avoid harmful material, and evaluate models against essential safety criteria. You can execute precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to assess user inputs and model responses deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.
The basic circulation includes the following steps: First, the system receives 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 getting the model's output, another guardrail check is applied. 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, a message is returned indicating the nature of the intervention and whether it occurred at the input or output stage. The examples showcased in the following sections show inference utilizing this API.
Deploy DeepSeek-R1 in Amazon Bedrock Marketplace
Amazon Bedrock Marketplace gives 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:
1. On the Amazon Bedrock console, select Model catalog under Foundation models in the navigation pane.
At the time of composing 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 as a company and choose the DeepSeek-R1 model.
The design detail page supplies necessary details about the model's abilities, rates structure, and implementation standards. You can discover detailed use instructions, including sample API calls and code bits for integration. The model supports various text generation jobs, including material development, code generation, and concern answering, utilizing its reinforcement discovering optimization and CoT reasoning capabilities.
The page likewise includes implementation options and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, select Deploy.
You will be triggered to set up the release details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters).
5. For Number of instances, enter a number of instances (between 1-100).
6. For Instance type, pick your instance type. For optimum efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can configure sophisticated security and infrastructure settings, consisting of virtual private cloud (VPC) networking, service function approvals, and encryption settings. For the majority of utilize cases, the default settings will work well. However, for production deployments, you may want to examine these settings to line up with your company's security and compliance requirements.
7. Choose Deploy to begin utilizing the design.
When the deployment is total, you can check DeepSeek-R1's abilities straight in the Amazon Bedrock play area.
8. Choose Open in playground to access an interactive interface where you can try out various 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 design template for optimum outcomes. For example, content for inference.
This is an outstanding method to check out the design's thinking and text generation capabilities before incorporating it into your applications. The play area provides immediate feedback, helping you comprehend how the model reacts to different inputs and letting you tweak your triggers for optimal outcomes.
You can rapidly test the model in the play area through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.
Run inference utilizing guardrails with the released DeepSeek-R1 endpoint
The following code example demonstrates how to perform inference utilizing a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can produce 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 developed the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures inference parameters, and sends a request to create text based upon a user timely.
Deploy DeepSeek-R1 with SageMaker JumpStart
SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, built-in algorithms, and prebuilt ML services that you can deploy with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your information, and release them into production using either the UI or SDK.
Deploying DeepSeek-R1 design through SageMaker JumpStart offers two practical methods: utilizing the intuitive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both methods to help you select the technique that best matches your requirements.
Deploy DeepSeek-R1 through SageMaker JumpStart UI
Complete the following actions to release DeepSeek-R1 utilizing SageMaker JumpStart:
1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be triggered to develop a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.
The model web browser shows available designs, with details like the service provider name and design abilities.
4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card reveals crucial details, including:
- Model name
- Provider name
- Task classification (for instance, Text Generation).
Bedrock Ready badge (if suitable), showing that this design can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to invoke the design
5. Choose the design card to view the design details page.
The design details page consists of the following details:
- The design name and provider details.
Deploy button to release the model.
About and Notebooks tabs with detailed details
The About tab consists of crucial details, such as:
- Model description.
- License details.
- Technical specifications.
- Usage guidelines
Before you release the design, it's recommended to examine the design details and license terms to verify compatibility with your use case.
6. Choose Deploy to proceed with implementation.
7. For Endpoint name, use the instantly created name or produce a custom-made one.
8. For example type ｸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the number of circumstances (default: 1).
Selecting appropriate instance types and counts is vital for cost and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is enhanced 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 deploy the design.
The deployment process can take numerous minutes to finish.
When deployment is complete, your endpoint status will alter to InService. At this point, the model is all set to accept reasoning demands through the endpoint. You can keep track of the deployment progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the release is complete, you can invoke the model utilizing a SageMaker runtime customer and integrate it with your applications.
Deploy DeepSeek-R1 using the SageMaker Python SDK
To get started with DeepSeek-R1 using the SageMaker Python SDK, you will require 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 shows how to release and use DeepSeek-R1 for reasoning programmatically. The code for releasing the model is supplied in the Github here. You can clone the notebook and range from SageMaker Studio.
You can run extra demands against the predictor:
Implement guardrails and run reasoning with your SageMaker JumpStart predictor
Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:
Clean up
To avoid unwanted charges, finish the actions in this area to tidy up your resources.
Delete the Amazon Bedrock Marketplace implementation
If you released the design using Amazon Bedrock Marketplace, complete the following steps:
1. On the Amazon Bedrock console, under Foundation models in the navigation pane, select Marketplace implementations.
2. In the Managed releases section, find 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
Delete the SageMaker JumpStart predictor
The SageMaker JumpStart model you released will sustain expenses if you leave it running. Use the following code to erase the endpoint if you desire to stop sustaining charges. For more details, see Delete Endpoints and Resources.
Conclusion
In this post, we checked out how you can access and release 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, describe 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.
About the Authors
Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative AI business develop innovative services utilizing AWS services and sped up calculate. Currently, he is concentrated on establishing strategies for fine-tuning and enhancing the reasoning efficiency of big language models. In his complimentary time, Vivek delights in hiking, watching motion pictures, and trying various cuisines.
Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS AI accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.
Jonathan Evans is a Specialist Solutions Architect working on generative AI with the Third-Party Model Science group at AWS.
Banu Nagasundaram leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is passionate about building solutions that assist consumers accelerate their AI journey and unlock company value.
|