**End of support notice:** On October 30, 2026, AWS will end support for Amazon Pinpoint. After October 30, 2026, you will no longer be able to access the Amazon Pinpoint console or Amazon Pinpoint resources (endpoints, segments, campaigns, journeys, and analytics). For more information, see [Amazon Pinpoint end of support](https://docs.aws.amazon.com/console/pinpoint/migration-guide). **Note:** APIs related to SMS, voice, mobile push, OTP, and phone number validate are not impacted by this change and are supported by AWS End User Messaging. # Using dedicated IP addresses with Amazon Pinpoint Using dedicated IP addresses When you create a new Amazon Pinpoint account, your emails are sent from IP addresses that are shared with other Amazon Pinpoint users. For [an additional monthly charge](https://aws.amazon.com/pinpoint/pricing/#Dedicated_IP_Addresses), you can lease dedicated IP addresses that are reserved for your exclusive use. Both of these options offer unique benefits and drawbacks, which are summarized in the following table. **** | Benefit | Shared IP addresses | Dedicated IP addresses | | --- | --- | --- | | [Ready to use with no additional setup](#channels-email-dedicated-ips-simplicity) | Yes | No | | [Reputation managed by AWS](#channels-email-dedicated-ips-managed-reputation) | Yes | No | | [Good for customers with continuous, predictable sending patterns](#channels-email-dedicated-ips-sending-patterns) | Yes | Yes | | [Good for customers with less predictable sending patterns](#channels-email-dedicated-ips-sending-patterns) | Yes | No | | [Good for high-volume senders](#channels-email-dedicated-ips-sending-volumes) | Yes | Yes | | [Good for low-volume senders](#channels-email-dedicated-ips-sending-volumes) | Yes | No | | [Additional monthly costs](#channels-email-dedicated-ips-costs) | No | Yes | | [Complete control over sender reputation](#channels-email-dedicated-ips-reputation-control) | No | Yes | | [Isolates reputation by email type, recipient, or other factors](#channels-email-dedicated-ips-isolate-reputation) | No | Yes | | [Provides known IP addresses that never change](#channels-email-dedicated-ips-known-addresses) | No | Yes | **Important** If you don't plan to send large volumes of email on a regular and predictable basis, we recommend that you use shared IP addresses. If you use dedicated IP addresses in use cases that involve sending low volumes of email, or if your sending patterns are highly irregular, you might experience deliverability issues. ## Ease of setup If you choose to use shared IP addresses, then you don't need to perform any additional configuration. Your Amazon Pinpoint account is ready to send emails as soon as you verify an email address and move out of the sandbox. If you choose to lease dedicated IP addresses, you have to determine how many dedicated IP addresses you need, submit a request, and optionally [create dedicated IP pools](channels-email-dedicated-ips-pools.md). ## Reputation managed by AWS IP address reputations are based largely on historical sending patterns and volume. An IP address that sends consistent volumes of email over a long period of time usually has a good reputation. Shared IP addresses are used by several Amazon Pinpoint customers. Together, these customers send a large volume of email. AWS carefully manages this outbound traffic in order to maximize the reputations of the shared IP addresses. If you use dedicated IP addresses, it's your responsibility to maintain your sender reputation by sending consistent and predictable volumes of email. ## Predictability of sending patterns An IP address with a consistent history of sending email has a better reputation than one that suddenly starts sending out large volumes of email with no prior sending history. If your email sending patterns are irregular (they don't follow a predictable pattern), then shared IP addresses are a better fit for your needs. When you use shared IP addresses, you can increase or decrease your email-sending patterns as the situation demands. If you use dedicated IP addresses, you have to warm up those addresses by sending an amount of email that gradually increases every day. The process of warming up new IP addresses is described in [Warming up dedicated IP addresses](channels-email-dedicated-ips-warming.md). After your dedicated IP addresses are warmed up, you must then maintain a consistent sending pattern. ## Volume of outbound email Dedicated IP addresses are more appropriately suited for customers who send large volumes of email. Most internet service providers (ISPs) only track the reputation of a given IP address if they receive a significant volume of mail from that address. For each ISP with which you want to cultivate a reputation, you should send several hundred emails within a 24-hour period at least once per month. In some cases, you might be able to use dedicated IP addresses if you don't send large volumes of email. For example, dedicated IP addresses might work well if you send to a small, well-defined group of recipients whose mail servers accept or reject email using a list of specific IP addresses, rather than IP address reputation. ## Additional costs The use of shared IP addresses is included in the standard Amazon Pinpoint pricing. Leasing dedicated IP addresses incurs an extra monthly cost beyond the standard costs that are associated with sending email using Amazon Pinpoint. Each dedicated IP address incurs a separate monthly charge. For pricing information, see the [Amazon Pinpoint pricing page](https://aws.amazon.com/pinpoint/pricing/). ## Control over sender reputation When you use dedicated IP addresses, your Amazon Pinpoint account is the only one that is able to send email from those addresses. For this reason, the sender reputation of the dedicated IP addresses that you lease is determined by your email-sending practices. ## Ability to isolate sender reputation By using dedicated IP addresses, you can isolate your sender reputation for different components of your email program. If you lease more than one dedicated IP address for use with Amazon Pinpoint, you can create *dedicated IP pools*—groups of dedicated IP addresses that can be used for sending specific types of email. For example, you can create one pool of dedicated IP addresses for sending marketing email, and another for sending transactional email. To learn more, see [Creating dedicated IP pools](channels-email-dedicated-ips-pools.md). ## Known, unchanging IP addresses When you use dedicated IP addresses, you can find the values of the addresses that send your mail in the **Dedicated IPs** page of the Amazon Pinpoint console. Dedicated IP addresses don't change. With shared IP addresses, you don't know the IP addresses that Amazon Pinpoint uses to send your mail, and they can change at any time. # Requesting and relinquishing dedicated IP addresses Requesting and relinquishing dedicated IPs This section describes how to request and relinquish dedicated IP addresses by submitting a request in the [AWS Support Center](https://console.aws.amazon.com/support/home#/). We charge your account an additional monthly fee for each dedicated IP address that you lease for use with Amazon Pinpoint. For more information about the costs associated with dedicated IP addresses, see [Amazon Pinpoint pricing](https://aws.amazon.com/pinpoint/pricing/#Optional_Charges). ## Best practices for working with dedicated IP addresses Although there's no minimum commitment, we recommend that you lease more than one dedicated IP address in each AWS Region where you use Amazon Pinpoint. Each AWS Region consists of multiple physical locations, called *Availability Zones*. When you lease more than one dedicated IP address, we distribute those addresses as evenly as possible across the Availability Zones in the AWS Region that you specified in your request. Distributing your dedicated IP addresses across Availability Zones in this way increases the availability and redundancy of your dedicated IP addresses. For a list of all the Regions where Amazon Pinpoint is currently available, see [Amazon Pinpoint endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/pinpoint.html) in the *Amazon Web Services General Reference*. To learn more about the number of Availability Zones that are available in each Region, see [AWS global infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/). ## Requesting dedicated IP addresses The following steps show how to request dedicated IP addresses by creating a case in the AWS Support Center. You can use this process to request as many dedicated IP addresses as you need. **To request dedicated IP addresses** 1. Sign in to the AWS Management Console at [https://console.aws.amazon.com/](https://console.aws.amazon.com/). 1. On the **Support** menu, choose **Support Center**. 1. On the **My support cases** tab, choose **Create case**. 1. Under **Create case**, choose **Service quota increase**. 1. Under **Case classification**, complete the following sections: + For **Quota type**, choose **Pinpoint Email**. + For **Mail Type**, choose the type of email that you plan to send using your dedicated IP addresses. If multiple values apply, choose the option that applies to the majority of the email that you plan to send. + For **Website URL**, enter the URL of your website. Providing this information helps us better understand the type of content that you plan to send. + For **Describe in detail how you will only send to recipients who have specifically requested your mail**, explain how you will make sure that you use your dedicated IP addresses to send email only to recipients who want to receive email from you. + For **Describe in detail the process that you will follow when you receive bounce and complaint notifications**, explain how you will process bounces and complaints about the email that you plan to send using your dedicated IP addresses. + For **Will you comply with AWS Service Terms and AUP**, choose the option that applies to your use case. 1. Under **Requests**, complete the following sections: + For **Region**, choose the AWS Region that your request applies to. + For **Quota**, choose **Desired Maximum Email Send Rate**. + For **New quota value**, enter the maximum number of messages that you need to be able to send per second. We use this value to calculate the number of dedicated IP addresses that you need to implement for your use case. For this reason, the estimate that you provide should be as accurate as possible. **Note** A single dedicated IP address can be used only in the AWS Region that you choose in this step. If you want to request dedicated IP addresses for use in another AWS Region, choose **Add another request**. Then complete the **Region**, **Quota**, and **New quota value** fields for the additional Region. Repeat this process for each Region that you want to use dedicated IP addresses in. 1. Under **Case description**, for **Use case description**, state that you want to request dedicated IP addresses. If you want to request a specific number of dedicated IP addresses, mention that as well. If you don't specify a number of dedicated IP addresses, we provide the number of dedicated IP addresses that are necessary to meet the sending rate requirement that you specified in the previous step. Next, describe how you plan to use dedicated IP addresses to send email using Amazon Pinpoint. Include information about why you want to use dedicated IP addresses instead of shared IP addresses. This information helps us better understand your use case. 1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**. 1. When you finish, choose **Submit**. After you submit the form, we evaluate your request. If we grant your request, we reply to your case in Support Center to confirm that your new dedicated IP addresses are associated with your account. ## Relinquishing dedicated IP addresses If you no longer need dedicated IP addresses that are associated with your account, you can relinquish them by completing the following steps. **Important** The process of relinquishing a dedicated IP address can't be reversed. If you relinquish a dedicated IP address in the middle of a month, we prorate the monthly dedicated IP usage fee, based on the number of days that have elapsed in the current month. **To relinquish dedicated IP addresses** 1. Sign in to the AWS Management Console at [https://console.aws.amazon.com/](https://console.aws.amazon.com/). 1. On the **Support** menu, choose **Support Center**. 1. On the **My support cases** tab, choose **Create case**. 1. Under **Create case**, choose **Service quota increase**. 1. Under **Case classification**, complete the following sections: + For **Quota type**, choose **Pinpoint Email**. + For **Mail Type**, choose any value. + For **Will you comply with the AWS Service Terms and AUP**, choose the option that applies to your use case. 1. Under **Requests**, complete the following sections: + For **Region**, choose the AWS Region that your request applies to. **Note** Dedicated IP addresses are unique to each AWS Region, so it's important to select the Region that the dedicated IP address is associated with. + For **Quota**, choose **Desired Maximum Email Send Rate**. + For **New quota value**, enter any number. The number that you enter here isn't important—you specify the number of dedicated IP addresses that you want to relinquish in the next step. **Note** A single dedicated IP address can be used in only a single AWS Region. If you want to relinquish dedicated IP addresses that you used in other AWS Regions, choose **Add another request**. Then complete the **Region**, **Quota**, and **New quota value** fields for the additional Region. Repeat this process for each dedicated IP address that you want to relinquish. 1. Under **Case Description**, for **Use case description**, indicate that you want to relinquish existing dedicated IP addresses. If you currently lease more than one dedicated IP address, include the number of dedicated IP addresses that you want to relinquish. 1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**. 1. When you finish, choose **Submit**. After we receive your request, we send you a message that asks you to confirm that you want to relinquish your dedicated IP addresses. After you confirm that you want to relinquish the IP addresses, we remove them from your account. # Viewing a list of dedicated IP addresses that are associated with your account Viewing your dedicated IPs You can view a list of dedicated IP addresses that are associated with your Amazon Pinpoint account in the current AWS Region. These IP addresses are available for use with both Amazon Pinpoint and Amazon Simple Email Service (Amazon SES). You can also use the Amazon Pinpoint console to quickly determine if any of your dedicated IP addresses have been listed on Domain Name System-based Blackhole Lists (*DNSBLs*). DNSBLs are also called *Realtime Blackhole Lists* (*RBLs*), *deny lists*, *blocklists*, or *blacklists*). DNSBLs are lists of IP addresses that are suspected of sending spam, malicious content, or other unsolicited messages. Different DNSBLs have different impacts on email deliverability. The lists offered by Spamhaus have the most serious impact on email delivery. **To view a list of dedicated IPs in your account** 1. Open the Amazon Pinpoint console at [https://console.aws.amazon.com/pinpoint/](https://console.aws.amazon.com/pinpoint/). 1. In the navigation pane, under **Email**, choose **Dedicated IPs**. The list of IP addresses also includes the following information: **Listing date** If the IP address is currently listed on a DNSBL, this field shows the date when it was most recently added. **Reputation** A description of the health of the IP address. **Blacklist name** If the IP address is currently listed on a DNSBL, this field shows the name of the list that it's listed on. **Blacklist reason** If the IP address is currently listed on a DNSBL, this field displays the reason that the address was added to the list. This text is provided by the list providers themselves. Some providers offer detailed explanations, while others offer generic information. # Warming up dedicated IP addresses Warming up dedicated IPs When determining whether to accept or reject a message, email service providers consider the reputation of the IP address that sent it. One of the factors that contributes to the reputation of an IP address is whether the address has a history of sending high-quality email. Email providers are less likely to accept mail from new IP addresses that have little or no history. Email sent from IP addresses with little or no history might end up in recipients' junk mail folders, or might be blocked altogether. When you start sending email from a new IP address, you should gradually increase the amount of email you send from that address before using it to its full capacity. This process is called *warming up* the IP address. The amount of time that's required to warm up an IP address varies between email providers. For some email providers, you can establish a positive reputation in around two weeks, while for others it might take up to six weeks. When warming up a new IP address, you should send emails to your most active users to ensure that your complaint rate remains low. You should also carefully examine your bounce messages and send less email if you receive a high number of blocking or throttling notifications. ## Automatically warm up dedicated IP addresses When you request dedicated IP addresses, Amazon Pinpoint automatically warms them up to improve the delivery of emails you send. The automatic IP address warm-up feature is enabled by default. The steps that happen during the automatic warm-up process depend on whether you already have dedicated IP addresses: + When you request dedicated IP addresses for the first time, Amazon Pinpoint distributes your email sending between your dedicated IP addresses and a set of addresses that are shared with other Amazon Pinpoint customers. Amazon Pinpoint gradually increases the number of messages sent from your dedicated IP addresses over time. + If you already have dedicated IP addresses, Amazon Pinpoint distributes your email sending between your existing dedicated IPs (which are already warmed up) and your new dedicated IPs (which aren't warmed up). Amazon Pinpoint gradually increases the number of messages that are sent from your new dedicated IP addresses over time. After you warm up a dedicated IP address, you should send around 1,000 emails every day to each email provider that you want to maintain a positive reputation with. You should perform this task on each dedicated IP address that you use with Amazon Pinpoint. You should avoid sending large volumes of email immediately after the warm-up process is complete. Instead, slowly increase the number of emails you send until you reach your target volume. If an email provider sees a large, sudden increase in the number of emails being sent from an IP address, they might block or throttle the delivery of messages from that address. # Creating dedicated IP pools Creating dedicated IP pools If you purchased several dedicated IP addresses to use with Amazon Pinpoint, you can create groups of those addresses. These groups are called *dedicated IP pools*. A common scenario is to create one pool of dedicated IP addresses for sending marketing communications, and another for sending transactional emails. Your sender reputation for transactional emails is then isolated from that of your marketing emails. In this scenario, if a marketing campaign generates a large number of complaints, the delivery of your transactional emails isn't impacted. Dedicated IP pools are available for use in both Amazon Pinpoint and Amazon Simple Email Service (Amazon SES). When you create a dedicated IP pool, you have to choose a configuration set to associate it with. Currently, you can only manage configuration sets and IP pools using Amazon SES. For more information about setting up configuration sets, see [Creating configuration sets](https://docs.aws.amazon.com/ses/latest/dg/creating-configuration-sets.html) in the *Amazon Simple Email Service Developer Guide*. For more information about setting up dedicated IP pools, see [Creating dedicated IP pools]() in the *Amazon Simple Email Service Developer Guide*. In order to use configuration sets (and therefore, dedicated IP pools) with Amazon Pinpoint, you must configure the configuration set as the default configuration set for the email identities that you use with Amazon Pinpoint. For more information, see [Applying a configuration set to an email identity](channels-email-manage-configuration-sets.md#channels-email-manage-configuration-sets-applying).