Managing dedicated IP addresses
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
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.
-
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> -
View the list of dedicated IP addresses issued to your cloud:
aws sesv2 get-dedicated-ips \ --endpoint-url=$ENDPOINT \ --profile $PROFILEIP addresses not distributed among custom pools are in the default pool named
ses-default-dedicated-pool. -
Create a pool:
aws sesv2 create-dedicated-ip-pool \ --endpoint-url=$ENDPOINT \ --profile $PROFILE \ --pool-name $POOL_NAMEThe 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. -
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_NAMEThe same IP address can belong only to one pool at any given time.
-
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 REQUIREWarning
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 NotFoundExceptionerror. The system will not automatically fall back to the shared IP address pool. -
Check the pool's composition:
aws sesv2 get-dedicated-ips \ --endpoint-url=$ENDPOINT \ --profile $PROFILE \ --pool-name $POOL_NAME -
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 -
Delete the pool:
aws sesv2 delete-dedicated-ip-pool \ --endpoint-url=$ENDPOINT \ --profile $PROFILE \ --pool-name $POOL_NAMENote
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.