Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Postbox
  • Getting started
    • All guides
    • Creating an address
    • Domain ownership check
    • Setting up a DMARC policy
    • Sending an email
    • Templating an email
    • Bulk emailing
    • Creating a configuration
    • Linking a configuration to an address
    • Managing a custom suppression list
    • Managing dedicated IP addresses
    • Limiting the list of senders
    • Writing logs
    • Viewing information about sent emails
  • Access management
  • Pricing policy
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Managing dedicated IP addresses

Managing dedicated IP addresses

Written by
Yandex Cloud
Updated at October 14, 2026
View in Markdown

Note

This feature is at the Preview stage.

Dedicated IP addresses are grouped into pools. If a pool is linked to a configuration, all emails the configuration applies to are sent from the linked pool’s IP addresses.

Dedicated IP addresses are issued to a cloud upon request. To get them, contact support.

AWS CLI

If you do not have the AWS CLI yet, install and configure it.

To manage dedicated IP addresses, assign the postbox.editor role to the service account used by the AWS CLI.

  1. In the terminal, define these variables:

    ENDPOINT=https://postbox.cloud.yandex.net
    PROFILE=<profile_name>
    POOL_NAME=<pool_name>
    CONFIGSET_NAME=<configuration_name>
    IP=<dedicated_IP_address>
    
  2. View the list of dedicated IP addresses issued to your cloud:

    aws sesv2 get-dedicated-ips \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE
    

    IP addresses not distributed among custom pools are in the default pool named ses-default-dedicated-pool.

  3. Create a pool:

    aws sesv2 create-dedicated-ip-pool \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --pool-name $POOL_NAME
    

    The pool name must be unique within the cloud and may contain lowercase Latin letters, digits, underscores _, and hyphens -. The name must be 1 to 64 characters long. You cannot use names reserved by the service.

  4. Add a dedicated IP address to the pool:

    aws sesv2 put-dedicated-ip-in-pool \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --ip $IP \
       --destination-pool-name $POOL_NAME
    

    The same IP address can belong only to one pool at any given time.

  5. Link the pool to a configuration:

    aws sesv2 put-configuration-set-delivery-options \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --configuration-set-name $CONFIGSET_NAME \
       --sending-pool-name $POOL_NAME \
       --tls-policy REQUIRE
    

    Warning

    This command completely updates the configuration's delivery settings. If you run it without specifying --sending-pool-name, the pool will be unlinked from the configuration, and mail will be sent from the service’s shared IP addresses.

    If a configuration is linked to a pool with no allocated IP addresses, sending emails with that configuration will fail: the SendEmail method will return the 404 NotFoundException error. The system will not automatically fall back to the shared IP address pool.

  6. Check the pool's composition:

    aws sesv2 get-dedicated-ips \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --pool-name $POOL_NAME
    
  7. To remove an IP address from the custom pool, move it to the default pool:

    aws sesv2 put-dedicated-ip-in-pool \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --ip $IP \
       --destination-pool-name ses-default-dedicated-pool
    
  8. Delete the pool:

    aws sesv2 delete-dedicated-ip-pool \
       --endpoint-url=$ENDPOINT \
       --profile $PROFILE \
       --pool-name $POOL_NAME
    

    Note

    You cannot delete a pool linked to a configuration. First, detach the pool from all configurations to which it is linked.

    You can delete a pool even if it contains dedicated IP addresses: when you delete a pool, all IP addresses are automatically moved to the default pool named ses-default-dedicated-pool.

Useful linksUseful links

  • Dedicated IP addresses

Was the article helpful?

Previous
Managing a custom suppression list
Next
Limiting the list of senders
© 2026 Direct Cursus Technology L.L.C.