4

I'm afraid you can't. The nested stack files must be in S3 as far as I know. You have a couple of options: Have some automation in place (e.g. aws-cli + shell script, or better ansible) that when executed will upload all the templates to a designated S3 bucket and then execute the the CloudFormation deployment. Use some templating engine like Ansible + ...


4

Look at AWS Fargate - it lets you run your Docker containers without having to spin up the EC2 instances for an ECS cluster. You simply schedule the Tasks (or Services), each gets is own IP address and they can talk to each other. You can also use AWS Service Discovery to facilitate the registration and lookup of the tasks' IP addresses. BTW Note that the ...


3

The ImageTagMutability property in ECR is not currently supported in CloudFormation, as verified by experimentation (nor is it part of the LifecyclePolicy property). There is sometimes lag between feature availability in CloudFormation, and the mutability flag was only introduced in late July. This comes up elsewhere in the corners of AWS, including: AWS ...


2

Did you try the variable ServerlessRestApi? It works for us like this: Outputs: EncryptURL: Description: "Encrypt endpoint URL for Stage environment" Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Stage/encrypt"


2

According to the documentation, the when directive is only allowed inside a stage. You have to use the script directive if you want to use conditional statements: post { always { script { if (DeleteStack == 'true') { // Destroy what you want ! } } } }


2

The 200 limit can be raised, however this is a grinding process that can take months. You work through customer support to get "elevated" as a client to more AWS privileges. Resources: - Worked under a company that specifically ran into this problem, took 8 months before that limit was lifted.


2

There is only one YAML spec. That would lead me to say "There are no YAML dialects". There are certainly differences in implementation, perhaps due to what the article claims as the spec's ambiguity: YAML specification is so ambiguous, It's a matter of opinion, I believe, but there is no doubting that various language-specific parsers of the same data ...


2

Linux Academy has many great courses on CloudFormation as well as other AWS and DevOps tools and services. They also have many guided labs where you will be given hands on guided learning of how to use various technologies. Otherwise, creating templates and launching CloudFormation stacks is something that you could learn by just creating infrastructure ...


2

1.) Create API (create-rest-api from the cli) simply creates the API Gateway resource, but it does not create the method, stage, authorizer, etc. for your API Gateway. Deploy API (create-deployment from the cli) will deploy either to an already created stage, or create a new stage for deployment. 2.) No, it will not deploy a CloudFormation stack in your ...


1

It turns out I was doing it wrong due to me being new to CloudFormation. For anyone else looking into how to attach both managed and inline policies to a user at the moment of user creation, this is how I do it which incidentally is pretty well documented by the AWS folks: ## =================== VERSION =================== AWSTemplateFormatVersion: '2010-09-...


1

Initially, I though no it does not make sense to use Terraform to create the infra structure to run Cloud Formation script to do create resources you can do using Terraform. If you are experience in Terraform and use it for your other infrastructure, it does not make sense to introduce another way of doing it, The only reason I could see to create the Cloud ...


1

As the error message states, TargetGroupARNs value should be of type List. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-as-group.html#cfn-as-group-targetgrouparns


1

While the WorkDocs API describes create-user as creating a user in the Directory Service (and does), it also activates the user as a WorkDocs user. As a result, it can only be called when the directory is associated with WorkDocs (i.e. when the directory is "enabled" in WorkDocs). These errors can occur when WorkDocs is not enabled. These errors ...


1

Resources: TargetGroup: ...


1

The split function returns a list of strings. I believe encapsulating the function in a list is what is giving you the error. Have you tried removing the brackets around the split function? Something like: !Select [ "0", !Split [ "," , !ImportValue [ !Sub "${ExportPrefix}-SubNets" ] ] ]


1

Don't worry about putting each stack in its own set of subnets, that's an overkill. Simply make the resources' Security Groups refer to other SGs in your stack templates and not to subnet CIDRs. What that means is for example the RDS SG sg-123456 will permit traffic from App SG sg-9876543 and not from the App subnet 10.20.30.0/24 you'll be fine from the ...


1

You should use TimeoutDurationMinutes in your code while requesting for spot instances via cloudformation. For more details: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticmapreduce-instancefleetconfig-spotprovisioningspecification.html


1

You wouldn't need to use Ansible for AWS cloudformation if you are fine with just using AWS cloudformation. Ansible integrated AWS cloudformation so that you can convert your local Ansible files into an AWS cloudformation easily. I'd suggest using Ansible since it provides a great way to test your stacks locally and then you would make the conversion to ...


1

I believe, alternatively, you could use CloudTrail+CloudWatch rules, but then you will get CREATE_STACK events for all stacks Here is some information about that: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-api-logging-cloudtrail.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/EventTypes.html And, of course, there's ...


1

This is a matter of implementation details and it's actually coming from the AWS Lambda product's implementation (which the doc you linked refers to), not from the Cloud Formation itself. Presently the AWS Lambda implementation requires you to include the actual dependent packages in the deployment package (per the doc you referenced). Hence the CFT doesn'...


1

Why don't you use Terraform for the purpose? It can launch as many instances you want, create network for you, create security groups, ECS, IAMs or whatever you want to create and terminate easily when you want. This is widely used in industry now.


Only top voted, non community-wiki answers of a minimum length are eligible