{"id":1197,"date":"2020-03-06T11:24:14","date_gmt":"2020-03-06T10:24:14","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=1197"},"modified":"2021-03-24T12:40:35","modified_gmt":"2021-03-24T11:40:35","slug":"how-to-create-and-maintain-an-aws-serverless-infrastructure-with-troposphere-and-codepipeline","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/how-to-create-and-maintain-an-aws-serverless-infrastructure-with-troposphere-and-codepipeline\/","title":{"rendered":"How to create and maintain an AWS serverless infrastructure with Troposphere and CodePipeline"},"content":{"rendered":"
Serverless AWS infrastructures often provide huge advantages with respect to \u201cclassic\u201d EC2 based AWS infrastructures as one can easily understand considering, for example, a basic Serverless web application developed using AWS Lambda (backend), DynamoDB (database), Cognito (Authentication) and S3 – CloudFront (Angular single page application). An application like this will scale automatically adapting to every level of traffic, will typically cost significantly less than an EC2 hosted application since the billing will only depend on the traffic and will have a close to zero maintenance cost since you don\u2019t need to update the OS, harden the instance, install security patches and so on. So basically going serverless is a no brainer in most situations: you\u2019ll pay less for an application that will be able to scale faster and you\u2019ll not be responsible anymore for the security of the various application components: AWS will take care of that.<\/span><\/p>\n