1 DeepSeek R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart

theoeck566384 edited this page 1 week ago

Today, we are excited to reveal 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, together with the distilled variations varying from 1.5 to 70 billion specifications to build, experiment, and responsibly scale your generative AI concepts 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 models also.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes reinforcement discovering to boost thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key identifying feature is its support knowing (RL) action, which was used to refine the model'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 enhancing both significance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) technique, suggesting it's equipped to break down complicated inquiries and factor through them in a detailed manner. This guided reasoning procedure allows the model to produce more precise, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT abilities, aiming to produce structured responses while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has actually recorded the market's attention as a flexible text-generation design that can be integrated into various workflows such as representatives, logical reasoning and information analysis jobs.

DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion specifications, enabling effective inference by routing queries to the most pertinent specialist "clusters." This method permits the design to focus on various issue domains while maintaining general 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 deploy the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.

DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 model to more efficient architectures based on popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller, more efficient designs to simulate the behavior and reasoning patterns of the bigger DeepSeek-R1 model, using it as an instructor model.

You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest deploying this model with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent damaging material, and examine designs against crucial safety criteria. At the time of writing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop several 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 model, you require access to an ml.p5e circumstances. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and verify you're using ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are deploying. To ask for a limit boost, develop a limitation increase demand and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to introduce safeguards, prevent damaging content, and evaluate designs against key safety criteria. You can execute safety steps for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This allows you to apply guardrails to assess user inputs and design responses deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail using the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo.

The basic flow includes the following steps: First, the system gets 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 . After getting the design's output, another guardrail check is applied. If the output passes this last check, it's returned as the last outcome. However, if either the input or output is intervened by the guardrail, a message is returned suggesting the nature of the intervention and whether it occurred at the input or output phase. The examples showcased in the following sections show reasoning utilizing this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock 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 brochure under Foundation designs 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 company and select the DeepSeek-R1 model.

The design detail page supplies essential details about the model's capabilities, prices structure, and implementation guidelines. You can find detailed use directions, consisting of sample API calls and code bits for integration. The model supports various text generation tasks, including material creation, code generation, and question answering, using its reinforcement finding out optimization and CoT reasoning capabilities. The page also includes deployment alternatives and licensing details to help you start with DeepSeek-R1 in your applications. 3. To begin utilizing DeepSeek-R1, pick Deploy.

You will be triggered to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated. 4. For Endpoint name, enter an endpoint name (between 1-50 alphanumeric characters). 5. For Variety of instances, enter a variety of instances (in 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 recommended. Optionally, surgiteams.com you can set up sophisticated security and facilities settings, consisting of virtual private 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 may desire to evaluate these settings to align with your organization'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 play ground. 8. Choose Open in playground to access an interactive user interface where you can try out different triggers and adjust design criteria like temperature level and optimum length. When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat template for ideal outcomes. For example, content for reasoning.

This is an outstanding method to explore the model's thinking and text generation capabilities before integrating it into your applications. The play ground offers instant feedback, helping you understand how the design reacts to different inputs and letting you fine-tune your triggers for optimal results.

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

Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint

The following code example shows how to perform reasoning using a released DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can develop 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 developed the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures inference parameters, and sends a request to create text based on a user timely.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and prebuilt ML solutions that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs 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: utilizing the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's explore both approaches to assist you select the technique that best matches your needs.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

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

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

The model internet browser displays available designs, with details like the provider name and model abilities.

4. Search for DeepSeek-R1 to see the DeepSeek-R1 design card. Each model card shows essential details, including:

- Model name

• Provider name
• Task category (for example, Text Generation). Bedrock Ready badge (if relevant), showing that this design can be signed up with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to invoke 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 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 specs.
• Usage standards
  
  Before you deploy the model, it's recommended to evaluate the model details and license terms to validate compatibility with your use case.
  
  6. Choose Deploy to continue with release.
  
  7. For Endpoint name, use the immediately generated name or produce a customized one.

8. For example type ¸ select an instance type (default: trademarketclassifieds.com ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of circumstances (default: 1). Selecting appropriate instance types and counts is crucial for cost and efficiency optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time inference is chosen by default. This is optimized for sustained traffic and low latency.
10. Review all setups for precision. For this model, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to release the design.
    
    The implementation process can take a number of minutes to finish.
    
    When release is total, your endpoint status will alter to InService. At this moment, the design is prepared to accept reasoning demands through the endpoint. You can keep track of the release progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the implementation is total, you can conjure up the model using a SageMaker runtime client and integrate it with your applications.
    
    Deploy DeepSeek-R1 utilizing the SageMaker Python SDK
    
    To get begun with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the required AWS authorizations and environment setup. The following is a detailed code example that shows how to release and utilize DeepSeek-R1 for reasoning programmatically. The code for deploying the design is provided in the Github here. You can clone the notebook 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 also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail utilizing the Amazon Bedrock console or the API, yewiki.org and execute it as displayed in the following code:
    
    Clean up
    
    To avoid undesirable charges, finish the actions in this area to tidy up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you released the design using Amazon Bedrock Marketplace, complete the following steps:
    
    1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, garagesale.es select Marketplace deployments.
12. In the Managed implementations area, find the endpoint you desire to delete.
13. Select the endpoint, and on the Actions menu, pick Delete.
14. Verify the endpoint details to make certain you're erasing the correct deployment: 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 want 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 start. For more details, refer to 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 build innovative services utilizing AWS services and accelerated calculate. Currently, he is focused on developing strategies for fine-tuning and enhancing the reasoning performance of large language designs. In his downtime, Vivek delights in treking, watching motion pictures, and trying different cuisines.
    
    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 Specialist Solutions Architect working on generative AI with the Third-Party Model Science group at AWS.
    
    Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI hub. She is enthusiastic about constructing options that assist clients accelerate their AI journey and unlock service value.