It is a capability of the AWS Systems manager that allows you to remotely maintain and manage the servers. Managed servers are servers that have been configured for use by SSM service.<\/p>\n
With Run Command, we can perform:<\/p>\n
- \n
- Adhoc exceptions. and<\/li>\n
- one-time configuration changes<\/li>\n<\/ul>\n
Follow the guide below for a demo on how to use the Run command.<\/p>\n
Prerequisites:\u00a0<\/strong><\/h2>\n
You will need an AWS Account to begin with. If you are new to AWS or do not have an account, you can create one using this link:<\/p>\n
https:\/\/aws.amazon.com\/free\/<\/a><\/p>\n
Here is a step-by-step guide to use the run command:\u00a0\u00a0<\/strong><\/p>\n
\u00a0Create an IAM role for EC2-SSM:\u00a0<\/strong><\/h2>\n
- \n
- Go to IAM Dashboard in AWS Console
\nhttps:\/\/console.aws.amazon.com\/iam\/home?region=us-east-2\u00a0\u00a0<\/a>
\n![\"IAM](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS1.png\")
\n<\/a><\/li>\n- Click on Roles<\/strong> on the left pane and click Create role
\n![\"Create](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS2.png\")
\n<\/a>
\n<\/strong><\/li>\n- Choose the AWS Service (EC2) and click next permissions
\n![\"Create](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS3.png\")
\n<\/a><\/li>\n- Choose AmazonSSMFullAccess<\/a> and click on next
\n![\"Amazon](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS4.png\")
\n<\/a><\/li>\n- Give a name for the role and Click Create role
\n![\"Create](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS5.png\")
\n<\/a><\/li>\n<\/ol>\nCreate Instances with the above roles attached:<\/strong><\/h2>\n
- \n
- Go to EC2 Dashboard in AWS<\/li>\n
- Click on Launch Instance, Choose the ubuntu AMI (ami-0b9064170e32bde34)<\/li>\n
- In Instance type, choose T2.micro and click on next
![\"ubuntu](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS6.png\")
\n<\/a><\/li>\n- In Instance Configure, let the instance count by 1.In the IAM role, choose the role you created in the previous task
\n![\"IAM](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS7.png\")
\n<\/a><\/li>\n- Keep default values for storage and move to the next stage.<\/li>\n
- Add tags to the Instance
\n![\"Adding](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS8.png\")
\n<\/a><\/li>\n- Review and Create the instance.<\/li>\n<\/ol>\n
Create a VPC Endpoint:\u00a0<\/strong><\/h2>\n
- \n
- Go to VPC Console,<\/li>\n
- Choose Endpoints towards the left pane
\n![\"Endpoints\"](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS9.png\")
\n<\/a><\/li>\n- Click on Create Endpoint
\n![\"Creating](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS10.png\")
<\/a><\/li>\n- Choose Service Category: AWS Service and select the Servicecom.a
\nmazonaws.us-east-2.ssm<\/a>
\n![\"AWS](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWSnew.png\")
<\/a>
\n![\"Service](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS11.png\")
\n<\/a><\/li>\n- Choose the VPC, subnet to which you want to create an endpoint<\/li>\n
- Click on create Endpoint
\n![\"AWS](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS12.png\")
<\/a>
\n![\"Create](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS13.png\")
\n<\/a><\/li>\n<\/ol>\nCreate a run command and execute the command:<\/strong><\/h2>\n
- \n
- Go to System manager console<\/li>\n
- Towards the left pane, choose the Run Command Service
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS14.png\")
\n<\/a><\/li>\n- Click on the Run command
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS15.png\")
\n<\/a><\/li>\n- Choose the Command Document that is compatible with the type of end servers ( Linux \/ windows)In this demo,\u00a0 We are using Linux servers, so I choose\u00a0AWS-ConfigureAWSPackage<\/a>
\n<\/a>![\"AWS-Configure-AWSPackage\"](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS16.png\")
<\/a> <\/li>\n- Scroll down, in command parameters,
\na. Action, (install)
\nb. Installation type:
\nc. Name: Provide the valid Package name ( eg: AmazonCloudWatchAgent, AwsEnaNetworkDriver)
\n![\"AWS-Configure](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS17.png\")
\n<\/a><\/li>\n- Targets: there are 3 ways you can identify the end servers:
\na. By specifying tags
\nb. Manually choosing
\nc. Choosing the resource GroupClick on Choose instance manually
\n![\"Choose](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS18.png\")
\n<\/a><\/li>\n- In the output options, Uncheck, enable S3 output
\n![\"S3](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS19.png\")
\n<\/a><\/li>\n- Click on the run command.
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS20.png\")
\n<\/a>You will notice the execution of the command.![\"Execution](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS21.png\")
<\/a>
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS22.png\")
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS23.png\")
<\/a>
\n![\"Run](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/AWS24.png\")
\n<\/a><\/li>\n- Verify:
\n<\/strong><\/p>\nsudo systemctl start amazon-cloudwatch-agent\r\nsudo systemctl status amazon-cloudwatch-agent<\/pre>\n<\/li>\n<\/ol>\n
Hope this blog has shed light on the uses of \u2018run command\u2019, and how it can be used to manage and maintain the servers. It can be used to perform patch updates\u00a0to the servers without SSH into the machine easily and securely.
\nTo learn more about managing infrastructure on AWS<\/strong>, then here is a step-by-step guide<\/strong><\/a> for you.<\/p>\nFeel free to drop any queries and our team of experts will get back to you very soon.<\/p>\n
Cheers!<\/p>\n","protected":false},"author":234,"featured_media":8509,"parent":0,"comment_status":"open","ping_status":"open","template":"","blog_category":[3606,3607],"user_email":"shylaj@cloudthat.com","published_by":"324","primary-authors":"","secondary-authors":"","acf":[],"_links":{"self":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/8464"}],"collection":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/users\/234"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/comments?post=8464"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/8464\/revisions"}],"predecessor-version":[{"id":46231,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/8464\/revisions\/46231"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/media?parent=8464"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog_category?post=8464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Click on the Run command
- Click on Create Endpoint
- In Instance Configure, let the instance count by 1.In the IAM role, choose the role you created in the previous task
- Click on Roles<\/strong> on the left pane and click Create role
- Go to IAM Dashboard in AWS Console