Skip to main content

MAZENG-FT-8 · Connect and validate a supported cloud account

Feature intent

A user needs to prove usable access to a cloud account before Maze relies on that connection.

Why it matters

A user needs to prove usable access to a cloud account before Maze relies on that connection.

Expected outcome

Avoids repeated credential entry and catches unusable credentials before they affect project work.

In scope

  • Select AWS, Azure, Google Cloud, or IBM Cloud as the connection provider.
  • Collect the selected provider's required credential fields.
  • Validate credentials before saving a connection.
  • Name and describe the validated connection and save it for reuse.
  • Support the registered-device QR handoff only if that interaction is explicitly retained in Next Gen scope.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-2
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    The credential form reflects the selected provider's requirements.

  2. 02

    Invalid credentials cannot advance to a usable saved connection.

  3. 03

    Valid credentials create a named connection visible in account settings.

  4. 04

    Cancellation or failed device confirmation leaves no usable connection behind.

Dependencies and risks

Dependencies

None recorded.

Risks

  • The Feature depends on external provider APIs and maintained provider-specific credential schemas.
  • The optional QR handoff depends on registered-device behavior from MAZENG-FT-6.
  • Secure secret storage, encryption, rotation, and key-recovery behavior require Architecture and security decisions.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source