1 回答
- 最新
- 投票最多
- 评论最多
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.
已回答 2 年前
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 6 个月前
- AWS 官方已更新 1 年前
btw, I am in GCC (Government Commercial Cloud in Singapore).
Can you share the trust policy of that role?