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

antonio6550869 edited this page 2 weeks ago

Today, we are excited to reveal that DeepSeek R1 distilled Llama and Qwen models 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, in addition to the distilled versions varying from 1.5 to 70 billion specifications to develop, experiment, and responsibly 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 release the distilled variations of the models too.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes reinforcement discovering to enhance thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base structure. A crucial differentiating function is its support knowing (RL) step, which was utilized to refine the design's reactions beyond the standard pre-training and tweak procedure. By incorporating RL, DeepSeek-R1 can adapt better to user feedback and goals, ultimately enhancing both relevance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) technique, meaning it's geared up to break down complex questions and factor through them in a detailed way. This assisted reasoning process allows the design to produce more accurate, transparent, larsaluarna.se and detailed answers. This design integrates RL-based fine-tuning with CoT abilities, aiming to create structured reactions while focusing on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has caught the market's attention as a flexible text-generation model that can be incorporated into different workflows such as agents, logical reasoning and information interpretation jobs.

DeepSeek-R1 utilizes a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture allows activation of 37 billion specifications, enabling effective reasoning by routing inquiries to the most relevant professional "clusters." This approach allows the design to focus on different issue domains while maintaining overall effectiveness. 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 deploy the model. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.

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

You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we advise releasing this model with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, prevent damaging content, and evaluate models against essential security requirements. At the time of writing this blog site, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can create multiple guardrails tailored to different usage cases and use them to the DeepSeek-R1 model, enhancing user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To deploy the DeepSeek-R1 design, 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 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 increase, produce a limit increase demand and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails permits you to introduce safeguards, avoid hazardous material, and evaluate models against key safety requirements. You can implement safety steps for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and model actions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail utilizing 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 actions: 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 design for reasoning. After getting the design's output, another guardrail check is used. 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 happened at the input or output stage. The examples showcased in the following sections demonstrate reasoning using this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace provides you access to over 100 popular, emerging, and specialized structure models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following steps:

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

The design detail page provides essential details about the design's abilities, rates structure, and application standards. You can discover detailed usage instructions, including sample API calls and code bits for combination. The design supports different text generation tasks, including material creation, code generation, and concern answering, utilizing its support finding out optimization and CoT thinking capabilities. The page also consists of implementation alternatives and licensing details to assist you start with DeepSeek-R1 in your . 3. To start utilizing DeepSeek-R1, choose Deploy.

You will be triggered to configure the deployment details for DeepSeek-R1. The model ID will be pre-populated. 4. For Endpoint name, get in an endpoint name (in between 1-50 alphanumeric characters). 5. For Number of instances, get in a variety of circumstances (in between 1-100). 6. For example type, choose your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended. Optionally, you can configure advanced security and facilities settings, consisting of virtual private cloud (VPC) networking, service role permissions, and encryption settings. For most utilize cases, the default settings will work well. However, for production deployments, you might 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 deployment is total, you can evaluate DeepSeek-R1's abilities straight in the Amazon Bedrock play ground. 8. Choose Open in playground to access an interactive interface where you can experiment with various triggers and adjust design parameters like temperature and maximum length. When utilizing R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for ideal results. For instance, content for reasoning.

This is an excellent way to check out the design's thinking and text generation abilities before integrating it into your applications. The play area offers instant feedback, helping you understand how the design reacts to various inputs and letting you tweak your prompts for ideal outcomes.

You can quickly check the design in the playground through the UI. However, to conjure up the deployed 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 demonstrates how to carry out reasoning using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have actually developed the guardrail, utilize the following code to carry out guardrails. The script initializes the bedrock_runtime client, configures reasoning specifications, and sends a demand to generate text based upon a user timely.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) center with FMs, built-in algorithms, and prebuilt ML solutions that you can deploy with just a couple of 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 design through SageMaker JumpStart offers two practical methods: using the user-friendly SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let's check out both techniques to help you choose the method that finest matches your requirements.

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 prompted to create a domain. 3. On the SageMaker Studio console, select JumpStart in the navigation pane.

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

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

- Model name

• Provider name
• Task category (for example, Text Generation). Bedrock Ready badge (if suitable), indicating that this model can be registered with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to invoke the design
  
  5. Choose the design card to see the model details page.
  
  The design details page includes the following details:
  
  - The model name and supplier details. Deploy button to release the design. About and Notebooks tabs with detailed details
  
  The About tab includes essential details, such as:
  
  - Model description.
• License details.
• Technical specs.
• Usage guidelines
  
  Before you release the model, it's suggested to review the design details and license terms to validate compatibility with your use case.
  
  6. Choose Deploy to continue with implementation.
  
  7. For Endpoint name, utilize the immediately generated name or develop a custom-made one.

8. For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of circumstances (default: 1). Selecting proper instance types and counts is vital for expense and performance optimization. Monitor your deployment to change 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 recommend sticking to SageMaker JumpStart default settings and making certain that network isolation remains in place.
11. Choose Deploy to deploy the design.
    
    The implementation procedure can take a number of minutes to complete.
    
    When implementation is complete, your endpoint status will change to InService. At this moment, the design is all set to accept reasoning demands through the endpoint. You can keep track of the deployment progress on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the deployment is total, genbecle.com you can conjure up the design utilizing a SageMaker runtime customer and integrate it with your applications.
    
    Deploy DeepSeek-R1 utilizing the SageMaker Python SDK
    
    To get going 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 consents and environment setup. The following is a detailed code example that demonstrates how to release and use DeepSeek-R1 for disgaeawiki.info reasoning programmatically. The code for releasing the model is provided in the Github here. You can clone the note pad and run from SageMaker Studio.
    
    You can run extra requests 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 develop a guardrail utilizing the Amazon Bedrock console or the API, and implement it as displayed in the following code:
    
    Tidy up
    
    To prevent undesirable charges, complete the steps in this area to clean up your resources.
    
    Delete the Amazon Bedrock Marketplace release
    
    If you released 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 releases.
12. In the Managed deployments section, find the endpoint you wish to delete.
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 design 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 checked out 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 start. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, 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 assists emerging generative AI business develop ingenious solutions utilizing AWS services and accelerated calculate. Currently, he is concentrated on establishing methods for fine-tuning and optimizing the reasoning efficiency of large language models. In his totally free time, Vivek takes pleasure in treking, viewing motion pictures, 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 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 item, engineering, and tactical collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI hub. She is passionate about developing options that help clients accelerate their AI journey and unlock company worth.