Skip to content
Alma Mobility MarketplacesAlma Mobility MarketplacesAlma Mobility Marketplaces developer docs

Start here

Do this first: AWS access

Section titled “Do this first: AWS access”

Request membership in an IAM AWS-SSO Marketplaces-Mobility-* group on day one, before anything else. Group membership sync takes 1–3 hours. Ask in the morning and you can use it that afternoon; ask at 16:00 and you cannot.

Which group to ask for, and who to ask, is in Confluence space MONE. The reasoning behind the four groups is in Why AWS access is split into four groups.

While you wait, the rest of the setup does not need AWS. Two pages are worth reading in that gap: how the services fit together, because we run two generations of platform side by side and nothing else makes sense until you know that, and the glossary, because half the names you are about to hear are Finnish or codenames.

Then, in rough order

Section titled “Then, in rough order”
  1. AWS access requested — see above. Nothing here blocks on it except step 4.
  2. GitHub — confirm you are in the alma-mobility-marketplaces org and can clone a private repo.
  3. Cloudflare Access — sign in to this site, then to https://scorecard.ajomark.dev, which asks for Auth0 after Access. Same Alma identity at the Access step. If one internal site lets you in and another does not, that is an Access policy question — say so rather than retrying, per Hostnames.
  4. AWS CLI — once the group has synced, follow Configure AWS SSO for the CLI and verify with aws sts get-caller-identity.
  5. Your first repo — find it on the repository map, then clone it and follow its own README.md. Per-repo setup lives in the repo, not here. Check the default branch on the map first: it is main in fewer than half our repositories.
  6. The shared Claude skills — two commands, and your Jira tickets, specs and ADRs come out in our formats. See Install the AJOMARK Claude skills.

Where documentation lives

Section titled “Where documentation lives”

Roughly: this site covers anything spanning repos or describing our environment. A service’s own repo covers how that service works. Confluence space MONE covers people and process. https://almamedia.cloud covers Alma-wide AWS guidance.

Where documentation lives has the full split, including why the line between this site and Confluence is write access rather than read access. Read it before you write a page; it saves an argument in review.