It's a super product - very intuitive. Also just subscribed - you have some awesome video's - I'll be getting stuck in to quite a lot of these. Thanks for your efforts
great demo.. if there is an option to see the CDK code in canvas visualization it changes a lot to see an entire project code in a whole different way, even if it doesnot have the ability modify the CDK code, visualization makes things easier to locate details in one place. I think it can be done by getting the CF from CDK and use it as an input for composer, but if there is a direct way it is much easier
Been waiting for this for years! What happens for example, when I secure apig with an iam role used by cognito idp as the auth role? I did not see any way to do this in the UI, so if I load a template that has this already in it, how does the UI handle it? This use case is just an example of a yaml template that has services that are not supported by the application composer ui?
Thanks for the video! I was curious how does it work with more specific IAM policies. For example if a lambda should only have read rights to a dynamoDB table or S3?
This is a great question! Lines represent relationships, in the case of lambda to table, this means a dynamoDbCrud policy is added to the lambda function. Currently that line can only means that and cannot mean something else. But of course there are times we will want it to mean something else, like a read only permission as u pointed out. So we need to think deeper about lines. Maybe allow them to have their own details panel for example. We will be thinking more about this in the upcoming months. Thanks for pointing this out, it helps us prioritize what we should be focusing on nexts. Lines are definitely on that list.
@@GaryJennings Thanks for letting me know. From my end there two aspect that I really like. Visualized infra and IAM management. Visualized infra really helps collectivize both drawio template and IaC in a single place which makes it much easier to digest the infra and makes it easy to understand the interconnectivity of the application. I also really like the grouping. If you are a larger organization and you different service lines grouping can make a whole lot of sense. I think the IAM is the only one I wish to be slightly improved. IAM management is imo a huge selling point for me and I feel like it needs to fleshed out a little more. I think a simple solution could be that you could right-click the line pick the IAM permission. I think also it would make sense to see the role assigned to a specific resource visiable in the visual tool (on top of the line maybe), and maybe hover over it to see the actual underlying policy? these are just my suggestions. Hope to see this flourish. Do you only see this fitting in for serverless workflows or does AWS consider this for EC2 based workflow aswell? because I think composer could be really good for both.
Can this evolve with all code changes in those functions and new aws services? Or is it only for bootstrapping? Regarding the line, it would be good if we can drag an IAM policy onto the line so we can store custom IAM policies.
This tool is meant for the whole life cycle of a project, not just bootstrapping. For example, you could start the project in composer, commit code and someone else edits the Sam project in their editor on their computer in the more traditional way. Commit. You can pull down those changes and your co workers changes will show up on the canvas. The cloudformation is the source of truth for the canvas, it doesn’t care how it was authored. As for IAM, this is a great idea! I’ll pass it on to the rest of the team
You can edit the lambda code in which ever editor u want locally. Composer will scaffold the lambda code for you and then u take it from there. The cloudformation on the other hand stays in sync and is visualized on the canvas
Yes! You can copy and paste cloudformation into the template view, or just load an existing project from a folder on your computer. Any Cloudformation template can be used. If it includes resources we dont support, they just show up as read only resources on the canvas, but u can still drag them around and place them into groups.
It doesn’t generate an output (like CDK), it keeps in sync with your CF, meaning it goes 2 ways. U can update CF and the canvas updates, u can update the canvas, and the CF updates. CDK is a 1 way thing where it generates CF as output. Composer doesn’t connect to your CDK code at the moment
@@GaryJennings Would be cool if it did generate CDK constructs and the unit tests for the constructs as well 🙂. I just tried it out and its pretty cool. I am looking forward to seeing how it evolves.
It's a super product - very intuitive. Also just subscribed - you have some awesome video's - I'll be getting stuck in to quite a lot of these. Thanks for your efforts
Wow thanks for demo. This looks like magic.
It's Visual Basic for AWS.
This is just awesome
Thanks. Useful overview
great demo.. if there is an option to see the CDK code in canvas visualization it changes a lot to see an entire project code in a whole different way, even if it doesnot have the ability modify the CDK code, visualization makes things easier to locate details in one place. I think it can be done by getting the CF from CDK and use it as an input for composer, but if there is a direct way it is much easier
Thank you 🙏🏾
Been waiting for this for years! What happens for example, when I secure apig with an iam role used by cognito idp as the auth role? I did not see any way to do this in the UI, so if I load a template that has this already in it, how does the UI handle it? This use case is just an example of a yaml template that has services that are not supported by the application composer ui?
Thanks man, I thought you actually going to talk about the functionality part of it eg like creating CRUD api
Lots more videos to come :)
Thanks for the video! I was curious how does it work with more specific IAM policies. For example if a lambda should only have read rights to a dynamoDB table or S3?
This is a great question!
Lines represent relationships, in the case of lambda to table, this means a dynamoDbCrud policy is added to the lambda function. Currently that line can only means that and cannot mean something else.
But of course there are times we will want it to mean something else, like a read only permission as u pointed out. So we need to think deeper about lines. Maybe allow them to have their own details panel for example.
We will be thinking more about this in the upcoming months. Thanks for pointing this out, it helps us prioritize what we should be focusing on nexts. Lines are definitely on that list.
@@GaryJennings Thanks for letting me know. From my end there two aspect that I really like. Visualized infra and IAM management. Visualized infra really helps collectivize both drawio template and IaC in a single place which makes it much easier to digest the infra and makes it easy to understand the interconnectivity of the application. I also really like the grouping. If you are a larger organization and you different service lines grouping can make a whole lot of sense. I think the IAM is the only one I wish to be slightly improved. IAM management is imo a huge selling point for me and I feel like it needs to fleshed out a little more. I think a simple solution could be that you could right-click the line pick the IAM permission. I think also it would make sense to see the role assigned to a specific resource visiable in the visual tool (on top of the line maybe), and maybe hover over it to see the actual underlying policy? these are just my suggestions. Hope to see this flourish.
Do you only see this fitting in for serverless workflows or does AWS consider this for EC2 based workflow aswell? because I think composer could be really good for both.
Can this evolve with all code changes in those functions and new aws services? Or is it only for bootstrapping?
Regarding the line, it would be good if we can drag an IAM policy onto the line so we can store custom IAM policies.
This tool is meant for the whole life cycle of a project, not just bootstrapping. For example, you could start the project in composer, commit code and someone else edits the Sam project in their editor on their computer in the more traditional way. Commit. You can pull down those changes and your co workers changes will show up on the canvas.
The cloudformation is the source of truth for the canvas, it doesn’t care how it was authored.
As for IAM, this is a great idea! I’ll pass it on to the rest of the team
Nice intro to Composer. Thank you. Is it possible to edit the code of the lambda
functions as per our business needs?
You can edit the lambda code in which ever editor u want locally. Composer will scaffold the lambda code for you and then u take it from there. The cloudformation on the other hand stays in sync and is visualized on the canvas
is there any perquisites to learn it ?
Is it possible to convert an existing infrastructure into composer
Yes! You can copy and paste cloudformation into the template view, or just load an existing project from a folder on your computer. Any Cloudformation template can be used. If it includes resources we dont support, they just show up as read only resources on the canvas, but u can still drag them around and place them into groups.
Does it only generate Cloud Formation templates? Will it generate any CDK code?
It doesn’t generate an output (like CDK), it keeps in sync with your CF, meaning it goes 2 ways. U can update CF and the canvas updates, u can update the canvas, and the CF updates.
CDK is a 1 way thing where it generates CF as output. Composer doesn’t connect to your CDK code at the moment
@@GaryJennings Would be cool if it did generate CDK constructs and the unit tests for the constructs as well 🙂. I just tried it out and its pretty cool. I am looking forward to seeing how it evolves.
And... where's the end result? Where is the functional UI?
The result is cloudformation. You deploy that with SAM framework into your AWS account
@@GaryJennings thanks