Setting Up

To sign up for an AWS account

1. Open https://portal.aws.amazon.com/billing/signup.

2. Follow the online instructions.

   Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.

   When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access.

Secure your AWS account root user

1. Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password.

   For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide.

2. Turn on multi-factor authentication (MFA) for your root user.

   For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide.

Create a user with administrative access

1. Enable IAM Identity Center.

   For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide.

2. In IAM Identity Center, grant administrative access to a user.

   For a tutorial about using the IAM Identity Center directory as your identity source, see Configure user access with the default IAM Identity Center directory in the AWS IAM Identity Center User Guide.

Sign in as the user with administrative access

• To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user.

  For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide.

Assign access to additional users

1. In IAM Identity Center, create a permission set that follows the best practice of applying least-privilege permissions.

   For instructions, see Create a permission set in the AWS IAM Identity Center User Guide.

2. Assign users to a group, and then assign single sign-on access to the group.

   For instructions, see Add groups in the AWS IAM Identity Center User Guide.

1. Create an IAM role for Amazon SageMaker.

   1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

   2. In the navigation pane of the IAM console, choose Roles, and then choose Create role.

   3. For Select type of trusted entity, choose AWS service.

   4. Choose the service that you want to allow to assume this role. In this case, choose SageMaker. Then choose Next: Permissions.

      • This automatically creates an IAM policy that grants access to related services such as Amazon S3, Amazon ECR, and CloudWatch Logs.

   5. Choose Next: Tags.

   6. (Optional) Add metadata to the role by attaching tags as key–value pairs. For more information about using tags in IAM, see Tagging IAM resources.

   7. Choose Next: Review.

   8. Type in a Role name.

   9. If possible, type a role name or role name suffix. Role names must be unique within your AWS account. They are not distinguished by case. For example, you cannot create roles named both PRODROLE and prodrole. Because other AWS resources might reference the role, you cannot edit the name of the role after it has been created.

   10. (Optional) For Role description, type a description for the new role.

   11. Review the role and then choose Create role.

       Note the SageMaker Role ARN, which you use to create a compilation job with SageMaker Neo and a packaging job with Edge Manager. To find out the role ARN using the console, do the following:

       1. Go to the IAMconsole: https://console.aws.amazon.com/iam/

       2. Select Roles.

       3. Search for the role you just created by typing in the name of the role in the search field.

       4. Select the role.

       5. The role ARN is at the top of the Summary page.

2. Create an IAM role for AWS IoT.

   The AWS IoT IAM role you create is used to authorize your thing objects. You also use the IAM role ARN to create and register device fleets with a SageMaker client object.

   Configure an IAM role in your AWS account for the credentials provider to assume on behalf of the devices in your device fleet. Then, attach a policy to authorize your devices to interact with AWS IoT services.

   Create a role for AWS IoT either programmatically or with the IAM console, similar to what you did when you created a role for SageMaker.

   1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

   2. In the navigation pane of the IAM console, choose Roles, and then choose Create role.

   3. For Select type of trusted entity, choose AWS service.

   4. Choose the service that you want to allow to assume this role. In this case, choose IoT. Select IoT as the Use Case.

   5. Choose Next: Permissions.

   6. Choose Next: Tags.

   7. (Optional) Add metadata to the role by attaching tags as key–value pairs. For more information about using tags in IAM, see Tagging IAM resources.

   8. Choose Next: Review.

   9. Type in a Role name. The role name must start with SageMaker.

   10. (Optional) For Role description, type a description for the new role.

   11. Review the role and then choose Create role.

   12. Once the role is created, choose Roles in the IAM console. Search for the role you created by typing in role name in the Search field.

   13. Choose your role.

   14. Next, choose Attach Policies.

   15. Search for AmazonSageMakerEdgeDeviceFleetPolicy in the Search field. Select AmazonSageMakerEdgeDeviceFleetPolicy.

   16. Choose Attach policy.

   17. Add the following policy statement to the trust relationship:

       {
         "Version": "2012-10-17",
         "Statement": [
             {
               "Effect": "Allow",
               "Principal": {"Service": "credentials.iot.amazonaws.com"},
               "Action": "sts:AssumeRole"
             },
             {
               "Effect": "Allow",
               "Principal": {"Service": "sagemaker.amazonaws.com"},
               "Action": "sts:AssumeRole"
             }
         ]
       }

       A trust policy is a JSON policy document in which you define the principals that you trust to assume the role. For more information about trust policies, see Roles terms and concepts.

   18. Note the AWS IoT role ARN. You use the AWS IoT Role ARN to create and register the device fleet. To find the IAM role ARN with the console:

       1. Go to the IAM console: https://console.aws.amazon.com/iam/

       2. Choose Roles.

       3. Search for the role you created by typing in the name of the role in the Search field.

       4. Select the role.

       5. The role ARN is on the Summary page.

3. Create an Amazon S3 bucket.

   SageMaker Neo and Edge Manager access your pre-compiled model and compiled model from an Amazon S3 bucket. Edge Manager also stores sample data from your device fleet in Amazon S3.

   1. Open the Amazon S3 console at https://console.aws.amazon.com/s3/.

   2. Choose Create bucket.

   3. In Bucket name, enter a name for your bucket.

   4. In Region, choose the AWS Region where you want the bucket to reside.

   5. In Bucket settings for Block Public Access, choose the settings that you want to apply to the bucket.

   6. Choose Create bucket.

   For more information about creating Amazon S3 buckets, see Getting started with Amazon S3.