AMARQUANTAMARQUANTSecure login

PRODUCTION OPERATIONS

Private by default.
Observable by design.

The public site explains the product. The terminal, data, user administration, and operational controls remain behind authenticated access.

ACCESS

Administrator-managed users

Public registration is unavailable. The protected bootstrap administrator creates viewer or trader accounts and controls account status.

  • Mandatory password change for new and reset users
  • Session revocation on password rotation
  • Inactive accounts cannot sign in or refresh
AUTHENTICATION

Defensive sign-in

Login attempts are throttled by email and source address. Passwords are entered through secure prompts and must not be placed in logs or command history.

  • Five failed attempts per 15-minute window
  • Redis-backed throttling
  • HTTPS-only production access
DELIVERY

Immutable deployment

Passing main-branch changes produce a commit-addressed image, migrate the database, update ECS, and finish with an HTTPS smoke test.

  • Separate publisher and deployer roles
  • Health-check rollback
  • Production deployment alerts
RECOVERY

Monitored pilot

The pilot stays cost-aware and single-AZ while alarms watch application health, infrastructure pressure, and storage.

  • Seven-day encrypted RDS backups
  • AWS budget alerts
  • Restore procedure maintained in the repository
Credential policy: AMARQUANT passwords, broker secrets, recovery codes, and session tokens must never be shared in chat, committed to source, or exposed in logs.