![Share on Facebook Facebook](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/social/regular/64x64/facebook.png)
![Share on Twitter twitter](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/social/regular/64x64/twitter.png)
![Share on Google+ google_plus](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/social/regular/64x64/google_plus.png)
![Share on Linkedin linkedin](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/social/regular/64x64/linkedin.png)
![Share by email mail](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/social/regular/64x64/mail.png)
![feather](https://www.deryasezen.com/wp-content/plugins/social-media-feather/synved-social/image/icon.png)
If you go towards DevOps, automated provisioning, you definetely will need to do things in automation.
Here is the command line, in case you need the new automated provisioned server to be added in your RDS security group:
aws rds rds-authorize-db-security-group-ingress –db-security-group-name mydbsecuritygroup –cidrip 192.168.1.10/27