unable to deploy cloudformation template (deployment.yaml) about aws-streaming-media-analytics

[alcousins]

thanks for reporting this. Did you build the template yourself (ie not using one of the pre-built ones?)?

The Schema resource in the CloudFormation template pulls the AppSync Schema from S3:

Schema:
Type: AWS::AppSync::GraphQLSchema
DependsOn: GraphQLApi
Properties:
ApiId: !GetAtt GraphQLApi.ApiId
DefinitionS3Location: !Join ["",["s3://",!Join ["/", [!Join ["-", [!FindInMap ["SourceCodeBucket", "General", "S3Bucket"], !Ref "AWS::Region"]],!Join ["/", [!FindInMap ["SourceCodeBucket", "General", "RecentVideoViewAppSyncCodePrefix"], !FindInMap ["SourceCodeBucket", "General", "Version"], "appsync_schema.graphql"]]]]]]

The S3 Bucket in question is defined in the Makefile in the 'bucket' variable, and the template is copied as part of the 'make copycodeww' operation:

aws-streaming-media-analytics/Makefile.sample

Line 85 in 33b0b50

aws s3 cp cloudformation/appsync_schema.graphql s3://$(bucket)-$$region/qos/lambda-functions/recentvideoview-appsync-function/$(version)/ --acl public-read --profile $(profile); \

My first guess is you may not have completed this step in building the code? Apologies if there was any confusion, we've made some effort to clean up any stray artefacts in the repo that might trip up in this way, but if you've found something, please let me know how you deployed the code and i'll take steps to make this clearer/remove something that might have led you astray!

[virkillz]

Hi, it seems like I also cannot follow the instruction and resulting in the same error as follow:

I'm following the instruction in README.md

I download the deployment.yaml file:
https://github.com/awslabs/aws-streaming-media-analytics/blob/master/cloudformation/deployment.yaml

• One thing I notice, it mentioned in step 3 the stack name by default is mediaqos, however, I can't see it populated or mentioned elsewhere inside the yaml file.
• Inside hte deployment.yaml file it mention the S3 bucket name is ganeshji-codedeployus. And from the error above it looks like cloudformation cannot found the S3 bucket. Does this means I need to create it first?

Thanks.

[alcousins]

Ah, I think i know what's going on here. I will try to push an update. Thanks for identifying this (obvious) gap. Documentation for this project has drifted through a few different sources.

In the meantime, you can deploy the template from the following sources which have been built/tested:

https://streamingvideoanalytics.workshop.aws/intro/deploying-in-own-account.html

I'll merge in some updated references to the docs and do a cleanup.

My apologies, this is a bit of an obvious one. Will get this fixed ASAP.

[alcousins]

i'm working on a fix for the documentation in #20

[alcousins]

I have merged #20 which cleans up the documentation. The old docs referenced using the deployment.yaml file that is in the repository as your starting point, however, this file is as you've noticed, a build artifact and locked down to a specific account.

I've removed the build artifacts from the repo, blocked on gitignore, and updated the docs to reference the latest workshop documentation which includes links to pre-built templates that are hosted in public S3 buckets so can be deployed without needing to build the project yourself.

[alcousins]

I noticed in the first attached screenshot @ariskumara was deploying in Singapore. I've just run a quick test deploy of the template for this region in the README.md and can confirm it deployed successfully.

I'll leave this open for a few days, please let me know if you're still having trouble (or success!). If I don't hear back i'll close it as I think these documentation problems were the likely cause of the two problems noted above.

[virkonomy]

Thanks. We try to launch by clicking the Launch Stack link (Singapore). I mostly worked as described (mediaqos name is pre-filled, etc).

However I got different type of failure.

Based on the error, do you think the Account verification is the root cause? I already open ticket to support as suggested. Once its resolved I will try again. Thanks again.

[alcousins]

my apologies, i missed this response, but yes, that error is caused by a new account. Following the guidance in the error should help to resolve that error.