I diagram at the start of what was being built would really help. I found this difficult to wrap my head around on the first listen, but once I put the design on paper while replaying it started to make a lot more sense
better explain the usecase this service solves , a new user to this service who knows AWS and its service will have no idea what is the product , protfolio , vending machine you are refering to , have not read the CF templates . looking at wizard any non computer user can say in file of s3 put that s3 value etc. explain concept first then show how these map to those conceptual solution
I will test but wonder how practical is this, if the user delete the product created, it will delet the account, ok, but if the user try create again, it will not be possibe reuse the same email, would be nice if the process of account creation was practical like create a Resorce group on azure, just create and delete as much you want without worrying about if I can use the same email or not.
The deployed product sits in the master account, so only admins with right polices would have the ability to create and delete. By the way this is an old solution, you can use Control Tower and it will give you the same capabilities plus more
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
I diagram at the start of what was being built would really help. I found this difficult to wrap my head around on the first listen, but once I put the design on paper while replaying it started to make a lot more sense
better explain the usecase this service solves , a new user to this service who knows AWS and its service will have no idea what is the product , protfolio , vending machine you are refering to , have not read the CF templates . looking at wizard any non computer user can say in file of s3 put that s3 value etc. explain concept first then show how these map to those conceptual solution
Great video. You should put links to the github repo in the description however.
I will test but wonder how practical is this, if the user delete the product created, it will delet the account, ok, but if the user try create again, it will not be possibe reuse the same email, would be nice if the process of account creation was practical like create a Resorce group on azure, just create and delete as much you want without worrying about if I can use the same email or not.
The deployed product sits in the master account, so only admins with right polices would have the ability to create and delete. By the way this is an old solution, you can use Control Tower and it will give you the same capabilities plus more
Too fast!
I bet if you tried replaying it, you would see it twice. You could even try replaying it a third time.