Set up Staging Construct Examples
To set up stage constructs for your Amazon SageMaker Model Registry, the administrator will need to grant the relevant permissions to the intended roles. The following provides examples on how to set up stage constructs for various roles.
Note
Users within a Amazon SageMaker AI domain will be able to view all stages defined within the domain, but can only use the ones they have permissions for.
Stages are defined by the ModelLifeCycle
parameter and have the
following structure. The administrator sets up the permissions for which
stage
and stageStatus
can be accessed by which
roles. The users assuming a role can use the relevant stage
and
stageStatus
and include their own
stageDescription
.
ModelLifeCycle { stage: String # Required (e.g., Development/QA/Production) stageStatus: String # Required (e.g., PendingApproval/Approved/Rejected) stageDescription: String # Optional }
The following table contains Model Registry pre-defined stage construct templates. You can define your own stage constructs based on your use cases. The relevant permissions will need to be set up before users can use them.
Stage | Stage status |
---|---|
Proposal |
PendingApproval |
Development |
InProgress |
QA |
OnHold |
PreProduction |
Approved |
Production |
Rejected |
Archived |
Retired |
The ModelLifeCycle
parameter can be invoked by the following
APIs:
To get Amazon EventBridge notifications on any model status update, see the example in Get event notifications for ModelLifeCycle. For an example EventBridge payload you may receive, see Model package state change.