Notifications destinations seem to be region-specific, even though createDestination is a grantless operation

[jlevers]

I've created a notifications destination via createDestination. Since this is a grantless operation (no refresh token involved), I would expect the destination not to be region-specific, since there's no definite geography associated with the LWA client ID and client secret – refresh tokens for any region can be generated using LWA creds from an application in any other region.

However, when I attempt to call createSubscription with a set of credentials from a different region than the app whose LWA creds I used to call createDestination, I get a 400 error with this payload:

{
  "errors": [
    {
      "code": "InvalidInput",
      "message": "Request has missing or invalid parameters and cannot be parsed.",
      "details": "No destination with id xxxx"
    }
  ]
}

So, is this a bug, or are destinations region-specific? If it's not a bug, this should be documented somewhere, as there's nothing indicating one way or another how regions/marketplaces are managed in the context of notifications.

[MeenaAmz]

@jlevers Can you please explain the issue in detail? Are you saying that you created the destination using one app and then attempting to create a subscription with a different app in a different marketplace or are you referring to different AWS regions or both?

Thanks
Meena

[jlevers]

Sure, here's the step by step:

• Created a destination using NA credentials
• Subscribed to a notification type using that destination, using NA credentials
• Attempted to subscribe to a different notification type using the same destination, with EU credentials

This is all within a single app. The destination was created using the credentials associated with the app, and then the subscription requests were made with a) those same credentials and b) a set of credentials generated via OAuth on the same app. In either case, the credentials were able to successfully create a subscription if the region of the subscribing credentials matched the region of the credentials that created the destination, but could not create a subscription if the region of the credentials was different than the region of the credentials that created the destination.

Let me know if I can make anything clearer, I know that's kinda word salad.