Data protection in AWS IoT RoboRunner - AWS IoT RoboRunner

Data protection in AWS IoT RoboRunner

The AWS shared responsibility model applies to data protection in AWS IoT RoboRunner. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. This content includes the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.

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). That way 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. We recommend TLS 1.2 or later.

  • 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.

  • If you require FIPS 140-2 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-2.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form fields such as a Name field. This includes when you work with AWS IoT RoboRunner or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

Encryption at rest

Data encryption refers to protecting data while in-transit (as it travels to and from AWS IoT RoboRunner), and at rest (while it is stored in AWS services). You can protect data in transit using Transport Layer Security (TLS) or at rest using client-side encryption.

AWS IoT RoboRunner stores data in other AWS services that encrypt data at rest by default. Encryption at rest integrates with AWS Key Management Service (AWS KMS) for managing the encryption key that is used to encrypt your service field values and aggregate values in AWS IoT RoboRunner.

AWS IoT RoboRunner encrypts all customer data at rest using encryption keys stored in AWS KMS. Organizational policies, industry or government regulations, and compliance requirements often require the use of encryption at rest to increase the data security of your applications. AWS IoT RoboRunner uses the service-owned KMS key to encrypt customer data at no additional charge to you.

How it works

AWS IoT RoboRunner manages AWS KMS encryption keys on your behalf and uses it to encrypt the data stored in your account. You can't view, manage, or use the AWS IoT RoboRunner encryption keys, or audit their use. However, you don't need to do any work or change any programs to protect the keys that encrypt your data.

Again, you're not charged a monthly fee or a usage fee if you use AWS-owned keys, and they don't count against AWS KMS quotas for your account.

Encryption in transit

When you manage AWS IoT RoboRunner resources with the AWS Management Console, AWS SDK, or the AWS IoT RoboRunner API, all communication is encrypted with Transport Layer Security (TLS), so it is secure by default.

For a complete list of API endpoints, see Regions and endpoints in the AWS General Reference.