Video on Demand on AWS cloudformation template failed to create

user_11850616 0
Viewed 150

I'm trying to deploy cloudformation template with the help of this URL: https://aws.amazon.com/solutions/implementations/video-on-demand-on-aws/

After sometimes it failed to create and ROLLBACK_IN_PROGRESS and then DELETE_IN_PROGRESS and finally DELETE_COMPLETE

CloudWatch Logs

.......
{
    "message": "internal server error",
    "code": "InternalServerErrorException",
    "time": "2020-08-04T15:37:35.622Z",
    "requestId": "dfffa7cc-bba8-44ae-bec4-507a8cc822af",
    "statusCode": 500,
    "retryable": true
}
......

Screenshots: CloudWatch log screenshot

1

Creation failed event screenshot

2

MediaPackageVod and MediaConvertTemplates are the only two logicalID which fails to create. Due to these ROLLBACK_IN_PROGRESS initiated.

amazon-cloudformation aws-lambda amazon-s3
1 Answers

The template works. I deployed it myself on my sandbox account. Thus, I can't replicate the issue and the fault must be somewhere else.

enter image description here

I used us-east-1 region with all values of the template set to their default. Maybe you've changed the default settings to some incorrect ones, or you have no permissions to create some of the resources?

If this helps, in your case the lambda function associated with the following custom resource fails:

  MediaPackageVod:
    Type: Custom::LoadLambda
    Properties:
      ServiceToken: !GetAtt CustomResource.Arn
      Resource: MediaPackageVod
      StackName: !Ref AWS::StackName
      GroupId: !Sub "${AWS::StackName}-packaging-group"
      PackagingConfigurations: "HLS,DASH,MSS,CMAF"
      DistributionId: !Ref CloudFront
      EnableMediaPackage: !Ref EnableMediaPackage

Thus, you can inspect the lambda function, and try to debug it. It will be available in your Lambda console.

Also the error you are getting is 500, which means this is lambda service error itself. Could be some temporary issue on the AWS side:

ServiceException -The AWS Lambda service encountered an internal error. HTTP Status Code: 500

Based on the comments and chat discussion:

A recommended solution was to check in different region. And in did, the template works in us-west-2.

The list of supported regions for AWS Elemental MediaPackage can be found here.

user_2488230
Related