Skip to content

ECZ-ID · Reciprocal Trust Infrastructure for the Machine Economy

SDK PASSPORT · AWS GETTING STARTED · 02/04Public customer resource

ECZ-ID SDK Passport AWS Marketplace Getting Started and Technical Guide

From a $0 AWS Marketplace subscription to a working SDK Passport, Dashboard control and Resolver proof.

Download PDF(PDF, 182 KB)

Release 2026.10 · 16 October 2026

About this document

Primary reader
AWS subscriber, cloud administrator, developer-platform administrator, developer.
Secondary reader
Security architect, platform engineer, procurement and support teams.
When to read this
You have found or subscribed to the SDK Passport listing and want to activate it correctly.
Release
2026.10 · 16 October 2026
What you will know after reading
You can move from Subscribe to Set up your account, TrustOps activation, Passport issue or reuse, Dashboard and Resolver verification.
What this document does not establish
AWS acquisition does not become the ECZ-ID authority root; the registration token is not a customer credential to retain or share.

NextAfter activation, read the Technical Reference for integration and proof semantics.

JOURNEY OVERVIEW

From AWS Marketplace to canonical SDK identity

The acquisition path is deliberately separate from the canonical identity/proof system.

AWS MARKETPLACE ACQUISITION

Activate an SDK Passport through AWS Marketplace

Provider acquisition is separated from canonical ECZ-ID identity, control and proof.

  • AWS Marketplace

    provider acquisition layer

  • ECZ-ID canonical system

    acquisition → activation → control → proof

  • Dashboard

    authenticated control

  • Resolver

    public read-only proof

  1. Step 1: Subscribe at $0

    SDK Passport permanently free

  2. Step 2: Set up your account

    continue to ECZ-ID

  3. Step 3: Registration token

    sensitive handoff never share

  4. Step 4: AWS-native adapter

    ResolveCustomer AWS customer

  5. Step 5: TrustOps

    acquisition + activation

  6. Step 6: Account + Parent

    reuse where appropriate

  7. Step 7: ProductCode mapping

    maps to SDK family

  8. Step 8: Issue / reuse SDK Passport

    canonical identity

AWS, repository and registry identifiers remain bindings/context; they do not become the ECZ-ID authority root.

ARCHITECTURE LAW AWS Marketplace is the provider acquisition context. TrustOps activates; Core remains canonical identity truth; Dashboard controls; Resolver proves.

  • CUSTOMER OUTCOME

    A working SDK Passport linked to the relevant account/Parent and available for public Resolver verification.

  • NOT THE OUTCOME

    A new AWS identity authority or a duplicate SDK identity for every subscription.

1. FIND AND SUBSCRIBE

The Passport is permanently free

Open the ECZ-ID SDK Passport listing and choose Subscribe at $0. This is not a time-limited Free Trial.

  • WHAT SUBSCRIBE DOES

    Creates the AWS Marketplace acquisition/subscription relationship for the free SDK Passport listing.

  • WHAT IT DOES NOT DO

    It does not by itself issue the Passport or turn AWS account identity into the canonical SDK identity.

PRICING There is no ECZ-ID software charge for this SDK Passport. It is permanently free.

  • USE INTENDED AWS ACCOUNT

    Subscribe from the AWS account intended for this acquisition context.

  • NO FREE TRIAL

    The product is already free.

  • NO PRIVATE OFFER REQUIRED

    This free Passport does not require a private offer.

  • CONTINUE

    Choose Set up your account after subscription.

2. SET UP YOUR ACCOUNT

AWS hands the acquisition to ECZ-ID

Choose Set up your account. AWS redirects the Marketplace registration token to the ECZ-ID fulfillment endpoint.

  • REGISTRATION TOKEN

    A sensitive, short-lived acquisition handoff used by the AWS Marketplace integration.

  • CUSTOMER SECRET?

    No. Do not store, share, paste into tickets, screenshots or documentation.

FULFILLMENT

https://trustops.ecocitizenz.com/aws/marketplace/fulfill
  • BROWSER REDIRECT

    The user is redirected into the supported ECZ-ID acquisition path.

  • DO NOT COPY TOKEN

    Let the integration process the registration token.

  • EXISTING CUSTOMER

    Use the supported sign-in/reuse path when you already have an account.

  • FAILURE

    Record the visible error and time - never the token.

3. RESOLVECUSTOMER AND TRUSTOPS

Turn provider acquisition into supported ECZ-ID activation

The AWS-native adapter resolves the Marketplace customer; TrustOps orchestrates account/Parent reuse or creation and Passport activation.

  • AWS-NATIVE ADAPTER

    Uses the appropriate Marketplace integration to resolve the AWS customer/acquisition context.

  • TRUSTOPS

    Owns acquisition, entitlement/activation and lifecycle handoff - not canonical identity truth.

CANONICAL BOUNDARY AWS identifiers can become bindings/context. The ECZ-ID Core remains the canonical source for identity, authority, state, custody and evidence truth.

  • ON SUCCESS

    Continue into supported account/Parent reuse or create and SDK Passport issue or reuse.

  • ON FAILURE

    Do not repeatedly retry by creating new accounts or package identities as a workaround.

4. ACCOUNT AND PARENT REUSE

Avoid duplicate identity

If the buyer already has the relevant EcoCitizenz account or Parent relationship, the intended architecture reuses it rather than creating a duplicate.

  • REUSE WHEN APPROPRIATE

    Existing supported account/Parent context should be preferred where it represents the same customer/organisation.

  • CREATE WHEN REQUIRED

    A new supported account/Parent may be created only when the canonical acquisition flow genuinely requires one.

DUPLICATE PREVENTION A new AWS subscription is not automatically a reason for another account, Parent or SDK Passport.

  • SAME ORGANISATION

    Reuse supported organisation/Parent context.

  • SAME SDK OBJECT

    Issue or reuse the canonical SDK Passport according to supported mapping.

  • DIFFERENT OBJECT

    Use a distinct Passport only when the package/release-family boundary genuinely differs.

  • RECOVERY PROBLEM

    Recover access first; do not mint replacements to bypass sign-in issues.

5. PRODUCTCODE MAPPING AND PASSPORT ISSUE OR REUSE

Map the acquisition to the SDK family

The AWS ProductCode identifies the intended Passport family for the shared fulfillment factory.

  • FAMILY MAPPING

    ProductCode → SDK Passport family.

  • IDENTITY RESULT

    Issue a new SDK Passport where the object legitimately needs one, or reuse the canonical Passport where the intended package identity already exists.

TARGET OUTCOME One canonical SDK identity for the intended package/release family - not a new Passport for every AWS subscription click.

  • OBJECT

    SDK / software package / release family.

  • PARENT

    Relevant organisation/Parent where applicable.

  • DASHBOARD

    Authenticated customer control after activation.

  • RESOLVER

    Public, independent proof re-check after issuance/reuse.

6. DASHBOARD HANDOFF

Operate the estate in the authenticated control plane

After acquisition and activation, the customer is handed into the EcoCitizenz Dashboard for permitted estate actions.

  • DASHBOARD IS

    Authenticated customer control: view/manage permitted Passport, binding, evidence and lifecycle actions.

  • DASHBOARD IS NOT

    The public Resolver and not the canonical Core itself.

FIRST CHECK Confirm the Dashboard shows the intended SDK Passport under the correct organisation/Parent before changing bindings or evidence.

  • CHECK IDENTITY

    Confirm the SDK ECZ-ID / family.

  • CHECK RELATIONSHIP

    Confirm organisation/Parent context.

  • CHECK CURRENT STATE

    Confirm published lifecycle/release context where supported.

  • CONTINUE

    Open Resolver and independently re-check the same ECZ-ID.

7. FIRST RESOLVER VERIFICATION

Prove the acquisition produced the intended public identity

After activation, independently re-check the SDK Passport through Resolver.

RESOLVER RE-CHECK

Turn a presented SDK ECZ-ID into a bounded decision input

Resolve the current public record, inspect only what is present, and fail safely when required proof is missing.

  • Consumer

    receives or discovers an SDK ECZ-ID

  • then

    ECZ-ID Resolver

    public · read-only · re-checkable GET /api/p/{ecz_id}.json

  • Identity + family

    Is this the SDK/package expected?

  • Responsibility

    Who claims publication/responsibility?

  • Bindings

    Repository / registry / docs refs

  • State

    Lifecycle / release-family context

  • Evidence

    What source, scope and freshness?

  • Boundary

    What is actually supported for this decision?

  • If required proof is present and fresh → evaluate local package policy / proceed

  • If absent, stale or mismatched → challenge, deny, pin or re-resolve

MACHINE ROUTE

GET https://api.ecocitizenz.com/api/p/{ecz_id}.json
  • VERIFY

    Family/object · organisation/Parent · state · repository/registry/release bindings · evidence where present.

  • DO NOT INFER

    Code safety, signature validity, vulnerability-free status, licence compliance or execution permission unless separately established.

TROUBLESHOOTING AND SECRET HANDLING

Diagnose the failed stage; never leak credentials

Treat subscription, account, issuance, Dashboard and Resolver failures as distinct layers.

  • SUBSCRIBE UNAVAILABLE

    Confirm you can see the Limited/Public listing and are using the intended AWS account.

  • SET UP ACCOUNT FAILS

    Record visible error/time; never expose the registration token.

  • RESOLVECUSTOMER FAILS

    Contact support with AWS context and failed stage.

  • WRONG/DUPLICATE IDENTITY

    Stop; recover or reuse the canonical account/Parent/Passport where supported.

  • RESOLVER MISSING

    Confirm acquisition/issuance completed and the ECZ-ID is correct.

  • PACKAGE RUNTIME ISSUE

    Diagnose registry access, signature, vulnerability, licence or dependency/runtime problems separately.

SUPPORT support@ecocitizenz.com · Never send passwords, package-registry tokens, private signing keys, AWS registration tokens or other secrets.

60-SECOND COMPLETION CHECK

You are done when these conditions are true

Use this as the final acquisition acceptance check.

  • SUBSCRIPTION

    AWS Marketplace subscription is active at $0.

  • ACCOUNT

    Supported EcoCitizenz account/Parent was reused or created as appropriate.

  • FAMILY MAPPING

    ProductCode mapped to SDK Passport.

  • PASSPORT

    The intended SDK Passport was issued or reused without duplicate identity.

  • DASHBOARD

    The Passport is visible under the correct customer context.

  • RESOLVER

    The same ECZ-ID resolves publicly and can be re-checked.

NEXT Read the SDK Passport Technical Reference before building automated verification or integration logic.

Download and support

This page is the HTML edition of ECZ-ID SDK Passport - AWS Marketplace Getting Started and Technical Guide, release 2026.10. The PDF is the designed offline copy.

Permanent route: https://developers.ecocitizenz.com/passports/sdk/aws-getting-started/