amazon-cloudformation

Here's (the DynamoDB part of) my Troposphere-generated JSON: "sandbox": { "Properties": { "AttributeDefinitions": [ { "AttributeName": "audit_id", "AttributeType": "S" }, { "AttributeName": "status", "AttributeType": "S" }, { "AttributeName": "filename", "AttributeType": "S" }, { "AttributeName": "file_detected_dt", "AttributeType": "S" }, { "AttributeName": "time_taken", "AttributeType": "N" }, { "AttributeName": "number_rows_processed_file", "AttributeType": "N" }, { "AttributeName": "number_rows_created_db", "AttributeType": "N" }, { "AttributeName": "info_messages", "AttributeType": "S" }

I already have my lambda / roles defined in cloudformation and would love to also use it to add a scheduled eventsources ... are there any docs or examples around ? Use Aws::Event::Rule with a ScheduleExpression and a AWS::Lambda::Permission // rule to periodically call the lambda "TagWatcherRule": { "Type": "AWS::Events::Rule", "Properties": { "ScheduleExpression": "rate(10 minutes)", "Targets": [ { "Id": "TagWatcherScheduler", "Arn": { "Fn::GetAtt": [ "TagWatcherFunction", "Arn" ] } } ] } }, // role may call the lambda "InvokeLambdaPermission": { "Type": "AWS::Lambda::Permission",

I already have my cognito user pool cloudformation template working, and have it integrated to my api gateway. But somehow i still have to manually configure the app client settings, domain, and federated identities to have a working login portal for the users. I have been looking here and there for possible solutions in automating these, but i cannot seem to find anything close to it. I would like to automate the configuration of the app client settings, domain, and federated identities via cloudformation sam template so i do not have to do these manually. Any suggestions are much appreciated

I have developed a .NET MVC application and have started playing around with AWS and deploying it via the Visual Studio Toolkit. I have successfully deployed the application using the Elastic Beanstalk option in the toolkit. As I was going over the tutorials for deploying .NET apps to AWS with the toolkit, I noticed there are tutorials for deploying with both Elastic Beanstalk and CloudFormation . What is the difference between these two? From what I can tell, it seems like they both essentially are doing the same thing - making it easier to deploy your application to the AWS cloud (setting up

From the documentation, AWS::Athena::NamedQuery , it is unclear how to attach Athena to an S3 bucket specified in the same stack. If I had to guess from the example , I would imagine that you can write a template like, Resources: MyS3Bucket: Type: AWS::S3::Bucket ... other params ... AthenaNamedQuery: Type: AWS::Athena::NamedQuery Properties: Database: "db_name" Name: "MostExpensiveWorkflow" QueryString: > CREATE EXTERNAL TABLE db_name.test_table (...) LOCATION s3://.../path/to/folder/ Would a template like the above work? Upon stack creation, will the table db_name.test_table be available to

This is part of the code of my template.yml in Cloud9: Type: 'AWS::Serverless::Function' Properties: Handler: index.handler Runtime: nodejs6.10 CodeUri: . Description: Updates records in the AppConfig table. MemorySize: 128 Timeout: 3 Role: 'arn:aws:iam::579913947261:role/FnRole' Events: Api1: Type: Api Properties: When I commit the changes in Cloud9, deployment fails at CodePipeline Deploy stage while trying ExecuteChangeSet . I get this error: CloudFormation is not authorized to perform: iam:PassRole on resource Can anyone help? While I can't say specifically what happened in your situation,

I'm trying to make AutoScalingGroup names on cloud formation templates dynamic. I was thinking if this is possible via parameters, or any other way? "DynamicASGName": { "Type": "AWS::AutoScaling::AutoScalingGroup", "Properties": { ...properties here... } } CloudFormation uses two sets of names: the logical resource name, to identify a resource within the stack, and the physical name which uniquely identifies it across the whole region. CloudFormation doesn't support setting the logical name dynamically, but with certain types, you can set the physical name in the template with the Name