1 DeepSeek R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart
Devin Spady редактировал эту страницу 4 месяцев назад


Today, we are delighted 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 deploy DeepSeek AI’s first-generation frontier model, DeepSeek-R1, along with the distilled versions ranging from 1.5 to 70 billion criteria to build, experiment, and properly scale your generative AI concepts on AWS.

In this post, we demonstrate how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable actions to deploy the distilled variations of the designs also.

Overview of DeepSeek-R1

DeepSeek-R1 is a large language design (LLM) established by DeepSeek AI that utilizes reinforcement learning to boost reasoning abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key identifying function is its support knowing (RL) action, which was used to improve the model’s actions beyond the basic pre-training and tweak process. By incorporating RL, DeepSeek-R1 can adjust more successfully to user feedback and objectives, ultimately enhancing both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) technique, suggesting it’s equipped to break down complicated queries and factor through them in a detailed way. This directed thinking process allows the design to produce more accurate, transparent, and detailed responses. This model integrates RL-based fine-tuning with CoT abilities, aiming to generate structured actions while concentrating on interpretability and user interaction. With its extensive abilities DeepSeek-R1 has captured the industry’s attention as a versatile text-generation model that can be incorporated into various workflows such as agents, logical thinking and information analysis jobs.

DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion parameters, enabling efficient reasoning by routing questions to the most appropriate professional “clusters.” This technique enables the model to specialize in various issue 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 utilize an ml.p5e.48 xlarge circumstances to release 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 abilities of the main R1 model 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 sized, more efficient designs to imitate the habits and reasoning patterns of the larger DeepSeek-R1 model, utilizing it as an instructor model.

You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we advise deploying this design with guardrails in place. In this blog, we will use Guardrails to present safeguards, prevent hazardous material, and evaluate designs against essential security criteria. 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 multiple guardrails tailored to different use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls across your generative AI applications.

Prerequisites

To release the DeepSeek-R1 design, you need access to an ml.p5e circumstances. To check if you have quotas for P5e, open the Service Quotas console and under AWS Services, choose Amazon SageMaker, and verify you’re using ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are deploying. To request a limitation increase, produce a limitation boost request and reach out to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to present safeguards, avoid harmful content, and evaluate designs against essential security requirements. You can carry out precaution for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to examine user inputs and design reactions released 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 create the guardrail, see the GitHub repo.

The basic flow involves the following steps: 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 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, bytes-the-dust.com if either the input or output is stepped in by the guardrail, a message is returned showing the nature of the intervention and whether it occurred at the input or output stage. The examples showcased in the following areas demonstrate inference utilizing 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 actions:

1. On the Amazon Bedrock console, pick Model brochure 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 does not support Converse APIs and other Amazon Bedrock tooling.

  1. Filter for DeepSeek as a service provider and select the DeepSeek-R1 design.

    The model detail page provides essential details about the design’s abilities, pricing structure, and application standards. You can find detailed usage directions, forum.altaycoins.com consisting of sample API calls and code snippets for combination. The design supports different text generation tasks, consisting of material creation, code generation, and concern answering, utilizing its reinforcement finding out optimization and CoT thinking capabilities. The page likewise consists of release options and licensing details to help you get begun with DeepSeek-R1 in your applications.
  2. To begin utilizing DeepSeek-R1, select Deploy.

    You will be triggered to configure the release details for DeepSeek-R1. The model ID will be pre-populated.
  3. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
  4. For Number of instances, enter a number of circumstances (in between 1-100).
  5. For Instance type, choose your circumstances type. For optimal performance with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested. Optionally, you can set up sophisticated security and facilities settings, consisting of virtual private cloud (VPC) networking, service function permissions, and encryption settings. For the majority of utilize cases, the default settings will work well. However, for production implementations, you may wish to review these settings to line up with your organization’s security and compliance requirements.
  6. Choose Deploy to begin utilizing the model.

    When the release is total, you can evaluate DeepSeek-R1’s capabilities straight in the Amazon Bedrock playground.
  7. Choose Open in play area to access an interactive interface where you can experiment with various prompts and change design specifications like temperature level and maximum length. When utilizing R1 with Bedrock’s InvokeModel and Playground Console, use DeepSeek’s chat design template for optimal outcomes. For example, material for reasoning.

    This is an outstanding way to check out the design’s reasoning and text generation capabilities before integrating it into your applications. The playground supplies immediate feedback, assisting you comprehend how the design responds to different inputs and letting you tweak your triggers for ideal results.

    You can rapidly test the model in the play ground through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.

    Run reasoning utilizing guardrails with the released DeepSeek-R1 endpoint

    The following code example demonstrates how to perform inference using a released DeepSeek-R1 design through Amazon Bedrock using 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 actually created the guardrail, utilize the following code to execute guardrails. The script initializes the bedrock_runtime client, sets up 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) center with FMs, integrated algorithms, and prebuilt ML options that you can deploy with just a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your data, and deploy them into production using either the UI or SDK.

    Deploying DeepSeek-R1 design through SageMaker JumpStart offers two practical techniques: using the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let’s check out both approaches to assist you pick the approach that best matches your needs.

    Deploy DeepSeek-R1 through SageMaker JumpStart UI

    Complete the following actions to deploy DeepSeek-R1 using SageMaker JumpStart:

    1. On the SageMaker console, bytes-the-dust.com choose Studio in the navigation pane.
  8. First-time users will be triggered to produce a domain.
  9. On the SageMaker Studio console, pick JumpStart in the navigation pane.

    The model internet browser shows available designs, with details like the service provider name and model abilities.

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

    - Model name
  10. Provider name
  11. Task classification (for instance, surgiteams.com Text Generation). Bedrock Ready badge (if applicable), suggesting that this design can be signed up with Amazon Bedrock, allowing you to use Amazon Bedrock APIs to conjure up the model

    5. Choose the design 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 release the design. About and Notebooks tabs with detailed details

    The About tab includes crucial details, such as:

    - Model description.
  12. License details.
  13. Technical specifications.
  14. Usage standards

    Before you deploy the design, it’s suggested to examine the model details and license terms to validate compatibility with your usage case.

    6. Choose Deploy to proceed with implementation.

    7. For Endpoint name, use the automatically produced name or produce a customized one.
  15. For Instance type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
  16. For Initial circumstances count, get in the variety of instances (default: 1). Selecting proper circumstances types and counts is vital for cost and efficiency optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time reasoning is picked by default. This is enhanced for sustained traffic and low latency.
  17. Review all setups for precision. For this model, we highly recommend sticking to SageMaker JumpStart default settings and making certain that network seclusion remains in place.
  18. Choose Deploy to release the design.

    The release process can take several minutes to complete.

    When deployment is complete, your endpoint status will change to InService. At this moment, the model is prepared to accept reasoning demands through the endpoint. You can keep track of the deployment progress on the SageMaker console Endpoints page, which will show relevant 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 using the SageMaker Python SDK

    To start with DeepSeek-R1 utilizing the SageMaker Python SDK, wiki.whenparked.com you will require to install the SageMaker Python SDK and make certain you have the necessary AWS consents and environment setup. The following is a detailed code example that shows how to deploy and utilize DeepSeek-R1 for inference programmatically. The code for deploying the design is supplied in the Github here. You can clone the notebook and garagesale.es 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 produce a guardrail utilizing the Amazon Bedrock console or the API, and implement it as displayed in the following code:

    Clean up

    To avoid undesirable charges, complete the actions in this section to tidy up your resources.

    Delete the Amazon Bedrock Marketplace release

    If you deployed the model using Amazon Bedrock Marketplace, total the following steps:

    1. On the Amazon Bedrock console, under Foundation models in the navigation pane, select Marketplace implementations.
  19. In the Managed implementations section, locate the endpoint you desire to delete.
  20. Select the endpoint, and on the Actions menu, choose Delete.
  21. Verify the endpoint details to make certain you’re erasing the appropriate implementation: 1. Endpoint name.
  22. Model name.
  23. Endpoint status

    Delete the SageMaker JumpStart predictor

    The SageMaker JumpStart model you deployed 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 Resources.

    Conclusion

    In this post, we explored how you can access and release the DeepSeek-R1 design utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get going. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, 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 options utilizing AWS services and sped up calculate. Currently, he is focused on establishing strategies for fine-tuning and optimizing the inference efficiency of big language models. In his leisure time, Vivek delights in treking, enjoying motion pictures, and trying different 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 dealing with 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 intelligence and generative AI hub. She is passionate about building solutions that help customers accelerate their AI journey and unlock organization worth.