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 release DeepSeek AI's first-generation frontier design, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion parameters to construct, experiment, and properly scale your generative AI ideas on AWS.

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

Overview of DeepSeek-R1

DeepSeek-R1 is a big language model (LLM) established by DeepSeek AI that utilizes support discovering to boost thinking capabilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. A crucial distinguishing function is its support learning (RL) step, which was utilized to fine-tune the design's actions beyond the standard pre-training and fine-tuning procedure. By including RL, DeepSeek-R1 can adapt more effectively to user feedback and objectives, ultimately improving both significance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) approach, indicating it's equipped to break down complicated inquiries and factor through them in a detailed way. This guided thinking process enables the design to produce more precise, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT abilities, aiming to generate structured reactions while focusing on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has actually caught the market's attention as a flexible text-generation model that can be incorporated into numerous workflows such as representatives, rational thinking and data analysis jobs.

DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion parameters, enabling effective reasoning by routing questions to the most appropriate expert "clusters." This method enables the design to specialize in various problem domains while maintaining total efficiency. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge circumstances to deploy the design. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.

DeepSeek-R1 distilled models bring the reasoning capabilities of the main R1 design to more efficient architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more efficient designs to simulate the behavior and reasoning patterns of the larger DeepSeek-R1 model, utilizing it as a teacher model.

You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we advise releasing this design with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to present safeguards, prevent hazardous material, and assess designs against crucial security criteria. At the time of composing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop numerous guardrails tailored to various usage cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative AI applications.

Prerequisites

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, choose Amazon SageMaker, and validate 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. To ask for a limitation increase, develop a limit boost request 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) approvals to utilize Amazon Bedrock Guardrails. For instructions, see Set up consents to utilize guardrails for material filtering.

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to introduce safeguards, avoid harmful content, and evaluate models against key safety criteria. You can execute precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to assess user inputs and design 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 create the guardrail, see the GitHub repo.

The basic circulation involves 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 design for inference. After receiving the design's output, another guardrail check is used. If the output passes this final check, it's returned as the last 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 phase. The examples showcased in the following sections show reasoning using this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace offers 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 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 utilize the InvokeModel API to conjure up the design. It does not support Converse APIs and other Amazon Bedrock tooling. 2. Filter for DeepSeek as a company and choose the DeepSeek-R1 model.

The model detail page supplies vital details about the model's capabilities, pricing structure, and implementation guidelines. You can find detailed usage guidelines, consisting of sample API calls and code snippets for combination. The model supports various text generation tasks, consisting of material development, code generation, and question answering, using its reinforcement learning optimization and CoT thinking capabilities. The page likewise consists of implementation options and licensing details to help you get started with DeepSeek-R1 in your applications. 3. To begin utilizing DeepSeek-R1, forum.batman.gainedge.org choose Deploy.

You will be triggered to configure the implementation details for DeepSeek-R1. The design ID will be pre-populated. 4. For Endpoint name, get in an endpoint name (between 1-50 alphanumeric characters). 5. For Number of instances, go into a variety of instances (between 1-100). 6. For example type, pick your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested. Optionally, you can set up sophisticated security and facilities settings, including virtual private cloud (VPC) networking, service function authorizations, and file encryption settings. For a lot of use cases, the default settings will work well. However, for production implementations, you may desire to review 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 test DeepSeek-R1's abilities straight in the Amazon Bedrock playground. 8. Choose Open in play ground to access an interactive interface where you can explore different prompts and adjust design criteria like temperature and maximum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For example, content for inference.

This is an excellent method to check out the model's thinking and text generation abilities before incorporating it into your applications. The play area provides instant feedback, helping you understand how the design reacts to different inputs and letting you tweak your triggers for ideal results.

You can rapidly test the design in the play area through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.

Run inference using guardrails with the released DeepSeek-R1 endpoint

The following code example demonstrates how to carry out 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 create the guardrail, see the GitHub repo. After you have actually developed the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures reasoning parameters, 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 just a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and release them into production utilizing either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart uses two practical methods: utilizing the user-friendly SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both approaches to help you pick the method that finest fits your requirements.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

Complete the following steps to deploy DeepSeek-R1 using SageMaker JumpStart:

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

The model browser shows available models, with details like the supplier name and model capabilities.

4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card. Each model card shows crucial details, consisting of:

- Model name

• Provider name
• Task category (for instance, Text Generation). Bedrock Ready badge (if applicable), suggesting that this model can be signed up with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to invoke the design
  
  5. Choose the model card to view the design details page.
  
  The design details page consists of the following details:
  
  - The design name and service provider details. Deploy button to release the design. About and Notebooks tabs with detailed details
  
  The About tab includes important details, such as:
  
  - Model description.
• License details.
• Technical requirements.
• Usage guidelines
  
  Before you deploy the model, it's advised to examine the design details and license terms to verify compatibility with your use case.
  
  6. Choose Deploy to continue with deployment.
  
  7. For Endpoint name, use the instantly produced name or produce a custom one.

8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the number of circumstances (default: 1). Selecting suitable instance types and counts is important for expense and efficiency optimization. Monitor your implementation to adjust these settings as needed.Under Inference type, Real-time inference is picked by default. This is optimized for sustained traffic and low latency.
10. Review all setups for precision. For this model, we strongly suggest sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to deploy the model.
    
    The deployment procedure can take numerous minutes to finish.
    
    When implementation is total, your endpoint status will change to InService. At this moment, the model is ready to accept inference requests through the endpoint. You can keep track of the release progress on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the deployment is complete, you can conjure up the design utilizing a SageMaker runtime client and integrate it with your applications.
    
    Deploy DeepSeek-R1 utilizing the SageMaker Python SDK
    
    To start with DeepSeek-R1 using the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the essential AWS approvals and environment setup. The following is a detailed code example that shows how to release and use DeepSeek-R1 for inference programmatically. The code for deploying the model is 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 utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail using the Amazon Bedrock console or the API, and execute it as revealed in the following code:
    
    Clean up
    
    To avoid unwanted charges, finish the actions in this area to clean up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you deployed the design using Amazon Bedrock Marketplace, complete the following steps:
    
    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
12. In the Managed implementations section, locate the endpoint you want to delete.
13. Select the endpoint, and on the Actions menu, pick Delete.
14. Verify the endpoint details to make certain you're deleting the appropriate implementation: 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 release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get going. 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 Beginning with Amazon SageMaker JumpStart.
    
    About the Authors
    
    Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging generative AI companies build innovative options using AWS services and sped up calculate. Currently, he is focused on establishing strategies for fine-tuning and enhancing the reasoning efficiency of large language designs. In his spare time, Vivek enjoys hiking, seeing films, and trying various foods.
    
    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 technology and Bioinformatics.
    
    Jonathan Evans is an Expert Solutions Architect working on generative AI with the Third-Party Model Science team at AWS.
    
    Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is passionate about constructing services that assist consumers accelerate their AI journey and unlock organization value.