Using AppKeys and TenantIDs for Amazon Chime SDK
You can use AppKeys and TenantIDs to limit access from a network to specific applications' Amazon Chime SDK WebRTC media sessions.
Developers use the Amazon Chime SDK to create applications that send and receive real-time video over
UDP. Application users require UDP access to the CHIME_MEETINGS subnet.
Organizations (network owners) can use AppKeys and TenantIDs to limit access from their network
to only a specific application's WebRTC media sessions.
Example 1: Using AppKeys
If App-A and App-B use the Amazon Chime SDK, an organization can allow App-A to access the WebRTC media sessions from their network, but block App-B and any other applications that use the Amazon Chime SDK. Organizations can do that with App-A's AppKey and an HTTPS proxy. For more information, refer to Limiting access to a specific application, later in this topic.
Example 2: Using AppKeys and TenantIDs
If App-A is publicly available and used by many customers, an organization may want to allow App-A to access WebRTC media sessions from their network only when their users are part of the session, and block access to all other App-A sessions. Organizations can do this by using the application's AppKey, the organization's TenantID, and an HTTPS proxy. For more information, refer to Limiting access to a specific tenant, later in this topic.
To use AppKeys and TenantIDs, you must have an HTTPS proxy server that allows adding HTTPS headers to a request. The following diagram shows how AppKeys and TenantIDs work.
In the image, App-A has tenants A-1 and A-2, and App-B has tenants B-1 and B-2. In this case, the AppKey only allows App-A to connect to the WebRTC media session, and the tenant ID only admits Tenant A-1 to the session.
Topics
Limiting access to a specific application
An AppKey is a consistent, unique 256-bit value that Amazon Chime creates for each AWS account. If you don't have an AppKey, you can request one from Amazon Support. If you have multiple AWS accounts, you can request a common AppKey for all your accounts.
Note
You can safely share your AppKeys publicly and enable other organizations to limit access from their networks.
The Amazon Chime SDK automatically associates each WebRTC media sessions with an AppKey based on the AWS account ID used to create the session. To limit access from your network to specific applications, do the following:
-
Route all outbound requests to the
CHIME_MEETINGSsubnet through an HTTPS proxy server. -
Configure the proxy server to add the following header to all outbound requests to the
CHIME_MEETINGSsubnet:X-Amzn-Chime-App-Keys:comma-separated list of allowed AppKeys.For example,
X-Amzn-Chime-App-Keys:allows the apps associated with those AppKeys to access the subnet.AppKey-A,AppKey-B,AppKey-C
The Amazon Chime SDK inspects inbound WebRTC media session connections for the
X-Amzn-Chime-App-Keys header and applies the following logic:
-
If the
X-Amzn-Chime-App-Keysheader is present and includes the session's AppKey, accept the connection. -
If the
X-Amzn-Chime-App-Keysheader is present but does not include the session's AppKey, reject the connection with a 403 error. -
If the
X-Amzn-Chime-App-Keysheader is not present, accept the connection. If users can access the application from outside the organization's network, they can also access the session.
Limiting access to a specific tenant
A TenantID is an opaque identifier created by developers. Remember the following about TenantIDs:
-
TenantIDs are not guaranteed to be unique between applications, so you must specify an AppKey for each TenantID list.
-
TenantIDs are case senstitive. Enter them exactly as prescribed by the developer.
-
An organization can limit access to multiple applications, but only specify TenantIDs for some of those applications. Applications without TenantIDs can connect to all WebRTC media sessions.
To associate a media session with TenantIDs, a developer must first add the
TenantIds property and a list of TenantIDs to a CreateMeeting or CreateMeetingWithAttendees request.
For example:
CreateMeeting(..., TenantIds : [ tenantId1, tenantId2 ] )
To limit access from an organization's network to their WebRTC media session in specific applications, do the following:
-
Follow the steps in Limiting access to a specific application.
-
Configure the HTTPS proxy server to add an
X-Amzn-Chime-Tenantsheader on outbound connections. Include a list of AppKeys and TenantIDs, delimited as shown in this example:X-Amzn-Chime-Tenants:AppKey-A:tenantId-A-1,tenantId-A-2;AppKey-B:tenantId-B-1,tenantId-B-2
The Amazon Chime SDK inspects inbound WebRTC media session connections for the
X-Amzn-Chime-Tenants header and applies the following logic:
-
If the header includes the session's
AppKey:tenantId, accept the connection. -
If the header includes the session's
AppKeybut no matchingtenantId, reject the connection with a 403 error. -
If the header does not include the session's
AppKey, accept the connection. -
If the header includes the session's
AppKey, but the session doesn't have at least one allowedtenantId, reject the connection with a 403 error. This may be a developer bug. -
If the header is not present, accept the connection. If users can access the application from outside the organization's network, they can also access all sessions.
HTTPS header examples
The following examples show some of the ways to use AppKeys and TenantIDs in HTTPS headers.
- One app with one tenant
-
X-Amzn-Chime-App-Keys:AppKeyX-Amzn-Chime-Tenants:AppKey:orgIdUsers can access only the organization's WebRTC media sessions in the specified app. All other apps are blocked.
- One app with two tenants
-
X-Amzn-Chime-App-Keys:AppKeyX-Amzn-Chime-Tenants:AppKey:engineeringId,salesIdUsers can access only the media sessions for engineering and sales in the specified app. All other apps are blocked.
- Two Apps, One limited to a Tenant
-
X-Amzn-Chime-App-Keys:AppKey1,AppKey2X-Amzn-Chime-Tenants:AppKey1:orgIdUsers can access only the organization's media sessions in App 1, and any session in App 2. All other apps are blocked.
