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ヶ月前
btw, I am in GCC (Government Commercial Cloud in Singapore).
Can you share the trust policy of that role?