From 71d1c3ad791a8006795595267881747752d53274 Mon Sep 17 00:00:00 2001 From: Jon Hartzler Date: Wed, 9 Oct 2019 15:22:01 -0400 Subject: [PATCH] change statemaching to be more specific and the keys to work out of the box with the main key set --- deploy/cloudformation/manifest-pipeline.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy/cloudformation/manifest-pipeline.yml b/deploy/cloudformation/manifest-pipeline.yml index cd60382f..28f25f2c 100644 --- a/deploy/cloudformation/manifest-pipeline.yml +++ b/deploy/cloudformation/manifest-pipeline.yml @@ -36,7 +36,7 @@ Parameters: MarbleProcessingKeyPath: Type: String Description: The ssm path to look for the marble data processing config from - Default: '/all/marble-data-processing/test' + Default: '/all/marble-data-processing/prod' NoReplyEmailAddr: Type: String Description: Email address notification emails are sent from @@ -369,7 +369,7 @@ Resources: Action: - 'states:ListStateMachines' - 'states:StartExecution' - Resource: !Sub "arn:aws:states:${AWS::Region}:${AWS::AccountId}:stateMachine:*" + Resource: !Sub "arn:aws:states:${AWS::Region}:${AWS::AccountId}:stateMachine:${AWS::StackName}-SchemaStateMachine" - PolicyName: ManifestPipelineSsmPermissions PolicyDocument: Version: 2012-10-17