CloudFormation - From Zero to Hero!

[@anandvamsi5141]

Nice explanation for CF, Good Job!!

[@amanbagrecha]

Really good explanation. The fundamentals were really necessary and you've done a great job!

[@LaimonasGaming]

Thanks, appreciate feedback :)

[@technovice4886]

Cloudformation appeared scary to me untill I went hrough this...thanks!

[@AVISH747]

This is awesome.. was looking out for just this.

[@jamilabbasOfficial]

Thanks for such a great tutorial on cloud formation.

[@bmariambete4322]

It was great .Provided with very easy way. Thanks

[@LaimonasGaming]

Great to hear that!

[@samirsingh108]

Thank You for this useful tutorial. Great explanation with examples.

[@amitpadgaonkar8830]

Thank you for the tutorial. Where can I get the slides?

[@bharatkendre9878]

Thank you very much. Good explanation.

[@hakeemshahzadibegum1478]

Nice video clip on AWS

[@dataslid]

Amazing aws tuts thanks

[@maycogarcia4788]

Very good.

[@geminishoeland2738]

hi its help me .kindly suggest me that we can create parameter as a separate stack and from the parameter stack we can create another stack

[@yogendarmoola964]

hi,how to attach a role to existing ec2 instance in cloudformation.

[@LaimonasGaming]

If EC2 was deployed without using CloudFormation, then it is very difficult, advanced AWS CDK usage is required. Better redeploy your EC2 (+ Role) using CloudFormation.

[@sangeetagentyal3702]

How to add 'QueueUrl' while giving call to SQS through step function in cloud-formation template?

[@datavesr]

1)First, define an Amazon SQS queue resource: Resources: MyQueue: Type: AWS::SQS::Queue Properties: QueueName: my-queue-name 2)Next, define the AWS Step Functions state machine: Resources: MyStateMachine: Type: AWS::StepFunctions::StateMachine Properties: StateMachineName: my-state-machine-name DefinitionString: Fn::Sub: - | { "Comment": "My state machine", "StartAt": "SendSQSMessage", "States": { "SendSQSMessage": { "Type": "Task", "Resource": "arn:aws:states:::sqs:sendMessage", "Parameters": { "QueueUrl.$": "$.queueUrl", "MessageBody.$": "$.messageBody" }, "End": true } } } - queueUrl: !GetAtt MyQueue.Arn messageBody: "Hello, world!" 3)Finally, define the CloudFormation stack parameters that include the 'QueueUrl': Parameters: QueueUrl: Type: String Default: !GetAtt MyQueue.Arn

[@NourAslaoui]

I honestly find Cloudformation templates way more humain-readable than the DOMs

[@LaimonasGaming]

Interesting. I couldn't get used to CF templates after 5 years. AWS CDK for me was the 21st-century discovery.

[@mattongbp]

DOMs are JSON with a lot of difficult syntax and YAML is much easier.

[@dhaoubouzayani6571]

Think you. Can I have the code please ?

[@ZahoorKhan-qx6gt]

This is not zero to hero. This is zero to beginner.

[@aisimeon]

I disagree, yaml is better. use cdk just to read your yml. yes, maybe it will take more time to write a valid yml, but you can test it out immediately, it can be used in any cdk - python, java, etc. devops will understand it easily.

[@sauloaccaio]

too much slowly