GitLab

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 model, DeepSeek-R1, in addition to the distilled variations varying from 1.5 to 70 billion parameters to develop, experiment, and properly scale your generative AI ideas on AWS.

In this post, we demonstrate how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar steps to deploy the distilled variations of the models also.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes support learning to improve thinking abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A crucial differentiating feature is its reinforcement learning (RL) action, which was used to refine the design's reactions beyond the standard pre-training and tweak process. By integrating RL, DeepSeek-R1 can adapt more effectively to user feedback and goals, ultimately improving both importance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) approach, meaning it's geared up to break down complicated inquiries and reason through them in a detailed way. This assisted reasoning process permits the design to produce more precise, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT capabilities, aiming to create structured reactions while focusing on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has captured the market's attention as a flexible text-generation model that can be integrated into numerous workflows such as agents, logical reasoning and data interpretation tasks.

DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion parameters, making it possible for effective inference by routing queries to the most relevant professional "clusters." This method allows the model to focus on various issue domains while maintaining total efficiency. 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 instance to release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.

DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 model to more effective architectures based on popular open models 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 thinking patterns of the larger DeepSeek-R1 design, utilizing it as a teacher model.

You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest releasing this design with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to introduce safeguards, prevent harmful content, and evaluate designs against crucial security requirements. At the time of writing 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 different use cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To deploy the DeepSeek-R1 design, 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 verify 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 increase request and reach out to your account group.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to present safeguards, prevent damaging content, and assess designs against crucial safety criteria. You can carry out precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to use guardrails to assess user inputs and design actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail utilizing the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.

The general flow 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 getting the model's output, another guardrail check is used. If the output passes this final check, it's returned as the final outcome. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the intervention and engel-und-waisen.de whether it occurred at the input or output phase. The examples showcased in the following areas show reasoning using this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Marketplace gives 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 steps:

1. On the Amazon Bedrock console, pick Model catalog under Foundation designs in the navigation pane. At the time of writing this post, you can use 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 provider and select the DeepSeek-R1 model.

The design detail page offers necessary details about the design's capabilities, prices structure, and execution standards. You can find detailed usage instructions, consisting of sample API calls and code snippets for combination. The design supports numerous text generation jobs, consisting of content production, code generation, and question answering, using its support finding out optimization and CoT reasoning capabilities. The page also includes release alternatives and licensing details to assist you start with DeepSeek-R1 in your applications. 3. To begin using DeepSeek-R1, choose Deploy.

You will be prompted to set up the implementation details for DeepSeek-R1. The model ID will be pre-populated. 4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters). 5. For Variety of instances, get in a variety of circumstances (between 1-100). 6. For example type, choose your instance type. For ideal performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended. Optionally, you can configure sophisticated security and facilities settings, consisting of virtual personal cloud (VPC) networking, service role consents, and file encryption settings. For most utilize cases, the default settings will work well. However, for production releases, you may wish to evaluate these settings to line up with your organization's security and compliance requirements. 7. Choose Deploy to begin using the design.

When the implementation is complete, you can test DeepSeek-R1's abilities straight in the Amazon Bedrock play ground. 8. Choose Open in play ground to access an interactive interface where you can experiment with different triggers and adjust model criteria like temperature and optimum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal outcomes. For instance, content for inference.

This is an exceptional way to check out the model's reasoning and text generation capabilities before integrating it into your applications. The play ground provides immediate feedback, assisting you understand how the model reacts to various inputs and letting you tweak your triggers for optimal results.

You can rapidly evaluate the model 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 perform inference using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce 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 developed the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime client, sets up reasoning specifications, and sends a request to create text based upon 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 release with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs 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 provides 2 practical methods: utilizing the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both methods to help you select the approach that finest fits 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 prompted to develop a domain. 3. On the SageMaker Studio console, select JumpStart in the navigation pane.

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

4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card. Each design card reveals key details, including:

- Model name

• Provider name
• Task category (for instance, Text Generation). Bedrock Ready badge (if appropriate), showing that this design can be registered with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to invoke the model
  
  5. Choose the design card to see the design details page.
  
  The model details page includes the following details:
  
  - The model name and service provider details. Deploy button to deploy the model. About and Notebooks tabs with detailed details
  
  The About tab includes important details, such as:
  
  - Model description.
• License details.
• Technical specs.
• Usage standards
  
  Before you deploy the design, it's suggested 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, utilize the instantly created name or develop a custom one.

8. For example type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the number of instances (default: 1). Selecting suitable circumstances types and counts is vital for expense and efficiency optimization. Monitor your implementation to change these settings as needed.Under Inference type, Real-time reasoning is selected by default. This is enhanced for sustained traffic and low latency.
10. Review all configurations for precision. For this model, we highly advise adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the model.
    
    The deployment process can take numerous minutes to complete.
    
    When implementation is total, your endpoint status will change to InService. At this moment, the design is ready to accept reasoning requests through the endpoint. You can keep track of the implementation progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the deployment is complete, you can invoke the model utilizing a SageMaker runtime customer and integrate it with your applications.
    
    Deploy DeepSeek-R1 utilizing the SageMaker Python SDK
    
    To begin with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the required AWS authorizations 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 releasing the design is provided in the Github here. You can clone the note pad and run from SageMaker Studio.
    
    You can run additional 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 displayed in the following code:
    
    Tidy up
    
    To prevent unwanted charges, complete the steps in this section to tidy up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you deployed the model utilizing Amazon Bedrock Marketplace, total the following steps:
    
    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
12. In the Managed releases area, locate the endpoint you want to erase.
13. Select the endpoint, and on the Actions menu, pick Delete.
14. Verify the endpoint details to make certain you're deleting the right release: 1. Endpoint name.
15. Model name.
16. Endpoint status
    
    Delete the SageMaker JumpStart predictor
    
    The SageMaker JumpStart model you released 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 deploy the DeepSeek-R1 design 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 models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting 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 solutions using AWS services and sped up compute. Currently, he is focused on establishing techniques for fine-tuning and enhancing the inference performance of large language models. In his free time, Vivek delights in treking, enjoying films, and trying various cuisines.
    
    Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science team 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 dealing with generative AI with the Third-Party Model Science team at AWS.
    
    Banu Nagasundaram leads product, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is enthusiastic about developing solutions that help clients accelerate their AI journey and unlock organization value.