You should setup an account alias in IAM so that the console shows users as user @ alias on the top right instead of it making your entire AWS account number public.
Wow. So you have to build that url inside lamda? Shouldn't AWS provide/ generate that url for each Config? Just like I am role arn.. Thanks for detailed video though
Not having codecommit as a source is such a weird miss -- one of the glaring feature gaps is change approvals and linking to a codecommit repo would be such an easy way to handle that since it can enforce code review requirements. Having to set up a bespoke codepipeine with cc as a source to publish a simple config file is obnoxious
What is the difference between the 'Frequency of configuration requests vs the Frequency of configurations received' ? I mean both the frequencies wouldn't be the same always?
@@rishabhrastogi6076 Because everytime it polls for new config doesnt mean it will get the new config so if no one has made any changes inside app config the frequency of received will be less.Frequency of requests will remain same according to the value set in env variable but freq. of received will vary
Great demo! Thanks a lot for the detailed explanations :D
Excellent video, this helped me a lot. Thank you.
You should setup an account alias in IAM so that the console shows users as user @ alias on the top right instead of it making your entire AWS account number public.
Could you please demonstrate how to integrate AppConfig into your application using APIs ?
Great explanation! thank you!
Thanks a lot for the wonderful tutorial.
Well structured video ❤
Thank for the tutorial! Really enjoy each of your video.
One question here. Is there any way to figure out what config version currently in play?
Great video. Tnx!
Wow. So you have to build that url inside lamda? Shouldn't AWS provide/ generate that url for each Config? Just like I am role arn..
Thanks for detailed video though
When using iac you have all the information to build the url and set it as an environment variable in your lambda… this should be the best practise
Not having codecommit as a source is such a weird miss -- one of the glaring feature gaps is change approvals and linking to a codecommit repo would be such an easy way to handle that since it can enforce code review requirements. Having to set up a bespoke codepipeine with cc as a source to publish a simple config file is obnoxious
Could please share policy to access parameter store
@Be A Better Dev can you please use dark mode in AWS console ?
good video
Thanks a million
Seems bit of an unnecessary service since the resources need to poll for any change which ends up with billing.
Can someone please help me understand AWS AppConfig's pricing model?
What is the difference between the 'Frequency of configuration requests vs the Frequency of configurations received' ? I mean both the frequencies wouldn't be the same always?
@@rishabhrastogi6076 Because everytime it polls for new config doesnt mean it will get the new config so if no one has made any changes inside app config the frequency of received will be less.Frequency of requests will remain same according to the value set in env variable but freq. of received will vary