i am very impressed with the presentation, it has fulfilled my current appetite. You have covered static& dynamic ways to write code and also how to make updates in the template and also went step by step explanation of the template. Thank You !!
Hi Sir, I am getting below error while creating with template design. Please provide reason for same. Template contains errors.: Template format error: At least one Resources member must be defined.
@@ValaxyTechnologies Sir, do you recommend jenkins pipeline for developers(gitrepo-jenkins-ansible-tomcatDevTest) to be created in private subnet or public subnet?
Sir, at(ruclips.net/video/Dl3Dx_rbtEg/видео.html) you are saying that stack should be planned per application and each stack per environment. But aws account structure creation that you recommend is environment based(prod/non-prod). Does this not conflict?
One size doesn't fit all. Right tool for the right environment. AWS philosophy is micro-segmentation for reducing blast radius. Choose the one that suits your enterprise needs.
@@ValaxyTechnologies yes your right.... But I would like to confirm that... If planning of stack is per application, then account structure should also be per application... Is that the right thought process?
I think, i didn't make it clear. There is NO right or WRONG approach. For some users, the design of the AWS resources will be solely dependent on the application environments. For another user, it may be dependent on how their teams are organized.
Architecting is all about, managing those trade-offs and weighing the risk-benefits. If you are doing other-way around, - say accounts per app, even then IAM and shared services will remain tricky to get it right in the beginning. Till the teams truly function in devops mode, some of these pain points dont go away.
i am very impressed with the presentation, it has fulfilled my current appetite. You have covered static& dynamic ways to write code and also how to make updates in the template and also went step by step explanation of the template. Thank You !!
Wow, thank you your kind words, will pass onto our developer! 🙏
(2.5 Yrs Old, still has some value to deliver)
a tip: watch series at Kaldrostream. I've been using them for watching lots of of movies these days.
@Rhett Ulises yup, been using KaldroStream for since november myself =)
Best tutorial for CloudFormation. Simply superb
Very nice and simple tutorial to follow. Thank you so much!
Wonderful vedio. clear and crisp explanation. Thanks a lot.
You should check out our other videos on AWS automation.
Clear Explanation
What is the difference between AMI and cloud formation?
Golden Ami was also having all the configuration what all the running instance have .
Great tutorial sir (Y) Thanks for uploading
This presentation is awesome!!!
You are welcome.
Awesome video... Its nice presentation..... Thanks for uploading
Thank you, check out our playlists for more interesting content.
wonderful video, thanks for the upload.
Hi Sir,
I am getting below error while creating with template design. Please provide reason for same.
Template contains errors.: Template format error: At least one Resources member must be defined.
Do you have any class-room training program?
We thought, On-Line is fantastic platform to reach larger audience base
After building the stack, how to shutdown the resources(VPC/EC2/..) of that stack? once the purpose is met.
Delete Stack
@@ValaxyTechnologies can we delete the stack using cloudformation template?
Yes
@@ValaxyTechnologies Sir, do you recommend jenkins pipeline for developers(gitrepo-jenkins-ansible-tomcatDevTest) to be created in private subnet or public subnet?
is this use in aws cli or aws python
Template is the same, whether you use in cli/gui/sdk .
please share git hub url
Updated now.
Please share the github link please
github.com/miztiik/AWS-Demos/tree/master/How-To/setup-cloudformation-webserver
404 not found
Sir, at(ruclips.net/video/Dl3Dx_rbtEg/видео.html) you are saying that stack should be planned per application and each stack per environment. But aws account structure creation that you recommend is environment based(prod/non-prod). Does this not conflict?
One size doesn't fit all. Right tool for the right environment.
AWS philosophy is micro-segmentation for reducing blast radius. Choose the one that suits your enterprise needs.
@@ValaxyTechnologies yes your right.... But I would like to confirm that... If planning of stack is per application, then account structure should also be per application... Is that the right thought process?
I think, i didn't make it clear.
There is NO right or WRONG approach. For some users, the design of the AWS resources will be solely dependent on the application environments.
For another user, it may be dependent on how their teams are organized.
@@ValaxyTechnologies point is account structuring based on environment is making us write lot of restriction policy(IAM)
Architecting is all about, managing those trade-offs and weighing the risk-benefits.
If you are doing other-way around, - say accounts per app, even then IAM and shared services will remain tricky to get it right in the beginning.
Till the teams truly function in devops mode, some of these pain points dont go away.
ɪnˈvʌɪrənm(ə)nt
?