amazon-cloudformation

just like in the title. I can deploy stuff on AWS using only Cloud Formation. Now I try to secure my API Gateway with API Keys and looks like I need a Usage Plan for it. It doesn't seem to be covered by the documentation right here: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigateway-apikey.html Have any of you had a similar problem and if yes, how did you solved it? AWS has today released the ability to create AWS::ApiGateway::UsagePlan using cloud formation templates Unfortunately there isn't currently a method of Adding API Keys to a UsagePlan through

How can I change the IAM Role for a Lambda function in an CloudFormation template of an AWS CodeStar project? I have created a AWS CodeStar project (web service, Lambda based, Node.js). By default, AWS CodeStar generates the following CloudFormation: AWSTemplateFormatVersion: 2010-09-09 Transform: - AWS::Serverless-2016-10-31 - AWS::CodeStar Parameters: ProjectId: Type: String Description: AWS CodeStar projectID used to associate new resources to team members Resources: HelloWorld: Type: AWS::Serverless::Function Properties: Handler: index.handler Runtime: nodejs4.3 Role: Fn::ImportValue:

When creating a Linux AMI in AWS with CloudFormation, I can view the output of the Cloud Init scripts, for example if I have a UserData section that echoes to stdout: "UserData": { "Fn::Base64": { "Fn::Join": [ "", [ "#!/bin/bash -xe\n", "echo hello, stdout\n" ] ] } } Then /var/log/cloud-init-output.log will contain these lines: + echo hello, stdout hello, stdout What is the equivalent log file for Windows AMIs? Is it somewhere in http://169.254.169.254/ , or is it a log file somewhere? According to the documentation you have to wrap UserData with <script></script> . The log is written to

I'm using CloudFormation to spin up some servers in an auto scaling group, and I want them all to use basic monitoring. I tried setting Monitoring to false in the AWS::AutoScaling::AutoScalingGroup properties as well as the AWS::AutoScaling::LaunchConfiguration , but the stack cannot start up; I see CREATE_FAILED with the error message: Encountered unsupported property Monitoring . Just another day in the lovingly roguish world of almost-but-not-quite-consistant CFN template syntax. The property you want is InstanceMonitoring , not Monitoring . It should apply to your LaunchConfiguration

We need to list all the stacks that are in CREATE_COMPLETE state. In our AWS account we have >400 such stacks. We have the following code written for this: stack_session = session.client('cloudformation') list_stacks = stack_session.list_stacks(StackStatusFilter=['CREATE_COMPLETE']) However this lists only the first 100 stacks. We want to know how we can get all the stacks? We are using the python boto3 library. I got this working using pagination. The code I wrote is below: stack_session = session.client('cloudformation') paginator = stack_session.get_paginator('list_stacks') response