You should use Cognito as a quick way to provide SAML/OAuth to a lot of apps, but it's not going to solve all your authentication woes. Nothing does (not even A

You should use Cognito as a quick way to provide SAML/OAuth to a lot of apps, but it's not going to solve all your authentication woes. Nothing does (not even Auth0). You should use CloudFormation if it's there and you're just trying to stand something up quickly. Shell scripts with AWS CLI works too. For more robust long term stuff, use Terraform, Pulumi, or custom Boto3 code. The point is to just start using the Infrastructure as Code pattern early, not to make it perfect. Terraform is surprisingly painful after a while, but it's easier to standardize your organization on large-scale. There's no great solutions in this space. You should absolutely throw money at ElastiCache to quickly scale up and down a cache. If you're not a very experienced sysadmin (and fuck the entire tech industry for making that term a dirty word - if you are not experienced at administrating systems) you'll be spending unnecessary time and energy to stand up and maintain it. Your caching should ideally just be in your service and scaling your services themselves should be sufficient, but whatever, Redis wasn't invented for people who write good code. > But, not all data/records/events should go into Kinesis Not all of anything should go into anything. Use it if it's convenient. Lambda is very useful for batch jobs and CloudWatch-triggered maintenance tasks. I wouldn't rely on it for anything more than that; I would rather just deploy the same code to a Fargate Spot Instance and not deal with all of Lambda's bullshit.