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 release DeepSeek AI‘s first-generation frontier model, DeepSeek-R1, in addition to the distilled variations ranging from 1.5 to 70 billion criteria to develop, experiment, and responsibly scale your generative AI concepts 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 versions of the designs as well.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language model (LLM) developed by DeepSeek AI that uses reinforcement discovering to boost thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential identifying feature is its reinforcement learning (RL) step, which was used to refine the model’s actions beyond the standard pre-training and tweak procedure. By including RL, DeepSeek-R1 can adjust more effectively to user feedback and goals, eventually boosting both importance and clarity. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, implying it’s geared up to break down complicated inquiries and reason through them in a detailed way. This directed reasoning procedure enables the model to produce more precise, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured responses while focusing on interpretability and user interaction. With its extensive capabilities DeepSeek-R1 has recorded the market’s attention as a flexible text-generation model that can be incorporated into different workflows such as representatives, rational reasoning and information interpretation jobs.

DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture enables activation of 37 billion criteria, enabling effective inference by routing queries to the most relevant professional « clusters. » This approach permits the model to specialize in various issue domains while maintaining overall performance. DeepSeek-R1 requires a minimum of 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 design. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.

DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 model to more efficient architectures based upon popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a process of training smaller sized, more effective models to mimic the behavior and reasoning patterns of the bigger DeepSeek-R1 design, utilizing it as a teacher design.

You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend releasing this model with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to introduce safeguards, avoid harmful content, and assess designs against crucial security requirements. At the time of composing this blog, for DeepSeek-R1 deployments 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 model, improving user experiences and standardizing safety controls throughout your generative AI applications.

Prerequisites

To release the DeepSeek-R1 design, you require access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, select Amazon SageMaker, and forum.batman.gainedge.org validate 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 request a limitation increase, develop a limit boost demand and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to introduce safeguards, prevent hazardous material, and demo.qkseo.in examine designs against crucial safety requirements. You can execute safety measures for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to evaluate user inputs and design responses released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail utilizing the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.

The general circulation includes the following actions: First, the system receives 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 reasoning. After receiving the design’s output, another guardrail check is applied. 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 showing the nature of the intervention and whether it happened 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 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 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 service provider and pick the DeepSeek-R1 model.

The model detail page offers vital details about the design’s capabilities, rates structure, and yewiki.org application standards. You can discover detailed usage guidelines, including sample API calls and code snippets for combination. The design supports various text generation tasks, consisting of material development, code generation, and question answering, utilizing its support discovering optimization and CoT thinking capabilities.
The page also includes release options and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, archmageriseswiki.com choose Deploy.

You will be prompted to configure the implementation 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 (in between 1-100).
6. For example type, select your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
Optionally, you can configure innovative security and facilities settings, including virtual personal cloud (VPC) networking, service role permissions, and file encryption settings. For most utilize cases, the default settings will work well. However, for production releases, you might wish to examine these settings to align with your company’s security and compliance requirements.
7. Choose Deploy to start using the model.

When the release is complete, you can evaluate DeepSeek-R1’s abilities straight in the Amazon Bedrock play area.
8. Choose Open in play area to access an interactive user interface where you can try out various prompts and change model parameters like temperature and optimum length.
When utilizing R1 with Bedrock’s InvokeModel and Playground Console, use DeepSeek’s chat template for optimal outcomes. For instance, content for inference.

This is an outstanding way to explore the design’s reasoning and text generation capabilities before incorporating it into your applications. The play ground offers instant feedback, helping you comprehend how the model responds to numerous inputs and letting you tweak your prompts for ideal results.

You can rapidly check the model in the play area 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 utilizing guardrails with the released DeepSeek-R1 endpoint

The following code example demonstrates how to carry out inference using a deployed 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 actually created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures inference parameters, 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 services that you can release with just a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your data, and release them into production utilizing either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart uses 2 convenient techniques: utilizing the instinctive SageMaker JumpStart UI or implementing programmatically through the SageMaker Python SDK. Let’s explore both techniques to assist you pick the method that finest suits your needs.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

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

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

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

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

– Model name
– Provider name
– Task category (for example, 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 invoke the model

5. Choose the model card to view the model details page.

The model details page consists of the following details:

– The model name and service 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 specs.
– Usage standards

Before you release the design, it’s suggested to review the model details and license terms to validate compatibility with your use case.

6. Choose Deploy to continue with deployment.

7. For Endpoint name, utilize the automatically generated name or create a customized one.
8. For Instance type ¸ pick an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the number of instances (default: hb9lc.org 1).
Selecting suitable circumstances types and counts is essential for expense and performance optimization. Monitor your implementation 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 design, we strongly advise adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the model.

The implementation process can take several minutes to complete.

When release is total, your endpoint status will alter to InService. At this point, the design is ready to accept reasoning demands through the . You can monitor the deployment development on the SageMaker console Endpoints page, which will show relevant metrics and status details. When the release is complete, 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 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the required AWS permissions and environment setup. The following is a detailed code example that demonstrates how to release and use DeepSeek-R1 for reasoning programmatically. The code for deploying the design is supplied in the Github here. You can clone the note pad 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 likewise utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:

Tidy up

To avoid undesirable charges, complete the steps in this section to clean up your resources.

Delete the Amazon Bedrock Marketplace deployment

If you deployed the design utilizing Amazon Bedrock Marketplace, total the following actions:

1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace deployments.
2. In the Managed deployments area, locate the endpoint you want to erase.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you’re erasing the proper implementation: 1. Endpoint name.
2. Model name.
3. 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 erase the endpoint if you wish to stop sustaining charges. For more details, see Delete Endpoints and systemcheck-wiki.de Resources.

Conclusion

In this post, we explored how you can access and release the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. 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 Getting begun 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 develop ingenious services using AWS services and accelerated compute. Currently, he is concentrated on developing strategies for fine-tuning and enhancing the reasoning efficiency of big language models. In his spare time, Vivek enjoys treking, viewing motion pictures, and attempting different cuisines.

Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science team at AWS. His area 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 product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker’s artificial intelligence and generative AI center. She is passionate about constructing solutions that help customers accelerate their AI journey and unlock organization value.