10DLC cross-account access - Amazon Pinpoint

10DLC cross-account access

There are two ways you can enable cross-account access for 10DLC.

  1. You can register the same tax ID and brand across multiple AWS accounts. These will be treated as separate registrations and charged separately. In addition, trust score and throughput allocation are evaluated separately by carrier and might differ across accounts.

  2. Alternatively, you can register a single AWS account, and use AWS Identity and Access Management (IAM) roles to associate other accounts with your main account. Then, delegate access permissions from the main account to the other accounts by granting them access to the 10DLC numbers in the main account. These steps are described below.

To grant access to the 10DLC numbers in your main account

  1. Sign in to the AWS Management Console and open the Amazon Pinpoint console at https://console.aws.amazon.com/pinpoint/.

  2. Under Account Settings, SMS and voice, choose the 10DLC tab.

  3. Register your company and campaign on the main account that will use the 10DLC phone number. For example, your main account might be a Production account, but you want your Development account to use a 10DLC number.

  4. Create the IAM role in your main account. This allows another account to call the SendMessages API operation. For this operation, you must specify the 10DLC number to use for the originating identity. For more information on creating roles, see Creating IAM roles in the IAM User Guide.

  5. Delegate and test access permission from your main account using IAM roles with any of your other accounts that need to use your 10DLC numbers. For example, you might delegate access permission from your Production account to your Development account. See Delegate access across AWS account using IAM roles in the IAM User Guide for more information about delegating and testing.

  6. Using the new role, send a message using a 10DLC number from the main account. See Using IAM roles in the IAM User Guide for more information on using a role.


    A sent message from the secondary account is treated as if it were sent from your main account. Quotas and billing are counted against this account and not any secondary accounts.