Posts

Showing posts with the label AWS

AWS in Plain English!

Image
Run an App Services No matter what you do with AWS you'll probably end up using these services as everything else interacts with them. EC2 Should have been called Amazon Virtual Servers Use this to Host the bits of things you think of as a computer. It's like http://www.linode.com","It's handwavy, but EC2 instances are similar to the virtual private servers you'd get at Linode, DigitalOcean or Rackspace. IAM Should have been called Users, Keys and Certs Use this to Set up additional users, set up new AWS Keys and policies. S3 Should have been called Amazon Unlimited FTP Server Use this to Store images and other assets for websites. Keep backups and share files between services. Host static websites. Also, many of the other AWS services write and read from S3. S3 in Plain English    S3 Buckets of Objects  VPC Should have been called Amazon Virtual Colocated Rack Use this to Overcome objections that "all our stuff is o...

Serverless Testing - AWS Lambda

Image
Let's start with what is Serverless Framework? Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Serverless Framework helps you develop and deploy your AWS Lambda functions, along with the AWS infrastructure resources they require. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building sophisticated, event-driven, serverless architectures, comprised of Functions and Events . It manages your code as well as your infrastructure It supports multiple languages (Node.js, Python, Java, and more) AWS Lambda is a compute service that lets you run code without provisioning or managing servers. You can also build serverless applications composed of functions that are triggered by events and automatically deploy them using AWS CodePipelin...