Submit IDT usage metrics
If you provide AWS credentials with required permissions, AWS IoT Device Tester collects and submits usage metrics to AWS. This is an opt-in feature and is used to improve IDT functionality. IDT collects information such as the following:
-
The AWS account ID used to run IDT
-
The IDT CLI commands used to run tests
-
The test suite that are run
-
The test suites in the
<device-tester-extract-location>
folder -
The number of devices configured in the device pool
-
Test case names and run times
-
Test result information, such as whether tests passed, failed, encountered errors, or were skipped
-
Product features tested
-
IDT exit behavior, such as unexpected or early exits
All of the information that IDT sends is also logged to a
metrics.log
file in the
folder. You can view the log file to see the information that was collected during a
test run. This file is generated only if you choose to collect usage metrics. <device-tester-extract-location>
/results/<execution-id>
/
To disable metrics collection, you do not need to take additional action. Simply
do not store your AWS credentials, and if you do have stored AWS credentials, do
not configure the config.json
file to access them.
Sign up for an AWS account
If you do not have an AWS account, complete the following steps to create one.
To sign up for an AWS account
Open https://portal.aws.amazon.com/billing/signup
. 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.
AWS sends you a confirmation email after the sign-up process is
complete. At any time, you can view your current account activity and manage your account by
going to https://aws.amazon.com/
Create a user with administrative access
After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks.
Secure your AWS account root user
-
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.
-
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
-
Enable IAM Identity Center.
For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide.
-
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
-
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.
-
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.
To provide access, add permissions to your users, groups, or roles:
-
Users and groups in AWS IAM Identity Center:
Create a permission set. Follow the instructions in Create a permission set in the AWS IAM Identity Center User Guide.
-
Users managed in IAM through an identity provider:
Create a role for identity federation. Follow the instructions in Creating a role for a third-party identity provider (federation) in the IAM User Guide.
-
IAM users:
-
Create a role that your user can assume. Follow the instructions in Creating a role for an IAM user in the IAM User Guide.
-
(Not recommended) Attach a policy directly to a user or add a user to a user group. Follow the instructions in Adding permissions to a user (console) in the IAM User Guide.
-
Provide AWS credentials to IDT
To allow IDT to access your AWS credentials and submit metrics to AWS, do the following:
-
Store the AWS credentials for your IAM user as environment variables or in a credentials file:
-
To use environment variables, run the following command:
AWS_ACCESS_KEY_ID=
access-key
AWS_SECRET_ACCESS_KEY=secret-access-key
-
To use the credentials file, add the following information to the
.aws/credentials file:
[profile-name] aws_access_key_id=
access-key
aws_secret_access_key=secret-access-key
-
-
Configure the
auth
section of theconfig.json
file. For more information, see (Optional) Configure config.json.