Jason Hummel

@peterwoodworth Yes. In my Pipeline template I see: EnvironmentVariables": "[{\"name\":\"AWS_API_BASE_URL\",\"type\":\"PLAINTEXT\",\"value\":\"#{DemoEnvTestPipelineStackInfrastructuredemoenv99E6F651.apiurl}\"},{\"name\":\"AWS_FRONTEND_BUCKET_NAME\",\"type\":\"PLAINTEXT\",\"value\":\"#{DemoEnvTestPipelineStackInfrastructuredemoenv99E6F651.bucketname}\"}]" The ENV variable is the correct one however, It's when I use it in the step outside of the ENV...

Exactly, the value in the ENV variable is correct, but the value in the policystatement is incorrect ``` // The echo shell commands array value is CORRECT // the CfnOutput...

Little more context, here's what I see in the CloudFormation template for that policyStatement: ``` { "Action": "S3:*", "Effect": "Allow", "Resource": [ "arn:aws:s3:::infrastructure-demo-etfrontendbucketa9f7bddb43ed5f2da912", "arn:aws:s3:::infrastructure-demo-etfrontendbucketa9f7bddb43ed5f2da912/*" ] } ``` Not sure where...

I've actually tried this in the past. I always end up with an error 'DemoEnvTestPipelineStack No export named found' Here's how the code was updated: The Stack: ``` export class...

Any ideas here? Doing more research, I think maybe the 'no export named' problem is because the pipeline creates the bucket in another account. Is there some way to get...