Skip to content

Modules

Amazon

Set up Amazon tasks to generate accounts on Amazon.

gen

Account generation is the only task mode on Amazon.

Set up a task#

ItemRequiredNotes
An OTP inboxYesAmazon emails a verification code during signup. A task without an inbox does not start.
Profile groupsRecommendedProfiles supply the addresses. You get one task per eligible profile, using that profile's email. If you pick none, AETHER does not refuse. It creates the tasks on random bridlecommunity.com addresses instead.
A proxy listRecommended (required on CA)The picker shows every saved list and starts on Localhost — this PC's IP, no proxy. Outside CA, Localhost runs Amazon from your own IP, and the task log says so. An Amazon CA task needs a proxy list. On Localhost it stops at once and makes no account.

The inbox can be IMAP or AYCD. Attach it under Settings, then set it on the task. A task with no inbox is refused at start, before it uses a proxy or an address. Its status becomes NO OTP INBOX ATTACHED. See OTP inboxes (IMAP).

Choose a region#

You pick the region when you create the task group. The Amazon tile has a US / CA / MX / JP switch. Tasks take the region of their group.

  • Only US and CA are saved on the group. An MX or JP group is saved with no region, so its tasks run on the US storefront.
  • A task with no region runs on US. Its log says no region on this task or its group — defaulting to US.
  • You cannot change a group's region later. Renaming is the only group edit. For another region, create a new task group.
  • Amazon CA runs on a different engine from US. That engine does not report finished accounts back to AETHER. A CA task never ends on ACCOUNT GENNED and files nothing in an account group.
  • Finished accounts go to a group named after the task group, or to Amazon US Genned. The account group is tagged with the region the accounts were made on.

Choose your emails#

Email quality matters more on Amazon than on any other module. Use real mailbox providers, the kind of inbox a person would own.

Amazon's refusal applies to the whole email family, such as a domain. It does not stop at one address. Every attempt counts toward it, whether the attempt succeeds or not.

AETHER does not stop you from using any email. It runs on whatever you pick. Read OTP inboxes (IMAP) before your first batch.

Phone step#

Some sessions reach a mobile-number page. The task row shows AMAZON DEVICE CHECK while that happens.

An Amazon task picks a saved SMS provider on its own. The task form has no SMS setting. A task uses your first saved NoServer provider, or else your first other SMS provider. On NoServer it rents from the AmazonVOIP pool by default.

With no provider saved, the task still starts. If Amazon then asks for a mobile number, the task cannot finish. Amazon CA tasks never rent a number.

Number rentals are charged per number, so a large group can quietly run up a bill. See SMS providers.

Concurrency#

Amazon runs at most five tasks at once, the same cap as most modules. Below that, the limit comes from your machine's free memory. It is not a number you set.

The rest of the group queues and starts as slots free up. A 200-task Amazon group is normal to create. It will not run 200 at once.

AETHER counts the memory your machine has free or can reclaim, and keeps 0.4 GB spare. It then allows one Amazon task per 0.5 GB. On a machine short of memory, that can be a single task.

Starting more does not make accounts arrive faster. They queue instead. More memory raises the limit only up to five.

Statuses#

StatusMeaning
PREPARING ENGINEA one-time setup download on the first Amazon task a machine runs. Amazon CA tasks do not show it.
SOLVING PROOF OF WORKAmazon set a proof-of-work puzzle, and the signup page is solving it. This is often the longest step.
AMAZON DEVICE CHECKA check beyond the email code, usually the mobile-number page.
PAGE UNREADABLE — RETRYINGAETHER lost its read of the signup page. The browser may have crashed, left the page or run out of memory. The run goes on, and its end sets the final status.
ACCOUNT ALREADY EXISTSThat address already has an Amazon account. This shows during the run. The row then ends on ALREADY GENNED, and the address cannot make a new account.
AMAZON REFUSED SIGNUPAmazon declined to create the account. The task is not retried. The row ends on GEN FAILED, and the task log keeps this status. If a whole batch hits it, check the email domain first.
NO OTP INBOX ATTACHEDThe task has no inbox, so it was refused at start. Nothing was spent. Set an inbox on the task.

For every status and which ones are terminal, see Task statuses.