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

Today, we are thrilled 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, along with the distilled versions varying from 1.5 to 70 billion criteria to develop, experiment, yewiki.org and properly scale your generative AI ideas on AWS.

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

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that utilizes support discovering to enhance reasoning capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A crucial distinguishing feature is its support learning (RL) action, which was utilized to improve the design’s actions beyond the basic pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adjust more efficiently to user feedback and objectives, ultimately improving both importance and clarity. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, suggesting it’s geared up to break down complex queries and factor through them in a detailed way. This directed reasoning procedure permits the model to produce more accurate, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT capabilities, aiming to generate structured responses while focusing on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has actually captured the market’s attention as a flexible text-generation model that can be integrated into numerous workflows such as representatives, sensible reasoning and data interpretation tasks.

DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, allowing effective reasoning by routing queries to the most appropriate specialist « clusters. » This approach enables the model to specialize in various issue domains while maintaining overall efficiency. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for inference. In this post, we will utilize an ml.p5e.48 xlarge instance to deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.

DeepSeek-R1 distilled designs bring the thinking abilities of the main R1 design to more effective architectures based upon popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller, more efficient designs to mimic the habits and reasoning patterns of the larger DeepSeek-R1 model, using it as an instructor design.

You can deploy 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 location. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous material, and assess models against key safety criteria. At the time of writing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the . You can create numerous guardrails tailored to various use cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing security controls throughout your generative AI applications.

Prerequisites

To deploy the DeepSeek-R1 model, you require access to an ml.p5e circumstances. To inspect 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 usage. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are releasing. To request a limitation increase, create a limitation boost request and connect to your account team.

Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) permissions to use Amazon Bedrock Guardrails. For guidelines, 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 content, and evaluate designs against crucial safety criteria. You can implement precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This allows you to use guardrails to examine user inputs and model reactions released 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, see the GitHub repo.

The general circulation includes the following steps: 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 getting the design’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 suggesting the nature of the intervention and whether it occurred at the input or output phase. The examples showcased in the following sections show reasoning using this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace gives 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, select Model brochure under Foundation models in the navigation pane.
At the time of composing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a service provider and select the DeepSeek-R1 design.

The model detail page provides necessary details about the model’s abilities, prices structure, and implementation standards. You can discover detailed use instructions, including sample API calls and code bits for integration. The design supports numerous text generation tasks, including content production, code generation, and concern answering, utilizing its reinforcement finding out optimization and CoT thinking capabilities.
The page also includes release alternatives and licensing details to assist you get going with DeepSeek-R1 in your applications.
3. To begin utilizing DeepSeek-R1, select Deploy.

You will be triggered to set up 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 Variety of circumstances, get in a number of instances (in between 1-100).
6. For example type, pick your instance type. For optimum efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, you can configure advanced security and infrastructure settings, including virtual personal cloud (VPC) networking, service function consents, and file encryption settings. For a lot of utilize cases, the default settings will work well. However, for production deployments, you might wish to examine these settings to line up with your organization’s security and compliance requirements.
7. Choose Deploy to begin using the design.

When the release is total, you can check DeepSeek-R1’s abilities straight in the Amazon Bedrock play area.
8. Choose Open in playground to access an interactive interface where you can try out various triggers and adjust design parameters like temperature level and maximum length.
When utilizing R1 with Bedrock’s InvokeModel and Playground Console, utilize DeepSeek’s chat template for ideal outcomes. For example, content for inference.

This is an excellent method to check out the model’s reasoning and text generation abilities before incorporating it into your applications. The play ground provides immediate feedback, helping you comprehend how the design reacts to different inputs and letting you tweak your triggers for ideal results.

You can rapidly check the model in the play area through the UI. However, to invoke the deployed 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 reasoning using a deployed DeepSeek-R1 design through Amazon Bedrock utilizing 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 produced the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime client, sets up inference criteria, and sends out a demand to produce text based on a user prompt.

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 few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your usage case, with your information, and release them into production utilizing either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart offers 2 hassle-free methods: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let’s explore both methods to help you choose the approach that best suits 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, pick 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 design browser shows available models, with details like the provider name and model abilities.

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

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

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

The design details page includes the following details:

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

The About tab includes important details, such as:

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

Before you release the model, it’s recommended to evaluate the design details and license terms to validate compatibility with your usage case.

6. Choose Deploy to continue with implementation.

7. For Endpoint name, utilize the automatically created name or pipewiki.org develop a customized one.
8. For Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial instance count, enter the number of instances (default: 1).
Selecting proper circumstances types and counts is essential for cost and efficiency optimization. Monitor your release to change 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 configurations for precision. For this design, we highly advise adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
11. Choose Deploy to deploy the model.

The deployment procedure can take numerous minutes to finish.

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

Deploy DeepSeek-R1 using the SageMaker Python SDK

To get going 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 permissions and environment setup. The following is a detailed code example that shows how to release and use DeepSeek-R1 for inference programmatically. The code for deploying the model is provided in the Github here. You can clone the notebook and range from SageMaker Studio.

You can run extra 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 develop a guardrail using the Amazon Bedrock console or the API, and execute it as revealed 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 model utilizing Amazon Bedrock Marketplace, total the following actions:

1. On the Amazon Bedrock console, under Foundation models in the navigation pane, choose Marketplace releases.
2. In the Managed deployments area, find the endpoint you wish to delete.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you’re erasing the appropriate implementation: 1. Endpoint name.
2. Model name.
3. 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 want 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 start. For more details, bytes-the-dust.com describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, forum.batman.gainedge.org Amazon Bedrock Marketplace, and Beginning 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 construct ingenious options using AWS services and sped up calculate. Currently, he is focused on developing methods for fine-tuning and enhancing the reasoning efficiency of big language designs. In his spare time, Vivek enjoys hiking, viewing movies, and attempting various 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 technology 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 tactical collaborations for Amazon SageMaker JumpStart, SageMaker’s artificial intelligence and generative AI center. She is passionate about building services that help customers accelerate their AI journey and unlock organization value.