Today, we are excited 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's first-generation frontier design, DeepSeek-R1, along with the distilled variations varying from 1.5 to 70 billion parameters to build, experiment, and responsibly scale your generative AI concepts on AWS.

In this post, we show how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to release the distilled versions of the models too.

Overview of DeepSeek-R1

DeepSeek-R1 is a large language model (LLM) established by DeepSeek AI that uses reinforcement finding out to improve reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. A crucial distinguishing feature is its reinforcement knowing (RL) step, which was utilized to refine the design's responses beyond the basic pre-training and tweak process. By including RL, DeepSeek-R1 can adjust better to user feedback and goals, ultimately boosting both significance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, meaning it's equipped to break down complex questions and reason through them in a detailed manner. This guided thinking procedure enables the model to produce more precise, transparent, and detailed responses. This model combines RL-based fine-tuning with CoT capabilities, aiming to generate structured responses while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has recorded the industry's attention as a flexible text-generation design that can be integrated into different workflows such as representatives, sensible thinking and data analysis tasks.

DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion parameters, making it possible for efficient inference by routing inquiries to the most pertinent expert "clusters." This technique permits the model to concentrate on different problem domains while maintaining general efficiency. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge instance to release the model. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.

DeepSeek-R1 distilled models bring the reasoning capabilities of the main R1 design to more efficient 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 efficient designs to mimic the habits and reasoning patterns of the bigger DeepSeek-R1 design, using it as a teacher 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 location. In this blog site, we will use Amazon Bedrock Guardrails to present safeguards, prevent harmful content, and evaluate designs against crucial security 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 produce numerous guardrails tailored to various usage cases and use them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls across your generative AI applications.

Prerequisites

To deploy the DeepSeek-R1 model, you require 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 validate you're utilizing 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 increase, develop a limitation increase demand and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to present safeguards, prevent harmful content, and evaluate designs against key safety criteria. You can carry out precaution for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to examine user inputs and design responses 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 develop the guardrail, see the GitHub repo.

The basic flow involves the following actions: 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 out to the design for reasoning. After getting the design's output, another guardrail check is used. If the output passes this final check, it's returned as the outcome. However, if either the input or output is stepped in by the guardrail, a message is returned showing the nature of the intervention and whether it happened at the input or output stage. The examples showcased in the following areas demonstrate reasoning utilizing this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace gives you access to over 100 popular, emerging, and specialized foundation models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:

1. On the Amazon Bedrock console, choose Model catalog under Foundation models in the navigation pane. At the time of writing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling. 2. Filter for DeepSeek as a company and choose the DeepSeek-R1 design.

The design detail page provides important details about the model's capabilities, pricing structure, and execution standards. You can find detailed usage guidelines, including sample API calls and code bits for integration. The design supports various text generation tasks, consisting of material development, code generation, and question answering, utilizing its reinforcement learning optimization and CoT reasoning abilities. The page also consists of release choices and licensing details to assist you begin with DeepSeek-R1 in your applications. 3. To begin utilizing DeepSeek-R1, choose Deploy.

You will be prompted to set up the release details for DeepSeek-R1. The design ID will be pre-populated. 4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters). 5. For Number of circumstances, enter a number of instances (in between 1-100). 6. For example type, select your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested. Optionally, you can set up sophisticated security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service function consents, and file encryption settings. For a lot of utilize cases, the default settings will work well. However, for production implementations, you might wish to examine these settings to align with your company's security and compliance requirements. 7. Choose Deploy to begin utilizing the design.

When the release is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock playground. 8. Choose Open in play area to access an interactive interface where you can explore different triggers and change model parameters like temperature and optimum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for optimal results. For example, material for inference.

This is an outstanding method to check out the design's thinking and text generation capabilities before integrating it into your applications. The playground supplies immediate feedback, assisting you understand how the model responds to different inputs and letting you fine-tune your triggers for optimal outcomes.

You can quickly check the design in the play area through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.

Run inference using guardrails with the released DeepSeek-R1 endpoint

The following code example shows how to carry out reasoning using 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 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 client, sets up inference specifications, and sends out a demand to generate text based on 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 options that you can release with just 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 model through SageMaker JumpStart provides 2 convenient techniques: using the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both approaches to help you choose the technique that best suits your needs.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

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

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

The design web browser displays available models, with details like the supplier name and design abilities.

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

- Model name

• Provider name
• Task classification (for example, Text Generation). Bedrock Ready badge (if appropriate), showing that this design can be signed up with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to conjure up the design
  
  5. Choose the model card to see the model details page.
  
  The model details page consists of the following details:
  
  - The design name and provider details. Deploy button to deploy the model. About and Notebooks tabs with detailed details
  
  The About tab consists of crucial details, such as:
  
  - Model description.
• License details.
• Technical specs.
• Usage guidelines
  
  Before you deploy the model, it's recommended to evaluate the design details and license terms to confirm compatibility with your usage case.
  
  6. Choose Deploy to continue with implementation.
  
  7. For Endpoint name, use the immediately created name or produce a custom one.

8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, go into the number of instances (default: 1). Selecting appropriate instance types and counts is vital for cost and efficiency optimization. Monitor your deployment 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 precision. For this design, we strongly recommend sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the model.
    
    The deployment process can take numerous minutes to finish.
    
    When implementation is complete, your endpoint status will alter to InService. At this moment, the design is prepared to accept reasoning demands through the endpoint. You can monitor the deployment progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the deployment is total, you can invoke the model utilizing a SageMaker runtime customer and incorporate it with your applications.
    
    Deploy DeepSeek-R1 utilizing the SageMaker Python SDK
    
    To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the essential AWS permissions and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for inference programmatically. The code for deploying the design is provided in the Github here. You can clone the note pad and range from SageMaker Studio.
    
    You can run extra demands against the predictor:
    
    Implement guardrails and run inference with your SageMaker JumpStart predictor
    
    Similar to Amazon Bedrock, you can likewise use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and implement it as shown in the following code:
    
    Tidy up
    
    To avoid undesirable charges, finish the steps in this area to clean up your resources.
    
    Delete the Amazon Bedrock Marketplace deployment
    
    If you released the design utilizing Amazon Bedrock Marketplace, total the following actions:
    
    1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, choose Marketplace implementations.
12. In the Managed deployments area, locate the endpoint you wish to delete.
13. Select the endpoint, and on the Actions menu, select Delete.
14. Verify the endpoint details to make certain you're deleting the proper implementation: 1. Endpoint name.
15. Model name.
16. Endpoint status
    
    Delete the SageMaker JumpStart predictor
    
    The SageMaker JumpStart model you deployed will sustain costs if you leave it running. Use the following code to delete the endpoint if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.
    
    Conclusion
    
    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 now to begin. 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 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 solutions utilizing AWS services and accelerated compute. Currently, he is focused on establishing techniques for fine-tuning and forum.pinoo.com.tr enhancing the reasoning efficiency of large language designs. In his leisure time, Vivek enjoys hiking, viewing films, and attempting different .
    
    Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS AI accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science 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 hub. She is passionate about constructing services that assist clients accelerate their AI journey and unlock service worth.