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

mavishornibroo edited this page 3 months ago

Today, we are delighted 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, along with the distilled versions varying from 1.5 to 70 billion parameters to build, experiment, and responsibly scale your generative AI ideas on AWS.

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

Overview of DeepSeek-R1

DeepSeek-R1 is a big language model (LLM) developed by DeepSeek AI that uses support finding out to improve thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. An essential differentiating feature is its support knowing (RL) action, which was used to improve the model's reactions beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adapt better to user feedback and goals, ultimately boosting both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) approach, suggesting it's equipped to break down complicated queries 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 wide-ranging abilities DeepSeek-R1 has caught the industry's attention as a versatile text-generation model that can be integrated into numerous workflows such as agents, sensible thinking and data analysis jobs.

DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture allows activation of 37 billion parameters, allowing efficient reasoning by routing questions to the most relevant expert "clusters." This approach allows the design to concentrate on different issue domains while maintaining total performance. DeepSeek-R1 requires a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge circumstances to release the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs supplying 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 describes a process of training smaller, more efficient models to imitate the behavior and reasoning patterns of the larger 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 model, we suggest deploying this model with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous material, and assess models against crucial security criteria. At the time of writing this blog, for ratemywifey.com DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce numerous guardrails tailored to different use cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To deploy 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, select 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 instance in the AWS Region you are deploying. To request a limitation boost, produce a limit increase demand and reach out to your account team.

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

Implementing guardrails with the ApplyGuardrail API

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

The general 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 receiving the design's output, another guardrail check is applied. If the output passes this last check, it's returned as the result. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following areas demonstrate inference utilizing 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, total the following actions:

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

The model detail page offers essential details about the design's abilities, prices structure, and application standards. You can discover detailed usage instructions, including sample API calls and code bits for integration. The design supports various text generation tasks, including content development, code generation, and question answering, using its reinforcement learning optimization and CoT thinking capabilities. The page likewise includes deployment choices and licensing details to assist you start with DeepSeek-R1 in your applications. 3. To start utilizing DeepSeek-R1, select 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, go into an endpoint name (between 1-50 alphanumeric characters). 5. For Number of instances, go into a number of circumstances (between 1-100). 6. For example type, pick your circumstances type. For optimum performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is advised. Optionally, you can set up sophisticated security and infrastructure settings, consisting of virtual private cloud (VPC) networking, service function authorizations, and file encryption settings. For many utilize cases, the default settings will work well. However, for production deployments, you may wish to review these settings to align with your company's security and compliance requirements. 7. Choose Deploy to begin using the design.

When the implementation is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock playground. 8. Choose Open in playground to access an interactive user interface where you can experiment with various triggers and adjust model parameters like temperature and optimum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimum outcomes. For instance, content for inference.

This is an exceptional method to explore the model's thinking and text generation capabilities before incorporating it into your applications. The play ground supplies immediate feedback, helping you comprehend how the design responds to numerous inputs and letting you tweak your prompts for optimum outcomes.

You can rapidly evaluate the model in the playground through the UI. However, to conjure up the deployed model programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.

Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint

The following code example demonstrates how to perform inference utilizing a deployed DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can produce a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime client, configures reasoning parameters, and sends out a demand to create text based upon a user timely.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and prebuilt ML options that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and release them into production using either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart provides 2 practical techniques: utilizing the instinctive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both techniques to assist you pick the technique that finest matches your requirements.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

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

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

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

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

- Model name

• Provider name
• Task category (for instance, Text Generation). Bedrock Ready badge (if relevant), showing that this model can be signed up with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the design
  
  5. Choose the model card to view the design details page.
  
  The model details page consists of the following details:
  
  - The model name and company details. Deploy button to release the model. About and Notebooks tabs with detailed details
  
  The About tab includes essential details, such as:
  
  - Model description.
• License details.
• Technical requirements.
• Usage guidelines
  
  Before you deploy the design, it's recommended to evaluate the design details and license terms to validate compatibility with your use case.
  
  6. Choose Deploy to proceed with implementation.
  
  7. For Endpoint name, utilize the automatically produced name or produce a custom-made one.

8. For Instance type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, go into the variety of instances (default: 1). Selecting suitable instance types and counts is essential for expense and performance optimization. Monitor your to adjust 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 accuracy. For this model, we strongly advise adhering to SageMaker JumpStart default settings and making certain that network isolation remains in place.
11. Choose Deploy to deploy the model.
    
    The implementation process can take a number of minutes to finish.
    
    When deployment is complete, your endpoint status will change to InService. At this point, the model is all set to accept reasoning demands through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the release is total, you can conjure up the design utilizing a SageMaker runtime customer and integrate it with your applications.
    
    Deploy DeepSeek-R1 using the SageMaker Python SDK
    
    To get begun with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the essential AWS approvals 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 supplied 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 inference with your SageMaker JumpStart predictor
    
    Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce 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 steps in this area to tidy up your resources.
    
    Delete the Amazon Bedrock Marketplace deployment
    
    If you released the model using Amazon Bedrock Marketplace, total the following actions:
    
    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
12. In the Managed implementations section, find the endpoint you desire to erase.
13. Select the endpoint, and on the Actions menu, select Delete.
14. Verify the endpoint details to make certain you're erasing the right implementation: 1. Endpoint name.
15. Model name.
16. Endpoint status
    
    Delete the SageMaker JumpStart predictor
    
    The SageMaker JumpStart model you released will sustain expenses 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 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get going. 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 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 companies build ingenious solutions using AWS services and sped up compute. Currently, he is concentrated on establishing strategies for fine-tuning and enhancing the reasoning efficiency of large language designs. In his downtime, Vivek enjoys hiking, enjoying movies, and trying various 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 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 collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is passionate about constructing options that help clients accelerate their AI journey and unlock organization worth.