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

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

In this post, we show how to get begun with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to release the distilled variations of the designs as well.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) established by DeepSeek AI that utilizes reinforcement discovering to improve reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A key identifying feature is its reinforcement knowing (RL) step, which was used to improve the design’s actions beyond the standard pre-training and tweak procedure. By integrating RL, DeepSeek-R1 can adapt more efficiently to user feedback and objectives, eventually boosting both relevance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) approach, meaning it’s equipped to break down complicated queries and reason through them in a detailed manner. This assisted thinking procedure permits the design to produce more accurate, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT abilities, aiming to produce structured actions while concentrating 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 various workflows such as representatives, logical reasoning and information analysis tasks.

DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, enabling efficient reasoning by routing inquiries to the most appropriate professional “clusters.” This approach enables the design to focus on various problem domains while maintaining general effectiveness. 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 deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.

DeepSeek-R1 distilled models bring the thinking abilities of the main R1 design 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 efficient designs to imitate the behavior and reasoning patterns of the bigger DeepSeek-R1 model, utilizing it as a teacher model.

You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest deploying this design with guardrails in location. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid damaging material, and examine models against essential safety requirements. 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 create several guardrails tailored to various use cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To release 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, pick Amazon SageMaker, and confirm 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 releasing. To ask for a limitation boost, create a limitation increase request 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) authorizations to use Amazon Bedrock Guardrails. For guidelines, see Establish permissions to utilize guardrails for material filtering.

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to present safeguards, prevent hazardous content, and assess models against essential security criteria. You can execute safety procedures for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and model responses deployed on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, wiki.dulovic.tech see the GitHub repo.

The general flow includes 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 to the model for inference. After receiving the model’s output, another guardrail check is used. If the output passes this last check, it’s returned as the outcome. However, if either the input or output is intervened by the guardrail, a message is returned indicating the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following areas demonstrate 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 actions:

1. On the Amazon Bedrock console, pick Model catalog under Foundation models in the navigation pane.
At the time of writing this post, you can utilize the InvokeModel API to conjure up the model. 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 design detail page offers important details about the design’s capabilities, prices structure, and execution guidelines. You can discover detailed usage guidelines, including sample API calls and code bits for combination. The design supports numerous text generation jobs, including material development, code generation, and concern answering, using its reinforcement finding out optimization and CoT reasoning capabilities.
The page likewise consists of release options and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, select Deploy.

You will be prompted to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of circumstances, get in a variety of circumstances (between 1-100).
6. For example type, choose your circumstances type. For optimum performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up innovative security and facilities settings, including virtual private cloud (VPC) networking, service role consents, and encryption settings. For most utilize cases, the default settings will work well. However, for production implementations, you may want to evaluate these settings to line up with your company’s security and compliance requirements.
7. Choose Deploy to begin utilizing the model.

When the implementation is complete, you can test DeepSeek-R1’s abilities straight in the Amazon Bedrock play area.
8. Choose Open in play ground to access an interactive interface where you can try out different prompts and adjust design criteria like temperature and optimum length.
When utilizing R1 with Bedrock’s InvokeModel and Playground Console, use DeepSeek’s chat design template for optimal results. For example, material for reasoning.

This is an exceptional method to explore the design’s reasoning and text generation abilities before incorporating it into your applications. The play ground supplies instant feedback, assisting you comprehend how the model responds to numerous inputs and letting you fine-tune your prompts for optimum results.

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

Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint

The following code example shows how to perform inference using a deployed DeepSeek-R1 model 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 create the guardrail, see the GitHub repo. After you have actually created the guardrail, use the following code to execute guardrails. The script initializes the bedrock_runtime customer, configures inference specifications, and sends a demand to create text based upon a user prompt.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, built-in algorithms, and prebuilt ML solutions that you can deploy with just a couple of clicks. With SageMaker JumpStart, higgledy-piggledy.xyz you can tailor pre-trained designs to your usage case, with your information, and deploy them into production using either the UI or raovatonline.org SDK.

Deploying DeepSeek-R1 design through SageMaker JumpStart offers two hassle-free approaches: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let’s explore both approaches to assist you pick the approach that finest matches your requirements.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

Complete the following actions to deploy DeepSeek-R1 using 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 design web browser displays available designs, with details like the provider name and model abilities.

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

– Model name
– Provider name
– Task category (for example, Text Generation).
Bedrock Ready badge (if relevant), indicating that this design can be registered with Amazon Bedrock, 35.237.164.2 enabling you to use Amazon Bedrock APIs to conjure up the model

5. Choose the design card to see the model details page.

The design details page consists of the following details:

– The model name and provider details.
Deploy button to deploy the design.
About and Notebooks tabs with detailed details

The About tab consists of important details, such as:

– Model description.
– License details.
– Technical requirements.
– Usage guidelines

Before you deploy the design, it’s advised to evaluate the design details and license terms to confirm compatibility with your usage case.

6. Choose Deploy to continue with release.

7. For Endpoint name, utilize the instantly generated name or produce a custom one.
8. For example type ¸ select a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, get in the number of instances (default: 1).
Selecting proper circumstances types and counts is essential for expense and efficiency optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time inference is chosen by default. This is enhanced for sustained traffic and low latency.
10. Review all configurations for accuracy. For this design, we strongly advise sticking 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 several minutes to complete.

When release is total, your endpoint status will change to InService. At this moment, the model is ready to accept reasoning demands through the endpoint. You can keep an eye on the deployment development on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the implementation is complete, you can conjure up the design using a SageMaker runtime client and integrate it with your applications.

Deploy DeepSeek-R1 utilizing the SageMaker Python SDK

To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to set up the SageMaker Python SDK and make certain you have the necessary AWS permissions and it-viking.ch environment setup. The following is a detailed code example that shows how to deploy and utilize DeepSeek-R1 for reasoning programmatically. The code for releasing the design is supplied in the Github here. You can clone the notebook and run from SageMaker Studio.

You can run additional requests 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 using the Amazon Bedrock console or the API, and implement it as revealed in the following code:

Tidy up

To prevent unwanted charges, complete the steps in this section to clean up your resources.

Delete the Amazon Bedrock Marketplace release

If you deployed the design utilizing Amazon Bedrock Marketplace, complete the following steps:

1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace releases.
2. In the Managed implementations area, locate the endpoint you desire to erase.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you’re deleting the right release: 1. Endpoint name.
2. Model name.
3. 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 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 deploy 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 designs, 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 links.gtanet.com.br Inference at AWS. He helps emerging generative AI companies build ingenious services using AWS services and sped up compute. Currently, he is focused on developing methods for fine-tuning and enhancing the inference performance of big language models. In his leisure time, Vivek enjoys treking, watching movies, and attempting different foods.

Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model 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 dealing with generative AI with the Third-Party Model Science team at AWS.

Banu Nagasundaram leads item, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker’s artificial intelligence and generative AI center. She is enthusiastic about building solutions that help clients accelerate their AI journey and unlock service worth.