1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
SageMaker assumes the AmazonSageMakerServiceCatalogProductsLaunchRole
role to access and launch Projects. If you aren't using the AmazonSageMakerFullAccess
policy for your Studio or user profile's execution role, make sure your Studio execution role has enough permissions to assume the AmazonSageMakerServiceCatalogProductsLaunchRole
.
You don't need to add Admin access to the launch role, it has the minimum required permissions to launch a service catalog product, including assuming the AmazonSageMakerServiceCatalogProductsUseRole
for running the project successfully.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
btw, I am in GCC (Government Commercial Cloud in Singapore).
Can you share the trust policy of that role?