In Part 1: What is Serverless? I talked about how one of the biggest pros to a serverless architecture is how well it scales and how high availability is baked in. In this post I’ll go over: How a traditional highly available scalable architecture works, How a scalable serverless architecture works, How you can benefit from a serverless architecture.

In this post we’ll answer the following questions: What is serverless architecture? (and what it’s not), What are the pros & cons of serverless?

One of the biggest challenges in a self-provisioned, public cloud environment like Amazon Web Services (AWS) is finding the right balance between resources, performance, and cost. With no initial visibility into usage stats, AWS customers tend to overprovision compute, storage, and database resources to cushion sudden spikes in demand. If users could see resource usage, they'd be able to determine if the numbers provisioned are really in line with the application workload.

Developers working hand in hand with IT professionals is vitally important to maintaining stable application environments with mininal errors. Ideally, they work in the same environment. This is called DevOps. Learn why DevOps and collaboration is necessary.

Function as a service (FaaS) products like AWS Lambda, Azure Functions, and Google Cloud Functions have instigated a paradigm shift in the way Ops teams provision and manage their organization's infrastructure. With everyday administrative tasks like provisioning, patching, maintaining compliance, and configuring operating systems all being abstracted away, your Ops team only has one task to work on - writing world-class code.

This small release introduces custom stages, stage-level configuration overrides, instant rollbacks and a few other refinements for Up the serverless deployment tool.

As you probably know, Site24x7's AWS monitoring capabilities provide complete visibility into resource utilization and performance for key compute resources, storage, and database services powering your application in the Amazon Web Services (AWS) cloud. From here on out, you'll have the power to not only identify issues that might affect application performance, but also automatically invoke operational tasks across multiple AWS resources to resolve them quickly.

In our previous posts, I showed you how to copy your DB and Aurora snapshots to ensure they are preserved beyond the lifetime of your RDS instance. However, those copies were simply second copies in the same region as the original. In this post, I’ll show you how to copy your RDS snapshots to a second region for extra protection. Please note that I will restrict this post to unencrypted snapshots. Copying encrypted snapshots is more involved, so I’ll show that in a separate post.

RDS snapshots can be unencrypted or they can be encrypted at rest. Today, best practice is to use encryption-at-rest on your RDS instances and clusters, and to encrypt your RDS snapshots. When you create an RDS snapshot from an RDS instance or cluster, the resulting snapshot will be encrypted if the source instance or cluster is encrypted. But if the source is not encrypted, then your RDS snapshot is not encrypted. When you create an RDS snapshot, you are not given the option to encrypt it.