A.I. Kung Fu

Tuesday, November 10, 2020

Configuring Amazon SageMaker Studio for teams and groups with complete resource isolation

Amazon SageMaker is a fully managed service that provides every machine learning (ML) developer and data scientist with the ability to build, train, and deploy ML models quickly. Amazon SageMaker Studio is a web-based, integrated development environment (IDE) for ML that lets you build, train, debug, deploy, and monitor your ML models. Amazon SageMaker Studio provides all the tools you need to take your models from experimentation to production while boosting your productivity. You can write code, track experiments, visualize data, and perform debugging and monitoring within a single, integrated visual interface.

This post outlines how to configure access control for teams or groups within Amazon SageMaker Studio using attribute-based access control (ABAC). ABAC is a powerful approach that you can utilize to configure Studio so that different ML and data science teams have complete isolation of team resources.

We provide guidance on how to configure Amazon SageMaker Studio access for both AWS Identity and Access Management (IAM) and AWS Single Sign-On (AWS SSO) authentication methods. This post helps you set up IAM policies for users and roles using ABAC principals. To demonstrate the configuration, we set up two teams as shown in the following diagram and showcase two use cases:

Use case 1 – Only User A1 can access their studio environment; User A2 can’t access User A1’s environment, and vice versa
Use case 2 – Team B users cannot access artifacts (experiments, etc.) created by Team A members

You can configure policies according to your needs. You can even include a project tag in case you want to further restrict user access by projects within a team. The approach is very flexible and scalable.

Authentication

Amazon SageMaker Studio supports the following authentication methods for onboarding users. When setting up Studio, you can pick an authentication method that you use for all your users:

IAM – Includes the following:
- IAM users – Users managed in IAM
- AWS account federation – Users managed in an external identity provider (IdP)
AWS SSO – Users managed in an external IdP federated using AWS SSO

Data science user personas

The following table describes two different personas that interact with Amazon SageMaker Studio resources and the level of access they need to fulfill their duties. We use this table as a high-level requirement to model IAM roles and policies to establish desired controls based on resource ownership at the team and user level.

User Personas

Permissions

Admin User

Create, modify, delete any IAM resource.

Create Amazon SageMaker Studio user profiles with a tag.

Read and describe Amazon SageMaker resources.

Data Scientists or Developers

Launch an Amazon SageMaker Studio IDE assigned to a specific IAM or AWS SSO user.

Create Amazon SageMaker resources with necessary tags. For this post, we use the team tag.

Update, delete, and run resources created with a specific tag.

Read and describe Amazon SageMaker resources.

Solution overview

We use the preceding requirements to model roles and permissions required to establish controls. The following flow diagram outlines the different configuration steps:

Applying your policy to the admin user

You should apply the following policy to the admin user who creates Studio user profiles. This policy requires the admin to include the studiouserid tag. You could use a different name for the tag if need be. The Studio console doesn’t allow you to add tags when creating user profiles, so we use the AWS Command Line Interface (AWS CLI).

For admin users managed in IAM, attach the following policy to the user. For admin users managed in an external IdP, add the following policy to the rule that the user assumes upon federation. The following policy enforces the studiouserid tag to be present when the sagemaker:CreateUserProfile action is invoked.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "CreateSageMakerStudioUserProfilePolicy",
            "Effect": "Allow",
            "Action": "sagemaker:CreateUserProfile",
            "Resource": "*",
            "Condition": {
                "ForAnyValue:StringEquals": {
                    "aws:TagKeys": [
                        "studiouserid"
                    ]
                }
            }
        }
    ]
}

AWS SSO doesn’t require this policy; it performs the identity check.

Assigning the policy to Studio users

The following policy limits Studio access to the respective users by requiring the resource tag to match the user name for the sagemaker:CreatePresignedDomainUrl action. When a user tries to access the Amazon SageMaker Studio launch URL, this check is performed.

For IAM users, attach the following policy to the user. Use the user name for the studiouserid tag value.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerPresignedUrlPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:CreatePresignedDomainUrl"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "sagemaker:ResourceTag/studiouserid": "${aws:username}" 
                }
            }
        }
    ]
}

For AWS account federation, attach the following policy to role that the user assumes after federation:

{
   "Version": "2012-10-17",
   "Statement": [
       {
           "Sid": "AmazonSageMakerPresignedUrlPolicy",
           "Effect": "Allow",
           "Action": [
                "sagemaker:CreatePresignedDomainUrl"
           ],
           "Resource": "*",
           "Condition": {
                  "StringEquals": {
                      "sagemaker:ResourceTag/studiouserid": "${aws:PrincipalTag/studiouserid}"
                 }
            }
      }
  ]
}

Add the following statement to this policy in the Trust Relationship section. This statement defines the allowed transitive tag.

"Statement": [
     {
        --Existing statements
      },
      {
      "Sid": "IdentifyTransitiveTags",
      "Effect": "Allow",
      "Principal": {
        "Federated": "arn:aws:iam::<account id>:saml-provider/<identity provider>"
      },
      "Action": "sts:TagSession",
      "Condition": {
        "ForAllValues:StringEquals": {
          "sts:TransitiveTagKeys": [
            "studiouserid"
          ]
        }
      }
  ]

For users managed in AWS SSO, this policy is not required. AWS SSO performs the identity check.

Creating roles for the teams

To create roles for your teams, you must first create the policies. For simplicity, we use the same policies for both teams. In most cases, you just need one set of policies for all teams, but you have the flexibility to create different policies for different teams. In the second step, you create a role for each team, attach the policies, and tag the roles with appropriate team tags.

Creating the policies

Create the following policies. For this post, we split them into three policies for more readability, but you can create them according to your needs.

Policy 1: Amazon SageMaker read-only access

The following policy gives privileges to List and Describe Amazon SageMaker resources. You can customize this policy according to your needs.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerDescribeReadyOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Describe*",
                "sagemaker:GetSearchSuggestions"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerListOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:List*"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerUIandMetricsOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:*App",
                "sagemaker:Search",
                "sagemaker:RenderUiTemplate",
                "sagemaker:BatchGetMetrics"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerEC2ReadOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeDhcpOptions",
                "ec2:DescribeNetworkInterfaces",
                "ec2:DescribeRouteTables",
                "ec2:DescribeSecurityGroups",
                "ec2:DescribeSubnets",
                "ec2:DescribeVpcEndpoints",
                "ec2:DescribeVpcs"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerIAMReadOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "iam:ListRoles"
            ],
            "Resource": "*"
        }
    ]
}

Policy 2: Amazon SageMaker access for supporting services

The following policy gives privileges to create, read, update, and delete access to Amazon Simple Storage Service (Amazon S3), Amazon Elastic Container Registry (Amazon ECR), and Amazon CloudWatch, and read access to AWS Key Management Service (AWS KMS). You can customize this policy according to your needs.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerCRUDAccessS3Policy",
            "Effect": "Allow",
            "Action": [
"s3:PutObject",
"s3:GetObject",
"s3:AbortMultipartUpload",
"s3:DeleteObject",
"s3:CreateBucket",
"s3:ListBucket",
"s3:PutBucketCORS",
"s3:ListAllMyBuckets",
"s3:GetBucketCORS",
                "s3:GetBucketLocation"         
              ],
            "Resource": "<S3 BucketName>"
        },
        {
            "Sid": "AmazonSageMakerReadOnlyAccessKMSPolicy",
            "Effect": "Allow",
            "Action": [
                "kms:DescribeKey",
                "kms:ListAliases"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCRUDAccessECRPolicy",
            "Effect": "Allow",
            "Action": [
"ecr:Set*",
"ecr:CompleteLayerUpload",
"ecr:Batch*",
"ecr:Upload*",
"ecr:InitiateLayerUpload",
"ecr:Put*",
"ecr:Describe*",
"ecr:CreateRepository",
"ecr:Get*",
                        "ecr:StartImageScan"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCRUDAccessCloudWatchPolicy",
            "Effect": "Allow",
            "Action": [
"cloudwatch:Put*",
"cloudwatch:Get*",
"cloudwatch:List*",
"cloudwatch:DescribeAlarms",
"logs:Put*",
"logs:Get*",
"logs:List*",
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:ListLogDeliveries",
"logs:Describe*",
"logs:CreateLogDelivery",
"logs:PutResourcePolicy",
                        "logs:UpdateLogDelivery"
            ],
            "Resource": "*"
        }
    ]
}

Policy 3: Amazon SageMaker Studio developer access

The following policy gives privileges to create, update, and delete Amazon SageMaker Studio resources.
It also enforces the team tag requirement during creation. In addition, it enforces start, stop, update, and delete actions on resources restricted only to the respective team members.

The team tag validation condition in the following code makes sure that the team tag value matches the principal’s team. Refer to the bolded code for specifcs.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerStudioCreateApp",
            "Effect": "Allow",
            "Action": [
                "sagemaker:CreateApp"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerStudioIAMPassRole",
            "Effect": "Allow",
            "Action": [
                "iam:PassRole"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerInvokeEndPointRole",
            "Effect": "Allow",
            "Action": [
                "sagemaker:InvokeEndpoint"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerAddTags",
            "Effect": "Allow",
            "Action": [
                "sagemaker:AddTags"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCreate",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Create*"
            ],
            "Resource": "*",
            "Condition": { "ForAnyValue:StringEquals": { "aws:TagKeys": [ "team" ] }, "StringEqualsIfExists": { "aws:RequestTag/team": "${aws:PrincipalTag/team}" } }
        },
        {
            "Sid": "AmazonSageMakerUpdateDeleteExecutePolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Delete*",
                "sagemaker:Stop*",
                "sagemaker:Update*",
                "sagemaker:Start*",
                "sagemaker:DisassociateTrialComponent",
                "sagemaker:AssociateTrialComponent",
                "sagemaker:BatchPutMetrics"
            ],
            "Resource": "*",
            "Condition": { "StringEquals": { "aws:PrincipalTag/team": "${sagemaker:ResourceTag/team}" } }
        }
    ]
}

Creating and configuring the roles

You can now create a role for each team with these policies. Tag the roles on the IAM console or with the CLI command. The steps are the same for all three authentication types. For example, tag the role for Team A with the tag key= team and value = “<Team Name>”.

Creating the Amazon SageMaker Studio user profile

In this step, we add the studiouserid tag when creating Studio user profiles. The steps are slightly different for each authentication type.

IAM users

For IAM users, you create Studio user profiles for each user by including the role that was created for the team the user belongs to. The following code is a sample CLI command. As of this writing, including a tag when creating a user profile is available only through AWS CLI.

aws sagemaker create-user-profile --domain-id <domain id> --user-profile-name <unique profile name> --tags Key=studiouserid,Value=<aws user name> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name>

AWS account federation

For AWS account federation, you create a user attribute (studiouserid) in an external IdP with a unique value for each user. The following code shows how to configure the attribute in Okta:

Example below shows how to add “studiouserid” attribute in OKTA. In OKTA’s SIGN ON METHODS screen, configure following SAML 2.0 attributes, as shown in the image below. 

Attribute 1:
Name: https://aws.amazon.com/SAML/Attributes/PrincipalTag:studiouserid 
Value: user.studiouserid

Attribute 2:
Name: https://aws.amazon.com/SAML/Attributes/TransitiveTagKeys
Value: {"studiouserid"}

The following screenshot shows the attributes on the Okta console.

Next, create the user profile using the following command. Use the user attribute value in the preceding step for the studiouserid tag value.

aws sagemaker create-user-profile --domain-id <domain id> --user-profile-name <unique profile name> --tags Key=studiouserid,Value=<user attribute value> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name>

AWS SSO

For instructions on assigning users in AWS SSO, see Onboarding Amazon SageMaker Studio with AWS SSO and Okta Universal Directory.

Update the Studio user profile to include the appropriate execution role that was created for the team that the user belongs to. See the following CLI command:

aws sagemaker update-user-profile --domain-id <domain id> --user-profile-name <user profile name> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name> --region us-west-2

Validating that only assigned Studio users can access their profiles

When a user tries to access a Studio profile that doesn’t have studiouserid tag value matching their user name, an AccessDeniedException error occurs. You can test this by copying the link for Launch Studio on the Amazon SageMaker console and accessing it when logged in as a different user. The following screenshot shows the error message.

Validating that only respective team members can access certain artifacts

In this step, we show how to configure Studio so that members of a given team can’t access artifacts that another team creates.

In our use case, a Team A user creates an experiment and tags that experiment with the team tag. This limits access to this experiment to Team A users only. See the following code:

import sys
!{sys.executable} -m pip install sagemaker
!{sys.executable} -m pip install sagemaker-experiments

import time
import sagemaker
from smexperiments.experiment import Experiment

demo_experiment = Experiment.create(experiment_name = "USERA1TEAMAEXPERIMENT1",
                                    description = "UserA1 experiment",
                                    tags = [{'Key': 'team', 'Value': 'TeamA'}])

If a user who is not in Team A tries to delete the experiment, Studio denies the delete action. See the following code:

#command run from TeamB User Studio Instance
import time
from smexperiments.experiment import Experiment
experiment_to_cleanup = Experiment.load(experiment_name="USERA1TEAMAEXPERIMENT1")
experiment_to_cleanup.delete()

[Client Error]
An error occurred (AccessDeniedException) when calling the DeleteExperiment operation: User: arn:aws:sts:: :<AWS Account ID>::assumed-role/ SageMakerStudioDeveloperTeamBRole/SageMaker is not authorized to perform: sagemaker:DeleteExperiment on resource: arn:aws:sagemaker:us-east-1:<AWS Account ID>:experiment/usera1teamaexperiment1

Conclusion

In this post, we demonstrated how to isolate Amazon SageMaker Studio access using the ABAC technique. We showcased two use cases: restricting access to a Studio profile to only the assigned user (using the studiouserid tag) and restricting access to Studio artifacts to team members only. We also showed how to limit access to experiments to only the members of the team using the team tag. You can further customize policies by applying more tags to create more complex hierarchical controls.

Try out this solution for isolating resources by teams or groups in Amazon SageMaker Studio. For more information about using ABAC as an authorization strategy, see What is ABAC for AWS?

About the Authors

Vikrant Kahlir is Senior Solutions Architect in the Solutions Architecture team. He works with AWS strategic customers product and engineering teams to help them with technology solutions using AWS services for Managed Databases, AI/ML, HPC, Autonomous Computing, and IoT.

Rakesh Ramadas is an ISV Solution Architect at Amazon Web Services. His focus areas include AI/ML and Big Data.

Rama Thamman is a Software Development Manager with the AI Platforms team, leading the ML Migrations team.

from AWS Machine Learning Blog https://ift.tt/38vljnT
via A.I .Kung Fu

Man born without a hand gets Metal Gear Solid 3D-printed bionic arm

Daniel Melville gets a Metal Gear Solid bionic arm.

Daniel Melville, who was born without a right hand, has a real bionic arm based on the Metal Gear Solid video game series.Read More

from VentureBeat https://ift.tt/36migvL
via A.I .Kung Fu

The best board games to give for 2020: Gloomhaven, Marvel United and more - CNET

The hottest thing in gaming right now is classic low-tech tabletop experiences. Here's our line-up of some of the best board games for this year.

from CNET News https://ift.tt/3piFQSE
via A.I .Kung Fu

Ex-Microsoft engineer gets 9-year prison sentence for fraud scheme - CNET

He'd racked up 18 federal felonies leading up to the sentencing.

from CNET News https://ift.tt/3nc9WWi
via A.I .Kung Fu

12 best TV shows to stream on Disney Plus - CNET

Looking for more great shows like The Mandalorian? Let's round up Disney's best gems.

from CNET News https://ift.tt/35iHpbt
via A.I .Kung Fu

Best holiday gifts under $100 for 2020 - CNET

Looking for an affordable gift this holiday buying season? Here's a great lineup of gift ideas to help stretch your Benjamin.

from CNET News https://ift.tt/3peranD
via A.I .Kung Fu

Configuring Amazon SageMaker Studio for teams and groups with complete resource isolation

Use case 1 – Only User A1 can access their studio environment; User A2 can’t access User A1’s environment, and vice versa
Use case 2 – Team B users cannot access artifacts (experiments, etc.) created by Team A members

Authentication

Amazon SageMaker Studio supports the following authentication methods for onboarding users. When setting up Studio, you can pick an authentication method that you use for all your users:

IAM – Includes the following:
- IAM users – Users managed in IAM
- AWS account federation – Users managed in an external identity provider (IdP)
AWS SSO – Users managed in an external IdP federated using AWS SSO

Data science user personas

User Personas

Permissions

Admin User

Create, modify, delete any IAM resource.

Create Amazon SageMaker Studio user profiles with a tag.

Read and describe Amazon SageMaker resources.

Data Scientists or Developers

Launch an Amazon SageMaker Studio IDE assigned to a specific IAM or AWS SSO user.

Create Amazon SageMaker resources with necessary tags. For this post, we use the team tag.

Update, delete, and run resources created with a specific tag.

Read and describe Amazon SageMaker resources.

Solution overview

We use the preceding requirements to model roles and permissions required to establish controls. The following flow diagram outlines the different configuration steps:

Applying your policy to the admin user

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "CreateSageMakerStudioUserProfilePolicy",
            "Effect": "Allow",
            "Action": "sagemaker:CreateUserProfile",
            "Resource": "*",
            "Condition": {
                "ForAnyValue:StringEquals": {
                    "aws:TagKeys": [
                        "studiouserid"
                    ]
                }
            }
        }
    ]
}

AWS SSO doesn’t require this policy; it performs the identity check.

Assigning the policy to Studio users

For IAM users, attach the following policy to the user. Use the user name for the studiouserid tag value.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerPresignedUrlPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:CreatePresignedDomainUrl"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "sagemaker:ResourceTag/studiouserid": "${aws:username}" 
                }
            }
        }
    ]
}

For AWS account federation, attach the following policy to role that the user assumes after federation:

{
   "Version": "2012-10-17",
   "Statement": [
       {
           "Sid": "AmazonSageMakerPresignedUrlPolicy",
           "Effect": "Allow",
           "Action": [
                "sagemaker:CreatePresignedDomainUrl"
           ],
           "Resource": "*",
           "Condition": {
                  "StringEquals": {
                      "sagemaker:ResourceTag/studiouserid": "${aws:PrincipalTag/studiouserid}"
                 }
            }
      }
  ]
}

Add the following statement to this policy in the Trust Relationship section. This statement defines the allowed transitive tag.

"Statement": [
     {
        --Existing statements
      },
      {
      "Sid": "IdentifyTransitiveTags",
      "Effect": "Allow",
      "Principal": {
        "Federated": "arn:aws:iam::<account id>:saml-provider/<identity provider>"
      },
      "Action": "sts:TagSession",
      "Condition": {
        "ForAllValues:StringEquals": {
          "sts:TransitiveTagKeys": [
            "studiouserid"
          ]
        }
      }
  ]

For users managed in AWS SSO, this policy is not required. AWS SSO performs the identity check.

Creating roles for the teams

Creating the policies

Create the following policies. For this post, we split them into three policies for more readability, but you can create them according to your needs.

Policy 1: Amazon SageMaker read-only access

The following policy gives privileges to List and Describe Amazon SageMaker resources. You can customize this policy according to your needs.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerDescribeReadyOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Describe*",
                "sagemaker:GetSearchSuggestions"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerListOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:List*"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerUIandMetricsOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:*App",
                "sagemaker:Search",
                "sagemaker:RenderUiTemplate",
                "sagemaker:BatchGetMetrics"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerEC2ReadOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeDhcpOptions",
                "ec2:DescribeNetworkInterfaces",
                "ec2:DescribeRouteTables",
                "ec2:DescribeSecurityGroups",
                "ec2:DescribeSubnets",
                "ec2:DescribeVpcEndpoints",
                "ec2:DescribeVpcs"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerIAMReadOnlyPolicy",
            "Effect": "Allow",
            "Action": [
                "iam:ListRoles"
            ],
            "Resource": "*"
        }
    ]
}

Policy 2: Amazon SageMaker access for supporting services

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerCRUDAccessS3Policy",
            "Effect": "Allow",
            "Action": [
"s3:PutObject",
"s3:GetObject",
"s3:AbortMultipartUpload",
"s3:DeleteObject",
"s3:CreateBucket",
"s3:ListBucket",
"s3:PutBucketCORS",
"s3:ListAllMyBuckets",
"s3:GetBucketCORS",
                "s3:GetBucketLocation"         
              ],
            "Resource": "<S3 BucketName>"
        },
        {
            "Sid": "AmazonSageMakerReadOnlyAccessKMSPolicy",
            "Effect": "Allow",
            "Action": [
                "kms:DescribeKey",
                "kms:ListAliases"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCRUDAccessECRPolicy",
            "Effect": "Allow",
            "Action": [
"ecr:Set*",
"ecr:CompleteLayerUpload",
"ecr:Batch*",
"ecr:Upload*",
"ecr:InitiateLayerUpload",
"ecr:Put*",
"ecr:Describe*",
"ecr:CreateRepository",
"ecr:Get*",
                        "ecr:StartImageScan"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCRUDAccessCloudWatchPolicy",
            "Effect": "Allow",
            "Action": [
"cloudwatch:Put*",
"cloudwatch:Get*",
"cloudwatch:List*",
"cloudwatch:DescribeAlarms",
"logs:Put*",
"logs:Get*",
"logs:List*",
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:ListLogDeliveries",
"logs:Describe*",
"logs:CreateLogDelivery",
"logs:PutResourcePolicy",
                        "logs:UpdateLogDelivery"
            ],
            "Resource": "*"
        }
    ]
}

Policy 3: Amazon SageMaker Studio developer access

The team tag validation condition in the following code makes sure that the team tag value matches the principal’s team. Refer to the bolded code for specifcs.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AmazonSageMakerStudioCreateApp",
            "Effect": "Allow",
            "Action": [
                "sagemaker:CreateApp"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerStudioIAMPassRole",
            "Effect": "Allow",
            "Action": [
                "iam:PassRole"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerInvokeEndPointRole",
            "Effect": "Allow",
            "Action": [
                "sagemaker:InvokeEndpoint"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerAddTags",
            "Effect": "Allow",
            "Action": [
                "sagemaker:AddTags"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AmazonSageMakerCreate",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Create*"
            ],
            "Resource": "*",
            "Condition": { "ForAnyValue:StringEquals": { "aws:TagKeys": [ "team" ] }, "StringEqualsIfExists": { "aws:RequestTag/team": "${aws:PrincipalTag/team}" } }
        },
        {
            "Sid": "AmazonSageMakerUpdateDeleteExecutePolicy",
            "Effect": "Allow",
            "Action": [
                "sagemaker:Delete*",
                "sagemaker:Stop*",
                "sagemaker:Update*",
                "sagemaker:Start*",
                "sagemaker:DisassociateTrialComponent",
                "sagemaker:AssociateTrialComponent",
                "sagemaker:BatchPutMetrics"
            ],
            "Resource": "*",
            "Condition": { "StringEquals": { "aws:PrincipalTag/team": "${sagemaker:ResourceTag/team}" } }
        }
    ]
}

Creating and configuring the roles

Creating the Amazon SageMaker Studio user profile

In this step, we add the studiouserid tag when creating Studio user profiles. The steps are slightly different for each authentication type.

IAM users

aws sagemaker create-user-profile --domain-id <domain id> --user-profile-name <unique profile name> --tags Key=studiouserid,Value=<aws user name> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name>

AWS account federation

For AWS account federation, you create a user attribute (studiouserid) in an external IdP with a unique value for each user. The following code shows how to configure the attribute in Okta:

Example below shows how to add “studiouserid” attribute in OKTA. In OKTA’s SIGN ON METHODS screen, configure following SAML 2.0 attributes, as shown in the image below. 

Attribute 1:
Name: https://aws.amazon.com/SAML/Attributes/PrincipalTag:studiouserid 
Value: user.studiouserid

Attribute 2:
Name: https://aws.amazon.com/SAML/Attributes/TransitiveTagKeys
Value: {"studiouserid"}

The following screenshot shows the attributes on the Okta console.

Next, create the user profile using the following command. Use the user attribute value in the preceding step for the studiouserid tag value.

aws sagemaker create-user-profile --domain-id <domain id> --user-profile-name <unique profile name> --tags Key=studiouserid,Value=<user attribute value> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name>

AWS SSO

For instructions on assigning users in AWS SSO, see Onboarding Amazon SageMaker Studio with AWS SSO and Okta Universal Directory.

Update the Studio user profile to include the appropriate execution role that was created for the team that the user belongs to. See the following CLI command:

aws sagemaker update-user-profile --domain-id <domain id> --user-profile-name <user profile name> --user-settings ExecutionRole=arn:aws:iam::<account id>:role/<Team Role Name> --region us-west-2

Validating that only assigned Studio users can access their profiles

Validating that only respective team members can access certain artifacts

In this step, we show how to configure Studio so that members of a given team can’t access artifacts that another team creates.

In our use case, a Team A user creates an experiment and tags that experiment with the team tag. This limits access to this experiment to Team A users only. See the following code:

import sys
!{sys.executable} -m pip install sagemaker
!{sys.executable} -m pip install sagemaker-experiments

import time
import sagemaker
from smexperiments.experiment import Experiment

demo_experiment = Experiment.create(experiment_name = "USERA1TEAMAEXPERIMENT1",
                                    description = "UserA1 experiment",
                                    tags = [{'Key': 'team', 'Value': 'TeamA'}])

If a user who is not in Team A tries to delete the experiment, Studio denies the delete action. See the following code:

#command run from TeamB User Studio Instance
import time
from smexperiments.experiment import Experiment
experiment_to_cleanup = Experiment.load(experiment_name="USERA1TEAMAEXPERIMENT1")
experiment_to_cleanup.delete()

[Client Error]
An error occurred (AccessDeniedException) when calling the DeleteExperiment operation: User: arn:aws:sts:: :<AWS Account ID>::assumed-role/ SageMakerStudioDeveloperTeamBRole/SageMaker is not authorized to perform: sagemaker:DeleteExperiment on resource: arn:aws:sagemaker:us-east-1:<AWS Account ID>:experiment/usera1teamaexperiment1

Conclusion

Try out this solution for isolating resources by teams or groups in Amazon SageMaker Studio. For more information about using ABAC as an authorization strategy, see What is ABAC for AWS?

About the Authors

Rakesh Ramadas is an ISV Solution Architect at Amazon Web Services. His focus areas include AI/ML and Big Data.

Rama Thamman is a Software Development Manager with the AI Platforms team, leading the ML Migrations team.

from AWS Machine Learning Blog https://ift.tt/38vljnT
via A.I .Kung Fu

With Its Own Chips, Apple Aims to Define the Future of PCs

Intel processors are on their way out, replaced by home-grown designs, which will give the Mac maker more control of its destiny.

from Wired https://ift.tt/3eOmobS
via A.I .Kung Fu

Online mortgage lender Better.com has raised ~$200M Series D led by L Catterton according to an internal memo; sources say the round values the company at $4B (Bloomberg)

Bloomberg:
Online mortgage lender Better.com has raised ~$200M Series D led by L Catterton according to an internal memo; sources say the round values the company at $4B — Online mortgage lender Better.com has closed a new funding round led by private equity firm L Catterton, according to an internal memo reviewed by Bloomberg News.

from Techmeme https://ift.tt/3eKpzRP
via A.I .Kung Fu

Strategy Analytics: in Q3, Samsung sold more smartphones in the US than Apple for the first time in three years; Samsung had 33.7% marketshare, Apple had 30.2% (Yonhap News Agency)

Yonhap News Agency:
Strategy Analytics: in Q3, Samsung sold more smartphones in the US than Apple for the first time in three years; Samsung had 33.7% marketshare, Apple had 30.2% — Samsung Electronics Co. sold the largest number of smartphones in the United States in the third quarter of the year …

from Techmeme https://ift.tt/2InrzTO
via A.I .Kung Fu

Two US House representatives who oversee the FCC ask Ajit Pai to abandon "controversial items under consideration", likely referencing changes to Section 230 (Devin Coldewey/TechCrunch)

Devin Coldewey / TechCrunch:
Two US House representatives who oversee the FCC ask Ajit Pai to abandon “controversial items under consideration”, likely referencing changes to Section 230 — Two U.S. Representatives who oversee the FCC have asked the agency to respect the results of the election by abandoning any …

from Techmeme https://ift.tt/38xxfps
via A.I .Kung Fu

Facebook says political content makes up about 6% of what is seen on its platform and says CrowdTangle measures engagement but doesn't predict reach (Sara Fischer/Axios)

Sara Fischer / Axios:
Facebook says political content makes up about 6% of what is seen on its platform and says CrowdTangle measures engagement but doesn't predict reach — Facebook Tuesday said that political content makes up only about 6% of what users actually see on its platform.

from Techmeme https://ift.tt/38wzOYA
via A.I .Kung Fu

Patreon partners with Acast, which will host creators' podcasts to simplify distribution of subscriber-only episodes and give them access to Acast analytics (Ashley Carman/The Verge)

Ashley Carman / The Verge:
Patreon partners with Acast, which will host creators' podcasts to simplify distribution of subscriber-only episodes and give them access to Acast analytics — Private RSS feeds are streamlined — Patreon's newest partnership might entice more podcasters to join its platform.

from Techmeme https://ift.tt/3lifwWA
via A.I .Kung Fu

Monday, November 9, 2020

2021 Land Rover Discovery update focuses on the tech - Roadshow

With a new infotainment system and more ways to connect, the Discovery is smarter -- and a little easier on the eyes, too.

from CNET News https://ift.tt/3eKu8v7
via A.I .Kung Fu

Apple's new Macs could change computers as we know them - CNET

As the insides of computers become more like iPhones, we can expect better battery life, thinner designs and even, maybe, a lower price tag.

from CNET News https://ift.tt/2GJvZnu
via A.I .Kung Fu

Alex Trebek's last Jeopardy episode will air on Christmas day - CNET

Legendary game-show host worked up until Oct. 29.

from CNET News https://ift.tt/3eKjeFV
via A.I .Kung Fu

NASA chief Jim Bridenstine will reportedly step down under Biden administration - CNET

The former Republican congressman reportedly thinks NASA should have a new chief.

from CNET News https://ift.tt/38mNqFY
via A.I .Kung Fu

PS5 launch games: Every PlayStation 5 title you can buy on Thursday - CNET

The PS5 has more than Miles Morales.

from CNET News https://ift.tt/3n0MICm
via A.I .Kung Fu

Get 6 months of Netflix bundled with Chromecast with Google TV streamer for $90 - CNET

The Google Store deal saves you $44, which is like getting the new Chromecast for $6.

from CNET News https://ift.tt/3l7m4XZ
via A.I .Kung Fu

17 of the best TV shows to watch on Amazon Prime Video - CNET

Looking for a great show to watch tonight? Let's round up Amazon's best gems.

from CNET News https://ift.tt/35gHJrg
via A.I .Kung Fu

The PS5's original design was even bigger than the one we got - CNET

How?

from CNET News https://ift.tt/2GIqFRg
via A.I .Kung Fu

Election 2020: Facebook, Twitter and YouTube wrestle with misinformation - CNET

The social media sites have their hands full.

from CNET News https://ift.tt/2I9z9Sf
via A.I .Kung Fu

Netflix is testing a regular, old-fashioned TV channel - CNET

But it would still be for subscribers only.

from CNET News https://ift.tt/35chjGS
via A.I .Kung Fu

Detectives and noxious locks take on bike thieves

The cycling industry is coming up with innovative ways to deter a wave of bike crime.

from BBC News - Technology https://ift.tt/38zEw7U
via A.I .Kung Fu

No, Software Glitches Are Not Affecting Vote Counts

Some Republicans have blamed software glitches for vote-count issues in Michigan and Georgia. The Michigan cases were caused by human error and soon fixed, while Georgia software issues didn’t affect tallies.

from NYT > Technology https://ift.tt/3ljI81x
via A.I .Kung Fu

Facebook Removes Pages Linked to Bannon for Pushing Misinformation

The pages, associated with the Stop the Steal hashtag, had about 2.5 million followers.

from NYT > Technology https://ift.tt/3pgzy5W
via A.I .Kung Fu

What to expect from Apple's "One More Thing" event: first Apple Silicon powered Macs, a macOS Big Sur release date, and potentially AirTags, over-ear headphones (Jay Peters/The Verge)

Jay Peters / The Verge:
What to expect from Apple's “One More Thing” event: first Apple Silicon powered Macs, a macOS Big Sur release date, and potentially AirTags, over-ear headphones — It seems likely Apple will reveal the first computers powered by its custom silicon

from Techmeme https://ift.tt/2U9YJsT
via A.I .Kung Fu

EU tightens rules on surveillance tech, forcing companies selling spyware, facial recognition, and tech with military uses to get a license, be more transparent (Patrick Howell O'Neill/MIT Technology ...)

Patrick Howell O'Neill / MIT Technology Review:
EU tightens rules on surveillance tech, forcing companies selling spyware, facial recognition, and tech with military uses to get a license, be more transparent — The goal is to make sales of technologies like spyware and facial recognition more transparent in Europe first, and then worldwide.

from Techmeme https://ift.tt/3pdYfjC
via A.I .Kung Fu

Enthusiast Gaming will be the first game media and influencer company on Nasdaq

Luminosity Gaming owns the Overwatch League team Vancouver Titans.

Enthusiast Gaming, an esports and gaming media firm, announced that it will become a publicly traded company on the Nasdaq stock market.Read More

from VentureBeat https://ift.tt/32pit03
via A.I .Kung Fu

You can stop panicking about the PlayStation 5 and Xbox Series X

This is a real picture of the PlayStation 5.

The PlayStation 5 and Xbox Series X are almost here, so it's time to stop worrying so much about every tiny detail.Read More

from VentureBeat https://ift.tt/36jim7s
via A.I .Kung Fu

Logo alert! Fiat Chrysler and Groupe PSA unveil new logo - Roadshow

This combined multinational entity will be called Stellantis. No, that's not the name of some anti-itch cream or a singles resort in the Caribbean.

from CNET News https://ift.tt/3km36M8
via A.I .Kung Fu

Best Buy Black Friday 2020 ad: See everything going on sale starting Nov. 22 - CNET

Looking for Best Buy's Black Friday ad circular? We have a scan of the whole ad, plus the best ads to keep an eye on.

from CNET News https://ift.tt/3k8G9vG
via A.I .Kung Fu

Facebook removed seven pages, with over 2.45 million followers, tied to Steve Bannon for pushing misinformation about voter fraud and election results (Elizabeth Dwoskin/Washington Post)

Elizabeth Dwoskin / Washington Post:
Facebook removed seven pages, with over 2.45 million followers, tied to Steve Bannon for pushing misinformation about voter fraud and election results — The pages, which pushed the ‘Stop the Steal’ hashtag and other misleading messages, were removed over the weekend while Bannon's account was frozen

from Techmeme https://ift.tt/3kdoB1p
via A.I .Kung Fu

Apple Silicon Macs will run iOS apps but some developers, including Facebook, Google, and the developers of Candy Crush and Among Us, have already opted out (Filipe Espósito/9to5Mac)

Filipe Espósito / 9to5Mac:
Apple Silicon Macs will run iOS apps but some developers, including Facebook, Google, and the developers of Candy Crush and Among Us, have already opted out — Apple will hold another special event tomorrow, and we expect to see the first Mac with Apple Silicon chips.

from Techmeme https://ift.tt/38qibts
via A.I .Kung Fu

Facebook and Google have been blocking political ads since Election Day, which Democrats say is hurting fundraising in the lead up to Georgia's upcoming runoffs (Issie Lapowsky/Protocol)

Issie Lapowsky / Protocol:
Facebook and Google have been blocking political ads since Election Day, which Democrats say is hurting fundraising in the lead up to Georgia's upcoming runoffs — The fate of the United States Senate will be determined by two Georgia runoffs scheduled for less than two months from now …

from Techmeme https://ift.tt/32qXBWk
via A.I .Kung Fu

What Makes Sand Soft?

Understanding how grains flow is vital for everything from landslide prediction to agricultural processing, and scientists aren’t very good at it.

from NYT > Technology https://ift.tt/2U78isz
via A.I .Kung Fu

Tim Berners Lee's Inrupt startup releases an enterprise version of the Solid privacy platform, which allows organizations to build privacy-focused apps (Ron Miller/TechCrunch)

Ron Miller / TechCrunch:
Tim Berners Lee's Inrupt startup releases an enterprise version of the Solid privacy platform, which allows organizations to build privacy-focused apps — Inrupt, the startup from World Wide Web founder Tim Berners-Lee, announced an enterprise version of the Solid privacy platform today …

from Techmeme https://ift.tt/3pay1P0
via A.I .Kung Fu

Trump will lose special Twitter protections when Biden takes office

U.S President Donald Trump returns to the White House after news media declared Democratic U.S. presidential nominee Joe Biden to be the winner of the 2020 U.S. presidential election, in Washington, U.S., November 7, 2020.

U.S. President Donald Trump will be subject to the same Twitter rules as any other user when President-elect Joe Biden takes office.Read More

from VentureBeat https://ift.tt/2JTDFFb
via A.I .Kung Fu

What it takes to pitch a game

One of the most difficult parts of independent game development is getting funding for your project. Here's some tips for doing so.Read More

from VentureBeat https://ift.tt/357slxe
via A.I .Kung Fu

Eve Online video game helps scientists understand Covid-19

Gamers have completed 47 million mini-game tasks amounting to 36 years categorising cells.

from BBC News - Technology https://ift.tt/35b7ngK
via A.I .Kung Fu

Indian grocery delivery service Bigbasket confirms it suffered a data breach in which attackers stole user email ids, mobile phone numbers, and full addresses (Saritha Rai/Bloomberg)

Saritha Rai / Bloomberg:
Indian grocery delivery service Bigbasket confirms it suffered a data breach in which attackers stole user email ids, mobile phone numbers, and full addresses — - Attackers offer to sell data on millions of users on dark web — Cybercrimes on the rise as Covid forces people to shop online

from Techmeme https://ift.tt/2U6LEAz
via A.I .Kung Fu

Sunday, November 8, 2020

Tim Berners-Lee startup launches privacy-focused service to secure your data - CNET

Inrupt wants you to control who can see your data.

from CNET News https://ift.tt/36csNtm
via A.I .Kung Fu

Free speech Twitter alternative Parler becomes top downloaded app as conservatives rally support to leave Twitter and Facebook (Emma Colton/Washington Examiner)

Emma Colton / Washington Examiner:
Free speech Twitter alternative Parler becomes top downloaded app as conservatives rally support to leave Twitter and Facebook — Social media platform Parler jumped to the top downloaded app this weekend, as conservatives rally support to leave Facebook and Twitter over censorship.

from Techmeme https://ift.tt/32qH5VY
via A.I .Kung Fu

Apple suspends new business with key supplier Pegatron after discovering violations of labor rules related to a student worker program (Bloomberg)

Bloomberg:
Apple suspends new business with key supplier Pegatron after discovering violations of labor rules related to a student worker program — - Apple says Pegatron violated rules for student worker program — Company says new business paused until corrective action taken

from Techmeme https://ift.tt/3eIRlOC
via A.I .Kung Fu

Alan Turing: Stolen items to be returned to UK from US after decades

A collection of items belonging to the Bletchley Park code-breaker were stolen from Dorset in 1984.

from BBC News - Technology https://ift.tt/3n5hLwH
via A.I .Kung Fu

Translate

Tuesday, November 10, 2020

Authentication

Data science user personas

Solution overview

Applying your policy to the admin user

Assigning the policy to Studio users

Creating roles for the teams

Creating the policies

Policy 1: Amazon SageMaker read-only access

Policy 2: Amazon SageMaker access for supporting services

Policy 3: Amazon SageMaker Studio developer access

Creating and configuring the roles

Creating the Amazon SageMaker Studio user profile

IAM users

AWS account federation

AWS SSO

Validating that only assigned Studio users can access their profiles

Validating that only respective team members can access certain artifacts

Conclusion

About the Authors

Authentication

Data science user personas

Solution overview

Applying your policy to the admin user

Assigning the policy to Studio users

Creating roles for the teams

Creating the policies

Policy 1: Amazon SageMaker read-only access

Policy 2: Amazon SageMaker access for supporting services

Policy 3: Amazon SageMaker Studio developer access

Creating and configuring the roles

Creating the Amazon SageMaker Studio user profile

IAM users

AWS account federation

AWS SSO

Validating that only assigned Studio users can access their profiles

Validating that only respective team members can access certain artifacts

Conclusion

About the Authors

Monday, November 9, 2020

Sunday, November 8, 2020

Blog Archive

Featured Post