Onboarding

1. Set up an AWS account

• Create an AWS account if you don't have one — a credit card is required for account creation, though costs for this integration are minimal
• Any IAM identity (user or role) within your account can be used to sign requests — no specific identity needs to be registered
• The signing identity must have the execute-api:Invoke permission. Because requests may be routed to multiple underlying regions, scope the resource to all regions using a wildcard: arn:aws:execute-api:*:*:*

If you are submitting data to the EU region, you must opt in to the eu-south-2 (Spain) region in your AWS account settings. This region is not enabled by default. There is no additional cost.

2. Provide your AWS account ID to Amazon

Share your AWS account ID with your Amazon representative (e.g. 123456789012). Amazon will register your account in the API Gateway access policy. Any request signed by any IAM identity within that account will be authorized.

No API key is required. Access is controlled at the AWS account level — any valid SigV4a-signed request from your registered account will be accepted.

3. Test in Gamma

Validate your integration against the Gamma environment before going to production. Gamma accepts the same payload format and returns the same responses as production. See Getting Started for endpoint URLs.

4. Verify asset identifiers

• Use the physical asset identifier (vehicle plate number) as assetIdentifier.id
• Coordinate with your Amazon representative to verify that the identifiers you use match Amazon's asset registry
• Use your SCAC code for both carrier and assetIdentifier.operator