aws-codepipeline

From a CloudFormation template, you can deploy CodeCommit and CodePipeline . From this announcement , You can now choose AWS CloudFormation as a deployment action in your release workflows built using AWS CodePipeline. I've worked out most of the Cloudformation Template, but I can't figure out the stages. Resources: PipelineRepo: Type: AWS::CodeCommit::Repository Properties: RepositoryName: pipeline RepositoryDescription: Pipeline setup repo PipelineArtifacts: Type: AWS::S3::Bucket PipelineRole: Type: AWS::IAM::Role Pipeline: Type: AWS::CodePipeline::Pipeline Properties: Name: pipeline

I was editing my CloudFormation templates and suddenly AWS tells me I need CAPABILITY_NAMED_IAM . I am curious as to which change triggers this? What is a named IAM resource? Before I already "name" my resources like RoleName: !Sub '${PipelineName}-codebuild' I am not asked to add this capability, I think until I add Parameters: AppName: Type: String Description: Prefix for resources Resources: LambdaRole: Type: AWS::IAM::Role Properties: RoleName: !Ref AppName To my SAM application template. But arent they the "same" except one uses !Ref ? Or maybe some other change triggered this? For

I have a AWS CodePipeline configured in a terraform file, like this: resource { name = "Cool Pipeline" ... stage { name = "Source" ... action { name = "Source" ... configuration { Owner = "Me" Repo = "<git-repo-uri>" Branch = develop OAuthToken = "b3287d649a28374e9283c749cc283ad74" } } } lifecycle { ignore_changes = "OAuthToken" } } The reason for ignoring the token, is that the AWS API doesn't show that token to terraform, instead AWS API outputs this with aws codepipeline get-pipeline <name> : "pipeline": { "stages": { "name": "Source", "actions": { "configuration": { "OAuthToken": "****" }

I was trying to set up AWS Code Pipeline with AWS SAM for Lambda using Java-8 as mentioned in the documentations http://docs.aws.amazon.com/lambda/latest/dg/automating-deployment.html (example is in node.js though). However, my Staging is stuck at CloudFormation Stack is stuck in REVIEW_IN_PROGRESS for a long time. Is there any way to debug this issue? I don't see any further events coming in console. Is there any specific things to check for? The template is as follow $ aws codepipeline get-pipeline --region us-east-1 --name aws-lexbot-facebook-pipeline { "pipeline": { "roleArn": "arn:aws:iam