1 Answer
- Newest
- Most votes
- Most comments
0
For SourceIdentity Propagation you can try these troubleshoots as per Sagemaker documentation:
- Enable it at the domain level during creation or update.
- For domain creation, use the --domain-settings
ExecutionRoleIdentityConfig=USER_PROFILE_NAME
parameter with AWS CLI or create-domain API. - For updating an existing domain, include the --domain-settings-for-update
ExecutionRoleIdentityConfig=USER_PROFILE_NAME
parameter. Stop all apps in the domain before updating. - Single-user setups via quick setup automatically enable source identity.
- Source identity allows administrators to view user profile names in CloudTrail logs for auditing and access control.
Relevant content
- Accepted Answerasked 5 months ago
- asked 3 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago