1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
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.
respondido hace 2 años
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
btw, I am in GCC (Government Commercial Cloud in Singapore).
Can you share the trust policy of that role?