Skip to main content

What is an operation role

Roles that you can scope to the specific task, and use in runbooks so they have built in guardrails for your maintenance or upgrade activities.

Required roles

Every app config must define three standard roles in its permissions config:
  • Provision: provisions and reprovisions the install, and deploys all components.
  • Deprovision: deprovisions the install, and tears down all components.
  • Maintenance: everything else, such as single component deploys, action runs, and input changes.

Scope custom operation roles to a task

Add more specific roles matching how you manage your customer environments, for example:
  • Deploy and teardown for one component: a deploy role that can create and update the component’s Lambda function, and a teardown role that can only delete it. See the deploy and teardown example.
  • An action that rotates a password: a role that can only update that one secret, set on the action. See assign a role to an entity.
  • One role for every teardown: an app-wide rule that sends all component teardowns to a delete-only role. See set app-wide rules.
When you need to resolve a deeper issue or outage, use a break glass role.

When Nuon uses a role

Each time Nuon changes something in your customer’s account, the runner assumes a role to do it. That happens when it:
  • Sets up, updates, or removes the install’s base infrastructure (the sandbox)
  • Deploys or removes a component
  • Runs an action
By default, each of these uses one of the three standard roles. You can choose a different role in three places:
  • On the sandbox, a component, or an action: in its config file.
  • For the whole app: with rules in operation_roles.toml, such as one role for every component teardown.
  • For a single run: from the dashboard or command line.
If you set a role in more than one place, see which role a run uses.

Next steps