SpekeGateway 2.0.0 migration guide
Intro
The main reasons for the migration is deprecation of .net6 lambda environment, and our aim to align CloudFormation parameters with Cloud Videokit Kit console configuration parameters.
Upgrading Speke Gateway to version 2.0.0 is mandatory for all Cloud DRM customers by December 20, 2024. Previous versions (1.3.6 and earlier) utilize .NET 6, which will be deprecated by AWS on December 20, 2024.
Cloudformation outputs won't be affected. The urls will stay the same and no further actions will be required from your side.
The list of changes in the input parameters are:
| Previous key name | New key name | Reason |
|---|---|---|
| AppId | ClientId | Discrepancy between CF template and CVK console |
| AppSecret | ClientSecret | Discrepancy between CF template and CVK console |
| AuthUrl | TokenUrl | Discrepancy between CF template and CVK console |
| LiveInvokeUrl and VodInvokeUrl | SpekeUrl | Identical value |
| EnableLogging | EnableGatewayLogging | Clarification |
The removed parameters are:
| Key name | Reason |
|---|---|
| BrandGuid | Already present in the SpekeUrl |
| Scope | Has a constant value |
The added parameters are:
| Key name | Reason |
|---|---|
| AuthenticationMethod | Option to choose authentication flow |
| ApiKey | Parameter for the alternative x-api-key authentication flow |
| LambdaLoggingLevel | An option to specify logging level |
Migration using AWS console
Cloudformation Template URL https://insysvt-solutions-euw1.s3.eu-west-1.amazonaws.com/solutions/spekegateway/2.1.0/cloudformation.yaml
- Click Update on CloudFormation Stack
- Specify new S3 URL
- Fill parameter fields
The parameters 1, 2, 3 and 4 are the only ones that need to be filled. Values can be found in the drm console.
- Click Submit at the end screen
