Closed robclemamzn closed 3 years ago
I suggest testing the deploy from a clean user-level AWS account.
Which template causes this error for you?
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-all-resources-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-browser-app-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-core-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-dynamodb-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-events-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-iam-roles-release.json
Hello sir –
The displayed error was:
'Parameter CloudWatchEventsTableName failed to satisfy constraint: Please enter a value for this field.'
The template has no value for this field.
From: Jim Thario notifications@github.com Reply-To: awslabs/aws-media-services-application-mapper reply@reply.github.com Date: Wednesday, January 13, 2021 at 10:29 AM To: awslabs/aws-media-services-application-mapper aws-media-services-application-mapper@noreply.github.com Cc: "Clements, Rob" robclem@amazon.com, Author author@noreply.github.com Subject: Re: [awslabs/aws-media-services-application-mapper] Deploy fails with CloudWatch template error (#177)
Which template causes this error for you?
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-all-resources-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-browser-app-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-core-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-dynamodb-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-events-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-iam-roles-release.json
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/awslabs/aws-media-services-application-mapper/issues/177#issuecomment-759635566, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASCYA3XFVUMSMIM5SHYREVDSZXQ6PANCNFSM4WBGQKEQ.
It was the default template https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-dynamodb-release.json
Pasted that URL into the form after setting region to ‘us-west-2’
From: Jim Thario notifications@github.com Reply-To: awslabs/aws-media-services-application-mapper reply@reply.github.com Date: Wednesday, January 13, 2021 at 10:29 AM To: awslabs/aws-media-services-application-mapper aws-media-services-application-mapper@noreply.github.com Cc: "Clements, Rob" robclem@amazon.com, Author author@noreply.github.com Subject: Re: [awslabs/aws-media-services-application-mapper] Deploy fails with CloudWatch template error (#177)
Which template causes this error for you?
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-all-resources-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-browser-app-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-core-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-dynamodb-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-events-release.json
https://rodeolabz-us-west-2.s3.amazonaws.com/msam/msam-iam-roles-release.json
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/awslabs/aws-media-services-application-mapper/issues/177#issuecomment-759635566, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASCYA3XFVUMSMIM5SHYREVDSZXQ6PANCNFSM4WBGQKEQ.
Until we have an update on documentation, you can use the following guide to install the entire solution with a single template.
This will be addressed in the new Implementation Guide and Landing Page releasing with 1.8.0.
The MSAM deploy currently fails with this CloudWatch error: 'Parameter CloudWatchEventsTableName failed to satisfy constraint: Please enter a value for this field.'
I was attempting to invoke it in my home region of us-west-2 if that matters. Also: when you change the region, the setup tool clears the template field, which you have to re-populate by restarting setup and copying the value before you change the region. The default template path should be listed on the page text independent of the field value...