Book Image

Cloud Security Automation

By : Prashant Priyam
Book Image

Cloud Security Automation

By: Prashant Priyam

Overview of this book

Security issues are still a major concern for all IT organizations. For many enterprises, the move to cloud computing has raised concerns for security, but when applications are architected with focus on security, cloud platforms can be made just as secure as on-premises platforms. Cloud instances can be kept secure by employing security automation that helps make your data meet your organization's security policy. This book starts with the basics of why cloud security is important and how automation can be the most effective way of controlling cloud security. You will then delve deeper into the AWS cloud environment and its security services by dealing with security functions such as Identity and Access Management and will also learn how these services can be automated. Moving forward, you will come across aspects such as cloud storage and data security, automating cloud deployments, and so on. Then, you'll work with OpenStack security modules and learn how private cloud security functions can be automated for better time- and cost-effectiveness. Toward the end of the book, you will gain an understanding of the security compliance requirements for your Cloud. By the end of this book, you will have hands-on experience of automating your cloud security and governance.
Table of Contents (15 chapters)
Title Page
Packt Upsell

Automate deployment – AWS OpsWorks

AWS OpsWorks provides configuration management using managed Chef and Puppet instances. This helps you automate your deployment, configuration, and management processes.

In AWS OpsWorks, we create a stack that is a collection of resources such as your web server, load balancer, and database servers. After that, we have a layer where we define the configuration of components. As per AWS:

"A layer is a blueprint for a set of Amazon EC2 instances. It specifies the instance's settings, associated resources, installed packages, profiles, and security groups."

After adding the layer, we have a list of the instances that will be running our workload, and then the application will be deployed on the infrastructure. Finally, there is monitoring, which monitors the infrastructure.

The only limitation with OpsWorks is that you cannot do the SSH into instances or do any custom configuration manually.

Let's see how easy it is to deploy a sample Node.js application using...