Today, we are excited 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 deploy DeepSeek AI's first-generation frontier design, DeepSeek-R1, in addition to the distilled versions varying from 1.5 to 70 billion specifications to build, experiment, and properly scale your generative AI ideas on AWS.

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 deploy the distilled versions of the designs also.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes reinforcement finding out to improve reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential differentiating feature is its reinforcement learning (RL) action, which was utilized to fine-tune the design's actions beyond the standard pre-training and fine-tuning process. By incorporating RL, DeepSeek-R1 can adjust better to user feedback and objectives, ultimately improving both relevance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) technique, meaning it's geared up to break down complex queries and surgiteams.com factor through them in a detailed manner. This guided thinking process permits the design to produce more precise, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT abilities, aiming to create structured responses while focusing on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has recorded the market's attention as a versatile text-generation design that can be incorporated into various workflows such as representatives, rational reasoning and information analysis jobs.

DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion criteria, enabling efficient inference by routing inquiries to the most pertinent specialist "clusters." This approach enables the model to focus on different issue domains while maintaining total performance. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for inference. 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 models bring the thinking capabilities of the main R1 model to more efficient architectures based on 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 designs to imitate the behavior and reasoning patterns of the larger DeepSeek-R1 model, using it as an instructor model.

You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we advise releasing this model with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, prevent damaging content, and examine designs against crucial safety requirements. At the time of composing this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce several guardrails tailored to various use cases and use them to the DeepSeek-R1 model, enhancing user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To release the DeepSeek-R1 design, 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, pick 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 limit boost, create a limitation boost request and reach out to your account group.

Because you will be releasing this design with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) consents to utilize Amazon Bedrock Guardrails. For guidelines, see Establish permissions to use guardrails for content filtering.

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails enables you to introduce safeguards, avoid hazardous content, and assess models against crucial safety requirements. You can implement safety steps for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to assess user inputs and model responses released 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 develop the guardrail, see the GitHub repo.

The basic circulation includes the following steps: 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 model for reasoning. After receiving the design's output, another guardrail check is applied. If the output passes this final check, it's returned as the result. However, if either the input or output is intervened by the guardrail, a message is returned showing the nature of the intervention and whether it occurred at the input or output stage. The examples showcased in the following sections demonstrate inference using this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized structure designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:

1. On the Amazon Bedrock console, select Model catalog under Foundation models in the navigation pane. At the time of writing this post, you can use the InvokeModel API to invoke the design. It doesn't support Converse APIs and other Amazon Bedrock tooling. 2. Filter for DeepSeek as a service provider and pick the DeepSeek-R1 design.

The model detail page supplies necessary details about the design's abilities, prices structure, and implementation standards. You can discover detailed use instructions, including sample API calls and code snippets for combination. 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 consists of deployment alternatives and licensing details to help you get started with DeepSeek-R1 in your applications. 3. To start utilizing DeepSeek-R1, pick Deploy.

You will be triggered to set up the deployment details 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, enter a number of instances (between 1-100). 6. For example type, choose your instance type. For optimum performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested. Optionally, you can configure advanced security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service function consents, and file encryption settings. For many utilize cases, the default settings will work well. However, for production releases, you might want to evaluate these settings to line up with your organization's security and compliance requirements. 7. Choose Deploy to begin utilizing the model.

When the deployment is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play area. 8. Choose Open in play area to access an interactive user interface where you can try out various prompts and adjust model parameters like temperature and optimum length. When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for ideal results. For example, content for reasoning.

This is an exceptional method to check out the model's reasoning and text generation abilities before incorporating it into your applications. The play area provides instant feedback, helping you understand how the design reacts to numerous inputs and letting you fine-tune your triggers for ideal outcomes.

You can rapidly evaluate the model in the playground through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.

Run inference utilizing guardrails with the deployed DeepSeek-R1 endpoint

The following code example shows how to perform reasoning utilizing a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning criteria, and sends a demand to create text based on a user prompt.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and prebuilt ML options that you can deploy 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 utilizing either the UI or SDK.

Deploying DeepSeek-R1 design through SageMaker JumpStart uses two hassle-free techniques: using the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both methods to help you select the method that finest matches your needs.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

Complete the following actions to release DeepSeek-R1 utilizing SageMaker JumpStart:

1. On the SageMaker console, pick Studio in the navigation pane. 2. First-time users will be triggered to develop a domain. 3. On the SageMaker Studio console, pick JumpStart in the navigation pane.

The design internet browser displays available models, with details like the provider name and model capabilities.

4. Look for DeepSeek-R1 to see the DeepSeek-R1 model card. Each design card reveals crucial details, including:

- Model name

• Provider name
• Task category (for example, Text Generation). Bedrock Ready badge (if suitable), showing that this design can be signed up with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to conjure up the design
  
  5. Choose the model card to view the model details page.
  
  The design details page includes the following details:
  
  - The model name and provider details. Deploy button to deploy the model. About and Notebooks tabs with detailed details
  
  The About tab consists of important details, such as:
  
  - Model description.
• License details.
• Technical specs.
• Usage standards
  
  Before you release the model, it's advised to examine the model details and license terms to validate compatibility with your usage case.
  
  6. Choose Deploy to continue with deployment.
  
  7. For Endpoint name, utilize the instantly produced name or develop a customized one.

8. For example type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of instances (default: 1). Selecting suitable circumstances types and counts is crucial for cost and efficiency optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time reasoning is picked by default. This is optimized for sustained traffic and low latency.
10. Review all setups for . For this model, we strongly suggest adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the model.
    
    The implementation process can take several minutes to complete.
    
    When deployment is total, your endpoint status will alter to InService. At this moment, the design is ready to accept inference demands through the endpoint. You can monitor the release progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is total, you can conjure up the model utilizing a SageMaker runtime client and integrate it with your applications.
    
    Deploy DeepSeek-R1 using the SageMaker Python SDK
    
    To get going with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS permissions and environment setup. The following is a detailed code example that demonstrates how to deploy and use DeepSeek-R1 for reasoning programmatically. The code for releasing the model is provided in the Github here. You can clone the notebook and range from SageMaker Studio.
    
    You can run additional demands against the predictor:
    
    Implement guardrails and run reasoning with your SageMaker JumpStart predictor
    
    Similar to Amazon Bedrock, you can also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:
    
    Tidy up
    
    To prevent undesirable charges, complete the steps in this section to tidy up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you deployed the design using Amazon Bedrock Marketplace, total the following actions:
    
    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, select Marketplace implementations.
12. In the Managed deployments area, locate the endpoint you wish to delete.
13. Select the endpoint, and on the Actions menu, choose Delete.
14. Verify the endpoint details to make certain you're erasing the right release: 1. Endpoint name.
15. Model name.
16. Endpoint status
    
    Delete the SageMaker JumpStart predictor
    
    The SageMaker JumpStart design 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 explored how you can access and deploy the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get begun. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going 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 build ingenious options using AWS services and sped up compute. Currently, he is focused on developing methods for fine-tuning and enhancing the reasoning efficiency of big language designs. In his totally free time, Vivek takes pleasure in hiking, viewing movies, and attempting 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 Professional Solutions Architect working on generative AI with the Third-Party Model Science group at AWS.
    
    Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is enthusiastic about constructing services that assist clients accelerate their AI journey and unlock organization value.