Infrastructure security in the Amazon Chime SDK - Amazon Chime SDK

Infrastructure security in the Amazon Chime SDK

As a managed service, the Amazon Chime SDK is protected by the AWS global network security procedures that are described in the Amazon Web Services: Overview of Security Processes white paper.

For an overview of security in the Amazon Chime Software Development Kit (SDK), see Understanding Security in the Amazon Chime Application and SDK blog post. The post includes information on how AWS protects your data, plus the various meeting security features.

You use AWS published API calls to access the Amazon Chime SDK through the network. Clients must support Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern systems such as Java 7 and later support these modes.

Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary security credentials to sign requests.