Amazon

Members sign in with their Amazon account, in the system browser.

Before you start

Console	Login with Amazon
Endpoint group	Social Login
Email	Returned, but not verified — cannot match an existing account
Signs in	In the browser

Login with Amazon is not AWS

This is a consumer sign-in product on developer.amazon.com. An AWS access key or Cognito pool is a different thing entirely and will not work here.

Create the security profile

1. Open the Login with Amazon console and choose Create a New Security Profile.

2. Fill in the profile name, description and a Consent Privacy Notice URL.

   The name and description are what members read on the consent screen. The privacy URL is required.

3. Open the profile’s Web Settings and press Edit.

4. Add your site under Allowed Origins — the scheme and host, with no path.

5. Add the redirect address under Allowed Return URLs: the string from Memberside → API Keys → Social Login → Amazon, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/amazon.

6. Copy the Client ID and Client Secret from the same screen.

Why the email cannot match an existing account

Amazon returns an address without a verification claim, so Memberside refuses to attach an Amazon sign-in to an account that already exists by matching it. New members can still register; existing ones should sign in first and link Amazon from Social Connects.

What to paste into Memberside

Under Memberside → API Keys → Social Login → Amazon:

Field	Value
Client ID	The Client ID
Client secret	The Client Secret

When it does not work

Symptom	Cause	Fix
“The redirect URI is not on the allow list”	The return URL is missing from Web Settings	Add it and save
The consent screen shows no description	The security profile has none	Fill it in — members see it
An AWS key is refused	This product uses its own credentials	Create a security profile
A second account is created for an existing member	Amazon’s email is unverified, so matching is refused	Have them sign in first, then link