Browser tool · nothing uploaded

Amazon Marketing Stream V2 setup commands

Pick a region and a dataset. Get the destination deploy, the subscription call, the one response check that stops you losing subscriptions silently, and the alarm for when delivery stalls.

Your setup

3–24 chars, lowercase letters, numbers and hyphens. One per client application.

Goes in the body, not a scope header.

These stay in your browser. The page makes no network request after it loads.

Hand the whole thing to an AI

Paste this into Claude or ChatGPT with AWS CLI access. It carries your settings above, the order of operations, and the four traps that make a V2 pipeline look finished when it isn’t.

Read it first 

        

        

          Prefer to understand it? The step-by-step guide
          explains what each command does and why the order matters.
        

      


      


      

        
Three things that bite

        
    
          
  • The response is a 207, not a 200. Per-item results live in success[] and errors[]. A client that checks only the HTTP status will treat a rejected subscription as created.
    • 
          
  • ACTIVE means the destination was reachable, not that data is flowing. Amazon validates the bucket and queue at creation and nothing after. Prove it with files in S3.
    • 
          
  • Records are restated totals, not deltas. The same key is re-sent with a higher version when it changes. Upsert on the latest version — never append, never sum.
    •