Cloud security at AWS is the highest priority. As an AWS customer, you benefit from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations.
Security is a shared responsibility between AWS and you. The shared responsibility
model
-
Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the effectiveness of our security as part of the AWS Compliance Programs
. To learn about the compliance programs that apply to the Amazon Chime SDK, see AWS Services in Scope by Compliance Program . -
Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations.
This documentation helps you understand how to apply the shared responsibility model when using the Amazon Chime SDK. The following topics show you how to configure the Amazon Chime SDK to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your Amazon Chime SDK resources.
Topics
Amazon Chime SDK resource-based policies
The Amazon Chime SDK supports resource-based policies for the following resource types.
Authorization based on Amazon Chime SDK
tags
The Amazon Chime SDK supports tagging for these resource types.
Amazon Chime SDK IAM roles
An IAM role is an entity within your AWS account that has specific permissions.
Using temporary credentials with the Amazon Chime SDK
You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling AWS STS API operations such as AssumeRole or GetFederationToken.
The Amazon Chime SDK supports using temporary credentials.
Service-linked roles
Service-linked roles allow AWS services to access resources in other services that complete actions on your behalf. Service-linked roles appear in your IAM account, and the services own the roles. An IAM administrator can view but not edit the permissions for service-linked roles.
The Amazon Chime SDK supports service-linked roles. For details about creating or managing those roles, see Using service-linked roles for Amazon Chime SDK.
Service roles
This feature allows a service to assume a service role on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.
The Amazon Chime SDK does not support service roles.
