You may be curious about the number of hours you've spent training and evaluating models.
To view sponsored hours usage
• In Your racer profile page, see Sponsored hours usage for total hours used.
Data Protection
Security for AWS DeepRacer
To use AWS DeepRacer to train and evaluate reinforcement learning, your AWS account must have appropriate security permissions to access dependent AWS resources, including VPC to run training jobs and an Amazon S3 bucket to store trained model artifacts, etc.
The AWS DeepRacer console provides a 1-click solution for you to have the required security settings set up for the dependent services. This section documents the AWS services AWS DeepRacer depends as well as the the IAM roles and policy defining the required permissions to access the dependent services.
Topics
• Data Protection in AWS DeepRacer (p. 188)
• AWS DeepRacer-Dependent AWS Services (p. 189)
• Required IAM Roles for AWS DeepRacer to Call Dependent AWS Services (p. 190)
• Identity and Access Management for AWS DeepRacer (p. 191)
Data Protection in AWS DeepRacer
AWS DeepRacer conforms to the AWS shared responsibility model, which includes regulations and guidelines for data protection. AWS is responsible for protecting the global infrastructure that runs all the AWS services. AWS maintains control over data hosted on this infrastructure, including the security configuration controls for handling customer content and personal data. AWS customers and APN partners, acting either as data controllers or data processors, are responsible for any personal data that they put in the AWS Cloud.
For data protection purposes, we recommend that you protect AWS account credentials and set up individual user accounts with AWS Identity and Access Management (IAM), so that each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:
• Use multi-factor authentication (MFA) with each account.
• Use SSL/TLS to communicate with AWS resources.
• Set up API and user activity logging with AWS CloudTrail.
• Use AWS encryption solutions, along with all default security controls within AWS services.
• Use advanced managed security services such as Amazon Macie, which assists in discovering and securing personal data that is stored in Amazon S3.
We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a Name field. This includes when you work with AWS DeepRacer or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into AWS DeepRacer or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server.
For more information about data protection, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.
AWS DeepRacer-Dependent Services
AWS DeepRacer-Dependent AWS Services
AWS DeepRacer uses the following AWS services to manage required resources:
Amazon Simple Storage Service
To store trained model artifacts in an Amazon S3 bucket.
AWS Lambda
To create and run the reward functions.
AWS CloudFormation
To create training jobs for AWS DeepRacer models.
SageMaker
To train the AWS DeepRacer models.
AWS RoboMaker
To simulate an environment for both training and evaluation.
The dependent AWS Lambda, AWS CloudFormation, SageMaker, and AWS RoboMaker in turn use other AWS services including Amazon CloudWatch and Amazon CloudWatch Logs.
The following table shows AWS services used by AWS DeepRacer, directly or indirectly.
AWS Services that AWS DeepRacer uses directly or indirectly
AWS service principal Comments
application-autoscaling • Indirectly called by SageMaker to automatically scale its operations.
cloudformation • Directly called by AWS DeepRacer to create
account resources.
cloudwatch • Directly called by AWS DeepRacer to log its
operations.
• Indirectly called by AWS RoboMaker to log its operations.
• Indirectly called by SageMaker to log its operations.
ec2 • Indirectly called by AWS CloudFormation and
SageMaker to create and run training jobs.
ecr • Indirectly called by AWS RoboMaker to work
with Amazon Elastic Container Registry.
kinesisvideo • Directly called by AWS DeepRacer to view
cached training streams.
• Indirectly called by AWS RoboMaker to cache training streams.
lambda • Directly called by AWS DeepRacer to create and
run the reward functions.
Required IAM Roles
AWS service principal Comments
logs • Directly called by AWS DeepRacer to log its
operations.
• Indirectly called by AWS Lambda to log its operations.
• Indirectly called by AWS RoboMaker to log its operations.
robomaker • Directly called by AWS DeepRacer to render a
virtual reinforcement learning environment in a simulation.
s3 • Indirectly called by AWS RoboMaker to list a
bucket beginning with 'deepracer' and to read objects in the bucket, or write objects to the bucket.
• Indirectly called by SageMaker to perform SageMaker-specific storage operations.
• Directly called by AWS DeepRacer to create, list, and delete buckets that have names starting with "deepracer." Also called to download objects from the buckets, upload objects to the buckets, or delete objects from the buckets.
sagemaker • Directly called by AWS DeepRacer to train
reinforcement learning models.
To use AWS DeepRacer to call these services, you must have appropriate IAM roles with required policies attached to them. Learn the details about these policies and roles in Required IAM Roles for AWS DeepRacer to Call Dependent AWS Services (p. 190).
Required IAM Roles for AWS DeepRacer to Call Dependent AWS Services
Before you create a model, use the AWS DeepRacer console to set up resources for your account. As you do this, the AWS DeepRacer console creates the following IAM roles:
AWSDeepRacerServiceRole
Allows AWS DeepRacer to create required resources and call AWS services on your behalf.
AWSDeepRacerSageMakerAccessRole
Allows Amazon SageMaker to create required resources and call AWS services on your behalf.
AWSDeepRacerRoboMakerAccessRole
Allows AWS RoboMaker to create required resources and call AWS services on your behalf.
AWSDeepRacerLambdaAccessRole
Allows AWS Lambda functions to call AWS services on your behalf.
AWSDeepRacerCloudFormationAccessRole
Allows AWS CloudFormation to create and manage AWS stacks and resources on your behalf.
Identity and Access Management
Follow the links to view detailed access permissions in the AWS IAM console.
Identity and Access Management for AWS DeepRacer
AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be authenticated (signed in) and authorized (have permissions) to use DeepRacer resources. IAM is an AWS service that you can use with no additional charge.
Topics
• Audience (p. 191)
• Authenticating With Identities (p. 191)
• Managing Access Using Policies (p. 193)
• How AWS DeepRacer works with IAM (p. 195)
• Identity-based policy examples for AWS DeepRacer (p. 199)
• AWS managed policies for AWS DeepRacer (p. 201)
• Cross-service confused deputy prevention (p. 204)
• Troubleshooting AWS DeepRacer identity and access (p. 205)
Audience
How you use AWS Identity and Access Management (IAM) differs, depending on the work that you do in DeepRacer.
Service user – If you use the DeepRacer service to do your job, then your administrator provides you with the credentials and permissions that you need. As you use more DeepRacer features to do your work, you might need additional permissions. Understanding how access is managed can help you request the right permissions from your administrator. If you cannot access a feature in DeepRacer, see Troubleshooting AWS DeepRacer identity and access (p. 205).
Service administrator – If you're in charge of DeepRacer resources at your company, you probably have full access to DeepRacer. It's your job to determine which DeepRacer features and resources your employees should access. You must then submit requests to your IAM administrator to change the permissions of your service users. Review the information on this page to understand the basic concepts of IAM. To learn more about how your company can use IAM with DeepRacer, see How AWS DeepRacer works with IAM (p. 195).
IAM administrator – If you're an IAM administrator, you might want to learn details about how you can write policies to manage access to DeepRacer. To view example DeepRacer identity-based policies that you can use in IAM, see Identity-based policy examples for AWS DeepRacer (p. 199).
Authenticating With Identities
Authentication is how you sign in to AWS using your identity credentials. For more information about signing in using the AWS Management Console, see Signing in to the AWS Management Console as an IAM user or root user in the IAM User Guide.
You must be authenticated (signed in to AWS) as the AWS account root user, an IAM user, or by assuming an IAM role. You can also use your company's single sign-on authentication or even sign in using Google or Facebook. In these cases, your administrator previously set up identity federation using IAM roles.
When you access AWS using credentials from another company, you are assuming a role indirectly.
Authenticating With Identities
To sign in directly to the AWS Management Console, use your password with your root user email address or your IAM user name. You can access AWS programmatically using your root user or IAM users access keys. AWS provides SDK and command line tools to cryptographically sign your request using your credentials. If you don't use AWS tools, you must sign the request yourself. Do this using Signature Version 4, a protocol for authenticating inbound API requests. For more information about authenticating requests, see Signature Version 4 signing process in the AWS General Reference.
Regardless of the authentication method that you use, you might also be required to provide additional security information. For example, AWS recommends that you use multi-factor authentication (MFA) to increase the security of your account. To learn more, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.
AWS account root user
When you first create an AWS account, you begin with a single sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and is accessed by signing in with the email address and password that you used to create the account. We strongly recommend that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks.
IAM Users and Groups
An IAM user is an identity within your AWS account that has specific permissions for a single person or application. An IAM user can have long-term credentials such as a user name and password or a set of access keys. To learn how to generate access keys, see Managing access keys for IAM users in the IAM User Guide. When you generate access keys for an IAM user, make sure you view and securely save the key pair. You cannot recover the secret access key in the future. Instead, you must generate a new access key pair.
An IAM group is an identity that specifies a collection of IAM users. You can't sign in as a group. You can use groups to specify permissions for multiple users at a time. Groups make permissions easier to manage for large sets of users. For example, you could have a group named IAMAdmins and give that group permissions to administer IAM resources.
Users are different from roles. A user is uniquely associated with one person or application, but a role is intended to be assumable by anyone who needs it. Users have permanent long-term credentials, but roles provide temporary credentials. To learn more, see When to create an IAM user (instead of a role) in the IAM User Guide.
IAM Roles
An IAM role is an identity within your AWS account that has specific permissions. It is similar to an IAM user, but is not associated with a specific person. You can temporarily assume an IAM role in the AWS Management Console by switching roles. You can assume a role by calling an AWS CLI or AWS API operation or by using a custom URL. For more information about methods for using roles, see Using IAM roles in the IAM User Guide.
IAM roles with temporary credentials are useful in the following situations:
• Temporary IAM user permissions – An IAM user can assume an IAM role to temporarily take on different permissions for a specific task.
• Federated user access – Instead of creating an IAM user, you can use existing identities from AWS Directory Service, your enterprise user directory, or a web identity provider. These are known as federated users. AWS assigns a role to a federated user when access is requested through an identity provider. For more information about federated users, see Federated users and roles in the IAM User Guide.
Managing Access Using Policies
• Cross-account access – You can use an IAM role to allow someone (a trusted principal) in a different account to access resources in your account. Roles are the primary way to grant cross-account access.
However, with some AWS services, you can attach a policy directly to a resource (instead of using a role as a proxy). To learn the difference between roles and resource-based policies for cross-account access, see How IAM roles differ from resource-based policies in the IAM User Guide.
• Cross-service access – Some AWS services use features in other AWS services. For example, when you make a call in a service, it's common for that service to run applications in Amazon EC2 or store objects in Amazon S3. A service might do this using the calling principal's permissions, using a service role, or using a service-linked role.
• Principal permissions – When you use an IAM user or role to perform actions in AWS, you are considered a principal. Policies grant permissions to a principal. When you use some services, you might perform an action that then triggers another action in a different service. In this case, you must have permissions to perform both actions. To see whether an action requires additional dependent actions in a policy, see Actions, resources, and condition keys for AWS DeepRacer in the Service Authorization Reference.
• Service role – A service role is an IAM role that a service assumes to perform actions on your behalf.
An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Creating a role to delegate permissions to an AWS service in the IAM User Guide.
• Service-linked role – A service-linked role is a type of service role that is linked to an AWS service.
The service can assume the role to perform an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.
• Applications running on Amazon EC2 – You can use an IAM role to manage temporary credentials for applications that are running on an EC2 instance and making AWS CLI or AWS API requests.
This is preferable to storing access keys within the EC2 instance. To assign an AWS role to an EC2 instance and make it available to all of its applications, you create an instance profile that is attached to the instance. An instance profile contains the role and enables programs that are running on the EC2 instance to get temporary credentials. For more information, see Using an IAM role to grant permissions to applications running on Amazon EC2 instances in the IAM User Guide.
To learn whether to use IAM roles or IAM users, see When to create an IAM role (instead of a user) in the IAM User Guide.
Managing Access Using Policies
You control access in AWS by creating policies and attaching them to IAM identities or AWS resources. A policy is an object in AWS that, when associated with an identity or resource, defines their permissions.
You can sign in as the root user or an IAM user, or you can assume an IAM role. When you then make a request, AWS evaluates the related identity-based or resource-based policies. Permissions in the policies determine whether the request is allowed or denied. Most policies are stored in AWS as JSON documents. For more information about the structure and contents of JSON policy documents, see Overview of JSON policies in the IAM User Guide.
Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.
Every IAM entity (user or role) starts with no permissions. In other words, by default, users can do nothing, not even change their own password. To give a user permission to do something, an administrator must attach a permissions policy to a user. Or the administrator can add the user to a group that has the intended permissions. When an administrator gives permissions to a group, all users in that group are granted those permissions.
IAM policies define permissions for an action regardless of the method that you use to perform the operation. For example, suppose that you have a policy that allows the iam:GetRole action. A user with that policy can get role information from the AWS Management Console, the AWS CLI, or the AWS API.
Managing Access Using Policies
Identity-Based Policies
Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Creating IAM policies in the IAM User Guide.
Identity-based policies can be further categorized as inline policies or managed policies. Inline policies are embedded directly into a single user, group, or role. Managed policies are standalone policies that you can attach to multiple users, groups, and roles in your AWS account. Managed policies include AWS managed policies and customer managed policies. To learn how to choose between a managed policy or an inline policy, see Choosing between managed policies and inline policies in the IAM User Guide.
Resource-Based Policies
Resource-based policies are JSON policy documents that you attach to a resource. Examples of based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must specify a principal in a resource-based policy.
Principals can include accounts, users, roles, federated users, or AWS services.
Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.
Access Control Lists (ACLs)
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy