[Action may be required] Amazon Chime SDK APIs in the Chime namespace are no longer supported for new customers

[dnnejo]

There are upcoming changes for the Amazon Chime SDK that may affect your application.

Background

At launch, the Amazon Chime SDK offered APIs on an endpoint shared with the Amazon Chime Application, service.chime.amazonaws.com, which is hosted in the US-EAST-1 Region. These APIs are part of the Chime namespace in the AWS SDK [1].

Since then, the Amazon Chime SDK launched five dedicated endpoints [2] with functionality equivalent APIs, each with its own namespace in the AWS SDK:

ChimeSDKIdentity => identity-chime..amazonaws.com [3]
ChimeSDKMediaPipelines => media-pipelines-chime..amazonaws.com [4]
ChimeSDKMeetings => meetings-chime..amazonaws.com [5]
ChimeSDKMessaging => messaging-chime..amazonaws.com [6]
ChimeSDKVoice => voice-chime..amazonaws.com [7]

The dedicated endpoints are available in additional AWS Regions [8] and offer additional functionality not available in the shared endpoint.

What’s Changing

The Amazon Chime SDK is ending support for APIs on the shared endpoint.

On June 29, 2023, the Amazon Chime SDK APIs in the Chime namespace in the AWS SDK will be tagged as not supported. Existing customers can continue to use the Chime namespace and the shared endpoint, however new customers will only be able to use the dedicated namespaces and endpoints.

On April 1, 2024, the Amazon Chime SDK APIs in the Chime namespace in the AWS SDK will be removed. Existing customers may continue to use older versions of the AWS SDK and call Amazon Chime SDK APIs the Chime namespace.

On June 30, 2024, we plan to remove the Amazon Chime SDK APIs from the shared endpoint. However, we will confirm that you have migrated your application first.

What Do I Need To Do

If your application uses the shared endpoint or namespace you should plan to migrate your application to use the dedicated endpoints and namespaces before June 30, 2024.

If your use of the Amazon Chime SDK is in scope of one or more AWS compliance programs, you should discuss your migration with your AWS account team as part of the migration planning process.

To assist you with migration, there is a Migration Guide in the Amazon Chime SDK Developer Guide [8], which include a API mapping table and detailed guides for each dedicated namespace.

If you have any questions or concerns, please contact AWS Support [9].

[1] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime.html
[2] https://docs.aws.amazon.com/general/latest/gr/chime-sdk.html
[3] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Identity.html
[4] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Media_Pipelines.html
[5] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Meetings.html
[6] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Messaging.html
[7] https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Voice.html
[8] https://docs.aws.amazon.com/chime-sdk/latest/dg/migrate-from-chm-namespace.html
[9] https://aws.amazon.com/support