Synopsis
Creates, in YOUR account, the security boundary that constrains Kubox and the one identity it connects as: KuboxBoundary, the KuboxConnect policy, and the KuboxConnect role carrying that boundary from the moment it exists. THIS IS THE ONE COMMAND THAT USES YOUR ADMINISTRATOR’S AUTHORITY. It creates the cap; everything afterwards runs inside it, as KuboxConnect, and cannot reach back to the credentials you run this with. Kubox never creates its own boundary, which is why this step is yours. It does exactly what the connection’s bootstrap contract says, because both are rendered from one declaration: what the console shows you to paste is what this runs. Run it again freely — every step reports what it found rather than failing on something that already exists.Options
Global options
See global options.SEE ALSO
- kubox cloud - Connect and manage the cloud accounts Kubox builds into