cloudformer | Rake helper tasks for AWS Cloudformation | AWS library
kandi X-RAY | cloudformer Summary
kandi X-RAY | cloudformer Summary
Cloudformer attempts to simplify AWS Cloudformation stack creation process in ruby projects by providing reusable rake tasks to perform common operations such as apply(create/update), delete, recreate on stack along with validations on templates. Task executions which enforce a stack change will wait until ROLLBACK/COMPLETE or DELETE is signalled on the stack (useful in continuous deployment environments to wait until deployment is successful). Refer examples section for more information.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Defines a task
- Defines a task
- Defines a new task
cloudformer Key Features
cloudformer Examples and Code Snippets
Lines of Code : 105License : Permissive (MIT)
Copy{
"AWSTemplateFormatVersion": "2010-09-09",
"Description": "Cloudformer - Demo App",
"Parameters": {
"AmiId": {
"Type": "String"
}
},
"Resources": {
"ApplicationServer": {
"Type": "AWS::EC2::Instance",
require 'cloudformer'
Cloudformer::Tasks.new("earmark") do |t|
t.template = "cloudformation/cloudformation.json"
t.parameters = parameters
end
"Parameters": {
"PackageUrl": {
"Type": "String"
},
"PackageVersion": {
"Type": "String"
rake apply # Apply Stack with Cloudformation script and parameters(And wait till complete - supports updates)
rake delete # Delete stack from CloudFormation(And wait till stack is complete)
rake events # Get the recent ev Community Discussions
Trending Discussions on cloudformer
QUESTION
AWS CloudFormation offers a default stack named CloudFormer, a template creation tool. CloudFormer creates a CloudFormation template from your current AWS environment, allowing you to click which manually created resources to include in your template.
The AWS CloudFormer documentation does not list the AWS services that CloudFormer supports. There is an announcement from 2013 (CloudFormer Now Supports Amazon VPC and More AWS Resources) that lists a subset of supported services, but there is no complete list.
Which services does AWS CloudFormer support? For example, does it support commonly used severless managed services, such as AWS Lambda and AWS Cognito?
...ANSWER
Answered 2020-Jul-16 at 20:59AWS CloudFormer is not a complete solution for creating CloudFormation templates from your existing AWS infrastructure.
AWS CloudFormer supports a very limited subset of AWS resources, focused on Network, Compute and Storage. The vast majority of AWS managed services, such as AWS Lambda and AWS Cognito are not support.
If you'd like to create a template of your network infrastructure (VPCs et al.) and EC2 instances, CloudFormer may be useful. If you're using other AWS managed services, you're out of luck.
Additionally, CloudFormer does not have a programmatic interface.
AWS CloudFormer's core support DNS: Route53 Network: VPC, Subnets EC2: Instances, LoadBalancer, Autoscaling, ElasticIP, SecurityGroups Storage: S3, EBS, RDS, SimpleDB, DynamoDB, ElastiCache, Redshift
Other supported services
- CloudWatch Alarms (but not CloudWatch dashboards)
- CloudFront
- Elastic Beanstalk
- Kinesis Streams
- OpsWorks
- SNS
- SQS
Common services that are NOT supported by AWS CloudFormer
- Cognito
- ECS
- EFS
- EKS
- Glue
- Lambda
- SageMaker
QUESTION
I was wondering if anybody has had any experience creating a cloudformation template from exisiting AWS resources.
I am currently trying to migrate from a classic elb to a alb using the wizard. However I already have cloudformation templates managed by github. Therefore I would need to add the alb in after it has been created. I tried using cloudformer but it doesn't appear to support alb whereas it does pickup classic.
Has anybody had experience migrating elbs and creating cloudformation templates from existing resources?
Many thanks!
...ANSWER
Answered 2020-Jun-10 at 11:25AWS::ElasticLoadBalancingV2::LoadBalancer is one of the resources that can be imported into CloudForamtion. But sadly AWS::ElasticLoadBalancingV2::TargetGroup can't be imported.
Importing is a try-and-see operation. It is not automated as many people expect it to be. The reason is that you have to manually create the template for the resources being imported. What's more, the attributes of the resources in the template created must match exactly existing resources.
CloudFormer is not helpful these days. Its not maintained by AWS anymore and has been in beta for years.
If you haven't tried importing anything before, the best way would be to start with AWS tutorial: Importing Existing Resources Into a Stack
This way you can start with something simple, before you move to ALB with all its listeners and listener rules. Off course you have to create new Target Group as well as it can't be imported sadly.
QUESTION
I have been using the cloudformer template within Cloudformation to generate a template for AWS resources. I notice it does create the template with DynamoDB tables and some other resources but does not create one for AppSync, Lambda, and IAM roles. Is there a way to auto generate the cloudformation template from an existing AppSync schema and other resources? Would I have to use the designer tool within CloudFormation to create the stack/template and copy over the schema/template and resources by hand?
...ANSWER
Answered 2020-Apr-09 at 22:10There is no utility available to auto generate the cloudformation template from existing account resources. The best option is to use the Cloudformation designer to construct all resource definitions. The schema can be uploaded to S3 and the designer needs to be updated to point to it to load.
QUESTION
I'm struggling to use AWS Cloud Former to generate a CloudFormation template. I have already launched the Cloud Former stack twice and attempted to connect to the associated DNS for the EC2 instance generated each time and keep receiving the error pictured below. I have already tried to create a new SSL certification for the EC2 instance via AWS Certificate Manager, but AWS does not allow this for EC2 instances. I'm not very familiar with SSL/HTTPS processes and would appreciate any guidance on next steps I should pursue to address/troubleshoot this.
Upon further research into this, I have found the following issue:
Specifically, I'm seeing the following SSL certification issue:
Has anyone else seen this yet with CloudFormer recently?
ANSWER
Answered 2020-Jan-17 at 22:56SSL certificates require a domain. On AWS you can set one up with the certificate manager, but it will still have an issue until you correctly configure Route 53 on AWS as well.
QUESTION
How to export existing, configured and tested AWS CloudWatch alarms to Cloudformation template?
I know about CloudFormer tool, but it supports limited number of AWS services (Amazon VPC, DynamoDB, etc) and don't supports some of services which we use. Which tools and approaches can I use in my case for generating Cloudformation template?
...ANSWER
Answered 2019-Nov-20 at 13:41AWS have recently announced the ability to create a new CloudFormation stack using existing resources or update an existing CloudFormation stack with imported resources. The announcement came via the AWS blog.
The CloudFormation documentation has been updated and includes supported resources (CloudWatch Alarms, VPC and DynamoDB Tables are all supported).
QUESTION
I'm trying to export existing AWS Data Pipeline task to Terraform infrastructure somehow.
Accordingly, to this issue, there is no direct support for Data Pipelines, but it still seems achievable using CloudFormation templates (terraform resource).
The problem is that I cannot find a way to export existing pipeline into CloudFormation template.
Exporting the pipeline with its specific definition syntax won't work as I've not found a way to include this definition into CloudFormation. CloudFormer does not support exporting pipelines either.
Does anybody know how to export a pipeline to CloudFormation or any other way to get AWS Data Pipeline automated with Terraform?
Thank you for your help!
...ANSWER
Answered 2019-Nov-03 at 01:53UPD [Jul. 2019]: Some progress has been made in the terraform repository. aws_datapipeline_pipeline resource has been implemented, but it is not yet clear how to use it. Merged pull request
Original answer:
As a solution to this problem, I've come up with a node.js script, which covers my use case. In addition, I've created a Terraform module to be used in Terraform configuration.
Here is the link to the gist with the code
Will copy usage examples here.
Command Line:QUESTION
Is there any way to get the cloudformation for lambdas? I know you can create AWS CloudFormation Templates from existing AWS Resources using CloudFormer. And also, cloudformer is in beta mode (AWS CloudFormer 0.41 (Beta)) at the time I am asking this question. While following the documentation, I could not find a way to create cloudformation for my lambda
I have selected everything while creating the cloudformation but the template contains no lambdas.
Is it not supported or I am missing something? If it is not supported, what is the reason behind this?
...ANSWER
Answered 2019-Sep-08 at 21:45If you save the Lambda code to disk, you could use Rubycfn to create your Lambda function in CloudFormation.
gem install rubycfn
Save the file below to example.rb and run rubycfn example.rb to generate the CloudFormation.
QUESTION
I want to replicate the infrastructure from one region(us-east-1) to another(us-east-2). so,I have generated a cloudfromation template of an existing infrastructure with the help of cloudformer tool.
...ANSWER
Answered 2018-Nov-19 at 05:41After a lot of debugging, when I started launching the things manually, I found the same error and I got to know that c3.large is causing the error. When I launch the template with c4.large it successfully launched the template from us-east-1 to us-east-2.
QUESTION
I have managed to reverse engineer all of my Route 53 record sets into a CloudFormation template using the (beta) CloudFormer tool. However, for some reason my NS and SOA record sets are not present in the template — why?
ANSWER
Answered 2018-Oct-06 at 18:04Because the values would be incorrect or not useful.
Route 53 populates these records with the correct values when a hosted zone is created. Deleting that hosted zone and creating a new one (for the same domain) results in the assignment of new, different NS and SOA values.
Setting these records in the new hosted zone to match those of the old hosted zone will not accomplish anything other than making the new hosted zone's records be wrong.
QUESTION
I want to create an elasticache instance using redis.
I think that I should use it "cluster mode disabled" because everything will fit into one server. In order to not have a SPOF, I want to create a read replica that will be promoted by AWS in case of a failure of the master. If possible, it would be great to balance the read only operations between master and slave, but it is not mandatory.
I created a functioning master/read-replica using the aws console then used cloudformer to create the cloudformation json conf. Cloudformer has created me two unlinked AWS::ElastiCache::CacheCluster, but by reading the doc. I don't understand how to link them... For now I have this configuration :
ANSWER
Answered 2018-Jul-16 at 21:47I managed to do this using AWS::ElastiCache::ReplicationGroup, the NumCacheClusters parameter provide the possibility to have numerous servers. Beware : it seem that you have to handle the connection to master/slave yourself (but in case of a master's failure, aws should normally detect it and change the dns of a slave to permit you point do not change your configuration). here is a sample :
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cloudformer
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
