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


AWS RDS is a highly available, scalable, and managed database service. It's a cost-efficient, resizable capacity database wherein AWS manages common database administration tasks.

As we know, the database is the most critical component for any application. That's why we always define a private subnet to host a database and only allow connections from the specific subnet or IP on a specific database port.

In the case of RDS, we apply the same, although we have more security components to ensure the security and safety of the database instance.

For RDS, we have two models to provision:

  • Single Availability Zone: In this model, you have only one database (master database) running in a single Availability Zone (AZ). However, it's not fault-tolerant, which means that if there is any problem or maintenance activity being performed on the database, your application can face downtime.
  • Multi AZ: In this model, you have two database instances running in two different AZs in master and standby fashion...