Security

Hosting and operations

Where the service runs, how its network is closed, how Ambient Assist AI reaches it, what the audit log records, and how the software is kept current.

Hosted inAWS
DatabasePrivate, encrypted, backed up
Ambient Assist AI’s accessOver a private VPN only
Audit logSix years
On this page

Hosting#

  • The service runs in AWS. Only the load balancer can reach the service’s tasks. A task connects outbound only to the database and to HTTPS endpoints.
  • The database keeps automated backups for seven days in production. Deletion protection is on.

Ambient Assist AI’s access#

  • Ambient Assist AI reaches the service’s administration only over a private VPN.
  • The administration pages show no member content.
  • Every change Ambient Assist AI makes to your organization appears in your audit log as “Ambient Assist AI”.

The audit log#

  • The service writes an audit row for every administrative action in your organization, and for every change Ambient Assist AI makes to it.
  • A row holds ids, counts and flags only, never an email, a name or free text. The service writes the row in the same database transaction as the change.
  • A settings change records which keys changed, never their values. Every save carries a version, and the service refuses a save over a newer version.
  • The log is kept six years. It survives the deletion of an organization or an account.
  • Your owners and admins read your organization’s log on the admin dashboard. See Audit log.

The software#

Every dependency is pinned in a lockfile. The service’s container images pin their base images by digest.

Service health#

The service records metrics and traces, and alarms notify Ambient Assist AI. Service logs are kept 30 days.

Esc
↑ ↓ to moveEnter to open