{"id":18824,"date":"2015-04-07T16:26:02","date_gmt":"2015-04-07T10:56:02","guid":{"rendered":"https:\/\/2thenew.today\/blog\/?p=18824"},"modified":"2015-09-17T16:46:10","modified_gmt":"2015-09-17T11:16:10","slug":"chef-recipe-to-change-pem-file-of-running-ec2-instances-and-adding-a-new-user-to-all-the-instances-and-give-sudo-privileges","status":"publish","type":"post","link":"https:\/\/2thenew.today\/blog\/chef-recipe-to-change-pem-file-of-running-ec2-instances-and-adding-a-new-user-to-all-the-instances-and-give-sudo-privileges\/","title":{"rendered":"CHEF recipe to change pem file of running ec2 instances and adding a new user to all the instances and give sudo privileges"},"content":{"rendered":"

This blog is to enable AWS chef professionals<\/a> to change pem of running servers or to add a new user with sudo privileges to an EC2 server farm using chef<\/a>. The post actually refers to a production usecase in which there is a huge number of instances running on single or multiple pem files which needed to be replaced instantly to a single pem file for all the servers without any downtime. This can be done to overcome security issue, for example, the pem file is being rotated to different peoples or the person who was managing these servers and there keys left the organization.<\/p>\n

Quick and easy resolution for above concern is listed below,<\/p>\n

1) This blogpost assumes pre existing CHEF test environment of 3 ubuntu servers, a chef server, a chef client and a chef workstation. For more information on setting up above mentioned test environment, please refer link below,
\nhttps:\/\/www.digitalocean.com\/community\/tutorials\/how-to-install-a-chef-server-workstation-and-client-on-ubuntu-vps-instances<\/a><\/p>\n

2) Create a new keypair using AWS console and download the new pem file,<\/p>\n

3) Obtain a public key against recently downloaded pem key using below command,\"publickeygenerate\"<\/a>The command will ask for the location of private key and will give the public key against that private key on stdout. Copy and save that into a file, with filename “authorized_keys” and put this file inside, ‘$HOME\/chef-repo\/cookbooks\/changekeypair\/files\/default\/’ directory.<\/p>\n

\"cheffilesloc\"<\/a><\/p>\n

3) Now, we push this public key file inside .ssh folder of all the instances using chef recipe below,\"changekeypairrecipe\"<\/a>Above recipe will push the “authorized_keys” file to all the chef clients and change its permissions to 600, so that public key held by the clients earlier will be replaced with a new public key. Now users having old private key cannot log into the system.<\/p>\n

To add a new user to a server farm with sudo privileges, following steps are to be followed,<\/strong><\/p>\n

1) Create a password shadow hash because original password should not be written in plain text in our recipe.\"openssl\"<\/a><\/p>\n

2) create a new cookbook and copy the recipe listed below,\"adduserrecipe\"<\/a>Above recipe will create a new user with username “intelligrape” and password as “theplaintextpassword” and add this user to sudoers.<\/p>\n

Thanks and regards
\nSharad Aggarwal<\/p>\n","protected":false},"excerpt":{"rendered":"

This blog is to enable AWS chef professionals to change pem of running servers or to add a new user with sudo privileges to an EC2 server farm using chef. The post actually refers to a production usecase in which there is a huge number of instances running on single or multiple pem files which […]<\/p>\n","protected":false},"author":176,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[1174],"tags":[],"class_list":["post-18824","post","type-post","status-publish","format-standard","hentry","category-aws-2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t