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

jenifergrattan edited this page 4 months ago

Today, we are thrilled 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 model, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion specifications to develop, experiment, and properly scale your generative AI concepts on AWS.

In this post, we show how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to deploy the distilled variations of the designs as well.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes reinforcement learning to boost reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key differentiating function is its support learning (RL) action, which was used to refine the model's reactions beyond the standard pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adjust more effectively to user feedback and objectives, eventually improving both significance and clarity. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, suggesting it's equipped to break down complex queries and reason through them in a detailed manner. This assisted reasoning procedure enables the design to produce more accurate, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT abilities, aiming to create structured actions while concentrating on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has caught the industry's attention as a versatile text-generation design that can be incorporated into different workflows such as agents, sensible thinking and data analysis tasks.

DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture enables activation of 37 billion parameters, enabling effective reasoning by routing questions to the most pertinent expert "clusters." This method allows the model to specialize in various issue domains while maintaining overall effectiveness. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs providing 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 models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller, more effective models to simulate the habits and thinking patterns of the larger DeepSeek-R1 design, utilizing it as a teacher model.

You can deploy DeepSeek-R1 model 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 damaging content, and assess designs against key security criteria. At the time of writing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can develop several guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, improving user experiences and standardizing safety controls across your generative AI applications.

Prerequisites

To release 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, pick Amazon SageMaker, and confirm you're utilizing 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 releasing. To request a limitation boost, develop a limit boost request and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails enables you to present safeguards, avoid damaging material, and evaluate models against crucial safety requirements. You can implement safety procedures for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to examine user inputs and hb9lc.org model actions deployed 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 develop the guardrail, surgiteams.com see the GitHub repo.

The general circulation involves the following steps: First, the system gets an input for the design. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the model 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 final 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 stage. The examples showcased in the following areas show reasoning utilizing this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized foundation models (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 utilize the InvokeModel API to invoke the model. It doesn't support Converse APIs and other Amazon Bedrock tooling. 2. Filter for DeepSeek as a company and select the DeepSeek-R1 design.

The design detail page offers important details about the design's capabilities, prices structure, and application guidelines. You can discover detailed use instructions, including sample API calls and code snippets for integration. The design supports numerous text generation jobs, including content production, code generation, and concern answering, utilizing its support finding out optimization and CoT reasoning abilities. The page likewise consists of implementation options and licensing details to help you get begun with DeepSeek-R1 in your applications. 3. To begin utilizing DeepSeek-R1, pick Deploy.

You will be triggered to configure the release details for DeepSeek-R1. The design ID will be pre-populated. 4. For Endpoint name, higgledy-piggledy.xyz get in an endpoint name (in between 1-50 alphanumeric characters). 5. For Variety of circumstances, go into a number of circumstances (in between 1-100). 6. For Instance type, choose your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested. Optionally, you can configure sophisticated security and facilities settings, consisting of virtual private cloud (VPC) networking, service role approvals, and encryption settings. For most use cases, the default settings will work well. However, for production deployments, you may wish to examine these settings to line up with your organization's security and compliance requirements. 7. Choose Deploy to start utilizing the design.

When the release is total, 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 explore various triggers and adjust model parameters like temperature and maximum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat design template for optimal results. For instance, content for inference.

This is an outstanding way to check out the model's thinking and text generation abilities before incorporating it into your applications. The play area offers instant feedback, helping you comprehend how the design reacts to various inputs and letting you fine-tune your prompts for ideal outcomes.

You can rapidly check the design in the play ground 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 released DeepSeek-R1 endpoint

The following code example shows how to carry out inference using a released DeepSeek-R1 model through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. 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. After you have created the guardrail, use the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up inference specifications, and sends out a request 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 engel-und-waisen.de prebuilt ML services that you can deploy with simply a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your data, and release them into production using either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart offers two hassle-free approaches: utilizing the user-friendly SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both techniques to help you pick the technique that best suits your needs.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

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

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

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

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

- Model name

• Provider name
• Task category (for instance, Text Generation). Bedrock Ready badge (if relevant), showing that this model can be registered with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to conjure up the design
  
  5. Choose the design card to view the model details page.
  
  The model details page consists of the following details:
  
  - The model name and supplier details. Deploy button to deploy the model. About and Notebooks tabs with detailed details
  
  The About tab consists of essential details, such as:
  
  - Model description.
• License details.
• Technical specifications.
• Usage standards
  
  Before you deploy the design, it's recommended to review the design details and license terms to validate compatibility with your usage case.
  
  6. Choose Deploy to continue with deployment.
  
  7. For Endpoint name, utilize the automatically produced name or develop a custom one.

8. For higgledy-piggledy.xyz Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the number of circumstances (default: 1). Selecting appropriate circumstances types and counts is essential for cost and efficiency optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is optimized for sustained traffic and low latency.
10. Review all setups for precision. For this design, we highly suggest adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
11. Choose Deploy to deploy the model.
    
    The implementation procedure can take a number of minutes to complete.
    
    When deployment is complete, your endpoint status will alter to InService. At this moment, the model is ready to accept inference demands through the endpoint. You can monitor the implementation development on the SageMaker console Endpoints page, which will show appropriate metrics and status details. When the deployment is complete, you can conjure up the design utilizing a SageMaker runtime customer and incorporate it with your applications.
    
    Deploy DeepSeek-R1 using the SageMaker Python SDK
    
    To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed 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 releasing the design is offered 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 also 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 displayed in the following code:
    
    Tidy up
    
    To prevent unwanted charges, finish the steps in this section to clean up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you deployed the design using Amazon Bedrock Marketplace, total the following steps:
    
    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace implementations.
12. In the Managed implementations area, find the endpoint you wish to erase.
13. Select the endpoint, and forum.pinoo.com.tr on the Actions menu, select Delete.
14. Verify the endpoint details to make certain you're deleting the appropriate release: 1. Endpoint name.
15. Model name.
16. Endpoint status
    
    Delete the SageMaker JumpStart predictor
    
    The SageMaker JumpStart design you deployed 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 deploy the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get begun. 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 begun 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 develop ingenious solutions utilizing AWS services and sped up compute. Currently, he is concentrated on establishing strategies for fine-tuning and optimizing the inference performance of large language designs. In his downtime, Vivek delights in treking, watching movies, 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 Science and Bioinformatics.
    
    Jonathan Evans is an Expert Solutions Architect working on generative AI with the Third-Party Model Science group at AWS.
    
    Banu Nagasundaram leads product, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial and generative AI hub. She is enthusiastic about building services that assist customers accelerate their AI journey and unlock organization worth.