datapace-collector 0.2.0__tar.gz

datapace_collector-0.2.0/.gitignore

@@ -0,0 +1,192 @@
+# Python (the backend keeps its own .gitignore at src/.gitignore; these cover
+# stray caches created outside it, e.g. by an editor run from the repo root)
+__pycache__/
+*.py[cod]
+.venv/
+.ruff_cache/
+.pytest_cache/
+
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional stylelint cache
+.stylelintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+!src/tests/fixtures/assessment/bundles/*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variable files
+.env
+.env.*
+!.env.example
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Storybook build output
+storybook-static
+
+# Turborepo
+.turbo
+
+# Vercel
+.vercel
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+.output
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# vuepress v2.x temp and cache directory
+.temp
+.cache
+
+# Sveltekit cache directory
+.svelte-kit/
+
+# vitepress build output
+**/.vitepress/dist
+
+# vitepress cache directory
+**/.vitepress/cache
+
+# Docusaurus cache and generated files
+.docusaurus
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# Firebase cache directory
+.firebase/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v3
+.pnp.*
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions
+
+# Playwright (scripts/e2e-stack.sh)
+playwright-report/
+test-results/
+blob-report/
+.playwright/
+
+# Validation-gate runs (scripts/gates.py) — logs and collected artifacts
+.gates/
+
+# Vite files
+vite.config.js.timestamp-*
+vite.config.ts.timestamp-*
+.vite/
+
+# MacOS
+.DS_Store
+
+# Claude Code worktrees (local-only feature branches)
+.claude/worktrees/
+
+# graphify runs out of its own venv (see the `graph` target). Kept at the repo
+# root, outside src/, so ruff and pyright never walk it.
+.venv-graph/
+
+# graphify: the graph and the agent-crawlable wiki are committed so a fresh
+# clone starts with both; report, html and caches are regenerated on demand and
+# would churn every run.
+graphify-out/*
+!graphify-out/graph.json
+!graphify-out/wiki/
+
+# `graphify install --project` regenerates these on every upgrade. The skill is
+# picked up from .claude/skills/ without them, and the settings.json it writes
+# hardcodes an absolute path to the installing machine's binary.
+.claude/CLAUDE.md
+.claude/settings.json
+.import_linter_cache/

datapace_collector-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

datapace_collector-0.2.0/PKG-INFO

@@ -0,0 +1,98 @@
+Metadata-Version: 2.5
+Name: datapace-collector
+Version: 0.2.0
+Summary: Collect read-only RDS evidence from AWS accounts you choose into an allowlisted Datapace evidence bundle.
+Project-URL: Homepage, https://datapace.ai
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Environment :: Console
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Requires-Dist: boto3
+Description-Content-Type: text/markdown
+
+# datapace-collector
+
+The customer-run half of the Cloud Self-Assessment (DAT-891, ADR-0023). A prospect runs
+it against AWS accounts they pick. It writes one evidence bundle (`.tgz`) that matches
+the frozen v1 schema at `src/datapace/domain/assessment/bundle_schema_v1.json`, plus a
+local `aliases.json` that maps each alias in the bundle back to the real resource.
+
+Its own distribution, Python ≥ 3.10, one runtime dependency (boto3). It imports nothing
+from `datapace`.
+
+```
+datapace-collector --profile 111111111111=prod --profile 222222222222=stage \
+  [--billing-profile payer] --regions us-east-1,eu-west-1 --out ./evidence
+```
+
+- **Only the named profiles are opened.** Without `--profile` it exits 2; it never
+  lists local profiles. Each profile must really be the account it is mapped to
+  (`sts:GetCallerIdentity`), or it exits 3.
+- **Preflight** probes every permission per account and region and prints each denial
+  with the IAM action and the input it costs. `rds:DescribeDBInstances` denied
+  everywhere → exit 3, nothing written.
+- **Collects** inventory, 90 days of daily and monthly RDS cost, RI/Savings Plans
+  coverage, reserved instances, manual snapshots and 30 days of hourly metrics (eight
+  `GetMetricData` workers, 60 s timeout, 3 retries).
+- **`--billing-profile`** reads Cost Explorer from a payer; lines for accounts not
+  selected are dropped.
+- **Exit codes:** 0 bundle written (complete or partial), 1 internal error, 2 usage,
+  3 preflight failed, 130 interrupted (partial bundle kept).
+
+## Running it
+
+Python ≥ 3.10. macOS's system `python3` is 3.9: the `.pyz` stops with a message
+naming the minimum version and exits 2; install a newer Python (python.org, Homebrew
+or uv) and run it with that. The same version ships three ways, built by `build.sh`:
+
+- **The `.pyz`**, for machines where nothing can be installed:
+  `python3 datapace-collector-<v>.pyz --profile … --out …`. boto3 is inside the file,
+  so it needs no network install. Its dependencies are exactly the hash-checked set
+  in `uv.lock`, never a fresh resolution. Bundles record `distribution: pyz`.
+- **The downloaded wheel**: `pip install ./datapace_collector-<v>-py3-none-any.whl`,
+  then `datapace-collector …`.
+- **PyPI**: `uvx datapace-collector@0.2.0 …` <!-- x-release-please-version -->
+  or `pip install datapace-collector==0.2.0`. <!-- x-release-please-version -->
+
+PyPI and the downloaded wheel are the same file, so both record `distribution: wheel`
+and the bundle cannot tell them apart.
+
+On first run the `.pyz` unpacks itself into
+`~/.shiv/datapace-collector-<v>.pyz_<build-id>/`, or under `$SHIV_ROOT` if set, and
+reuses that copy afterwards. It unpacks before the version check, so a run refused
+on Python 3.9 leaves the copy too. Remove it with `rm -rf ~/.shiv/datapace-collector-*`.
+
+## What keeps the bundle safe
+
+- `operations.py`'s `READ_ONLY_OPERATIONS` is every AWS call the collector may make.
+  `tests/test_safety.py` records each botocore call and fails on anything outside it.
+- Every record is built field by field from the schema's closed properties: an
+  allowlist, not a redaction. Raw ids become `HMAC(salt, kind|account|region|id)`
+  aliases. `tests/test_leaks.py` seeds account ids, ARNs, endpoints, tags,
+  `MasterUsername` and ARN-bearing AccessDenied messages, and asserts none reaches a
+  bundle byte.
+- A denied input is `denied` with a reason code in the manifest, never empty data that
+  looks like a result.
+- `aliases.json` (mode 0600) sits beside the bundle, never inside it. A later run into
+  the same `--out` reuses its salt, so aliases stay stable across bundles. It also
+  holds the salt: keep it, and do not upload it.
+
+## Development
+
+```bash
+cd collector
+uv run pytest       # reads the platform's schema by repository path
+uv run pyright
+./build.sh          # dist/datapace_collector-0.1.0-py3-none-any.whl and
+                    # dist/datapace-collector-0.1.0.pyz, smoke-run on 3.10 and 3.9
+```
+
+`make ci-collector` from the repo root runs all of it plus ruff. Ruff and pyright both
+target Python 3.10, so newer syntax fails the check rather than a prospect's install.

datapace_collector-0.2.0/README.md

@@ -0,0 +1,79 @@
+# datapace-collector
+
+The customer-run half of the Cloud Self-Assessment (DAT-891, ADR-0023). A prospect runs
+it against AWS accounts they pick. It writes one evidence bundle (`.tgz`) that matches
+the frozen v1 schema at `src/datapace/domain/assessment/bundle_schema_v1.json`, plus a
+local `aliases.json` that maps each alias in the bundle back to the real resource.
+
+Its own distribution, Python ≥ 3.10, one runtime dependency (boto3). It imports nothing
+from `datapace`.
+
+```
+datapace-collector --profile 111111111111=prod --profile 222222222222=stage \
+  [--billing-profile payer] --regions us-east-1,eu-west-1 --out ./evidence
+```
+
+- **Only the named profiles are opened.** Without `--profile` it exits 2; it never
+  lists local profiles. Each profile must really be the account it is mapped to
+  (`sts:GetCallerIdentity`), or it exits 3.
+- **Preflight** probes every permission per account and region and prints each denial
+  with the IAM action and the input it costs. `rds:DescribeDBInstances` denied
+  everywhere → exit 3, nothing written.
+- **Collects** inventory, 90 days of daily and monthly RDS cost, RI/Savings Plans
+  coverage, reserved instances, manual snapshots and 30 days of hourly metrics (eight
+  `GetMetricData` workers, 60 s timeout, 3 retries).
+- **`--billing-profile`** reads Cost Explorer from a payer; lines for accounts not
+  selected are dropped.
+- **Exit codes:** 0 bundle written (complete or partial), 1 internal error, 2 usage,
+  3 preflight failed, 130 interrupted (partial bundle kept).
+
+## Running it
+
+Python ≥ 3.10. macOS's system `python3` is 3.9: the `.pyz` stops with a message
+naming the minimum version and exits 2; install a newer Python (python.org, Homebrew
+or uv) and run it with that. The same version ships three ways, built by `build.sh`:
+
+- **The `.pyz`**, for machines where nothing can be installed:
+  `python3 datapace-collector-<v>.pyz --profile … --out …`. boto3 is inside the file,
+  so it needs no network install. Its dependencies are exactly the hash-checked set
+  in `uv.lock`, never a fresh resolution. Bundles record `distribution: pyz`.
+- **The downloaded wheel**: `pip install ./datapace_collector-<v>-py3-none-any.whl`,
+  then `datapace-collector …`.
+- **PyPI**: `uvx datapace-collector@0.2.0 …` <!-- x-release-please-version -->
+  or `pip install datapace-collector==0.2.0`. <!-- x-release-please-version -->
+
+PyPI and the downloaded wheel are the same file, so both record `distribution: wheel`
+and the bundle cannot tell them apart.
+
+On first run the `.pyz` unpacks itself into
+`~/.shiv/datapace-collector-<v>.pyz_<build-id>/`, or under `$SHIV_ROOT` if set, and
+reuses that copy afterwards. It unpacks before the version check, so a run refused
+on Python 3.9 leaves the copy too. Remove it with `rm -rf ~/.shiv/datapace-collector-*`.
+
+## What keeps the bundle safe
+
+- `operations.py`'s `READ_ONLY_OPERATIONS` is every AWS call the collector may make.
+  `tests/test_safety.py` records each botocore call and fails on anything outside it.
+- Every record is built field by field from the schema's closed properties: an
+  allowlist, not a redaction. Raw ids become `HMAC(salt, kind|account|region|id)`
+  aliases. `tests/test_leaks.py` seeds account ids, ARNs, endpoints, tags,
+  `MasterUsername` and ARN-bearing AccessDenied messages, and asserts none reaches a
+  bundle byte.
+- A denied input is `denied` with a reason code in the manifest, never empty data that
+  looks like a result.
+- `aliases.json` (mode 0600) sits beside the bundle, never inside it. A later run into
+  the same `--out` reuses its salt, so aliases stay stable across bundles. It also
+  holds the salt: keep it, and do not upload it.
+
+## Development
+
+```bash
+cd collector
+uv run pytest       # reads the platform's schema by repository path
+uv run pyright
+./build.sh          # dist/datapace_collector-0.1.0-py3-none-any.whl and
+                    # dist/datapace-collector-0.1.0.pyz, smoke-run on 3.10 and 3.9
+```
+
+`make ci-collector` from the repo root runs all of it plus ruff. Ruff and pyright both
+target Python 3.10, so newer syntax fails the check rather than a prospect's install.

datapace_collector-0.2.0/datapace_collector/__init__.py

@@ -0,0 +1 @@
+"""The customer-run Datapace evidence collector (DAT-891)."""

datapace_collector-0.2.0/datapace_collector/aliases.py

@@ -0,0 +1,74 @@
+"""Stable, salted aliases for every raw AWS identifier, and the local lookup.
+
+An alias is `kind_` plus 12 hex digits of HMAC-SHA256(salt, kind|account|
+region|identifier), the construction the DAT-886 fixtures use. The salt stays
+on the prospect's machine in `aliases.json`, beside the bundle and never inside
+it (ADR-0023 §3). A later run into the same `--out` reuses that salt, so the
+same resource gets the same alias across bundles.
+"""
+
+from __future__ import annotations
+
+import hashlib
+import hmac
+import json
+import os
+import secrets
+from pathlib import Path
+
+ALIASES = "aliases.json"
+
+
+class AliasFileError(Exception):
+    """An `aliases.json` exists but cannot be used; replacing it would break stability."""
+
+
+class Aliaser:
+    def __init__(self, salt: bytes, entries: dict[str, dict[str, str]]) -> None:
+        self._salt = salt
+        self._entries = entries
+
+    @classmethod
+    def load(cls, out: Path) -> Aliaser:
+        path = out / ALIASES
+        if not path.exists():
+            return cls(secrets.token_bytes(32), {})
+        try:
+            data = json.loads(path.read_text())
+            return cls(bytes.fromhex(data["salt"]), dict(data["aliases"]))
+        except (OSError, ValueError, KeyError, TypeError) as exc:
+            raise AliasFileError(
+                f"{path} is unreadable ({type(exc).__name__}); move it away to start"
+                " with a new salt, which changes every alias"
+            ) from None
+
+    def alias(self, kind: str, account: str, region: str, identifier: str) -> str:
+        message = f"{kind}|{account}|{region}|{identifier}".encode()
+        digest = hmac.new(self._salt, message, hashlib.sha256).hexdigest()
+        alias = f"{kind}_{digest[:12]}"
+        self._entries[alias] = {
+            "kind": kind,
+            "account": account,
+            "region": region,
+            "identifier": identifier,
+        }
+        return alias
+
+    def account(self, account: str) -> str:
+        return self.alias("acct", account, "", account)
+
+    def save(self, out: Path) -> Path:
+        """Write the lookup into `out`, mode 0600, atomically."""
+        path = out / ALIASES
+        tmp = out / f".{ALIASES}.tmp"
+        body = {"salt": self._salt.hex(), "aliases": self._entries}
+        tmp.unlink(missing_ok=True)
+        try:
+            fd = os.open(tmp, os.O_WRONLY | os.O_CREAT | os.O_TRUNC, 0o600)
+            with os.fdopen(fd, "w") as f:
+                json.dump(body, f, indent=1, sort_keys=True)
+            os.replace(tmp, path)
+        except BaseException:
+            tmp.unlink(missing_ok=True)
+            raise
+        return path