Answers: <p>Installing a box is probably not the best solution, mostly because there's no real need for it.</p>
  
  <p>You should ask for an access to AWS console in customer account with proper rights fitting your responsibilities and maybe setup <a href="https://aws.amazon.com/config/" rel="nofollow noreferrer">AWS config</a>, <a href="https://aws.amazon.com/cloudwatch/" rel="nofollow noreferrer">Cloudwatch</a> for the monitoring and alerting part, <a href="https://aws.amazon.com/cloudtrail/" rel="nofollow noreferrer">Cloudtrail</a> and maybe <a href="https://aws.amazon.com/inspector/" rel="nofollow noreferrer">Amazon Inspector</a> for the audit part.</p>
  
  <p>To ensure machines and AWS services themselves are properly configured you may rely on AWS Config/Amazon Inspector or tools like <a href="https://www.inspec.io/docs/reference/platforms/" rel="nofollow noreferrer">inspec</a> (and here you may or may not need a bastion host on your customer VPC to check other machines, this mostly depends on the agreement you have with customer about direct links/VPN)</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-06-28T15:31:25.467Z
Answers: 2018-06-28T15:31:25.467Z
Answers: Tensibai
Body: <p>I work for a managed services company and am working out a plan to retrofit our customer support machines to support AWS in a general way.  </p>
  
  <p>We use Ansible and lots of ssh port forwarding to connect to traditional, non-cloud, boxes (Windows, Linux, AIX, Firewalls, routers, UC, other Cisco stuff).  </p>
  
  <p>Beyond the AWS CLI, what tools should I deploy to my Linux and Windows support boxes for managing, monitoring and troubleshooting AWS that are different than the traditional tools? </p>
  
Comments: CC BY-SA 4.0
Comments: 2018-06-28T15:13:14.317Z
Comments: What kind of AWS resources/services ? What do you really mean by managing/montioring/troubleshooting AWS ? AWS by itself is very vague.
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-06-28T15:19:27.277Z
Comments: @tensibai that's pretty much what performing [managed services](https://en.wikipedia.org/wiki/Managed_services) is.  The AWS resources are whatever our customers want out of AWS (probably enterprisey business stuff, not the esoteric stuff.  Everything from S3, SNS, SQS, EBS, Lambda, Glacier, Databases, Redshift.
Comments: Peter Turner
Tags: <amazon-web-services><toolchain>
Title: What tools should I deploy to support AWS for a Managed Services company?
UserDisplayName: Peter Turner
ThreadText: # What tools should I deploy to support AWS for a Managed Services company?
  
  (Asked by: username_0 on 2018-06-28)
  
  I work for a managed services company and am working out a plan to retrofit our customer support machines to support AWS in a general way.
  
  We use Ansible and lots of ssh port forwarding to connect to traditional, non-cloud, boxes (Windows, Linux, AIX, Firewalls, routers, UC, other Cisco stuff).
  
  Beyond the AWS CLI, what tools should I deploy to my Linux and Windows support boxes for managing, monitoring and troubleshooting AWS that are different than the traditional tools?
  
  **Tags:** amazon-web-services, toolchain
  
  > **Comments:**
  > **username_1**: What kind of AWS resources/services ? What do you really mean by managing/montioring/troubleshooting AWS ? AWS by itself is very vague.  
  > **username_0**: @username_1 that's pretty much what performing [managed services](https://en.wikipedia.org/wiki/Managed_services) is.  The AWS resources are whatever our customers want out of AWS (probably enterprisey business stuff, not the esoteric stuff.  Everything from S3, SNS, SQS, EBS, Lambda, Glacier, Databases, Redshift.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-06-28. Score: 1
  
  Installing a box is probably not the best solution, mostly because there's no real need for it.
  
  You should ask for an access to AWS console in customer account with proper rights fitting your responsibilities and maybe setup [AWS config](https://aws.amazon.com/config/), [Cloudwatch](https://aws.amazon.com/cloudwatch/) for the monitoring and alerting part, [Cloudtrail](https://aws.amazon.com/cloudtrail/) and maybe [Amazon Inspector](https://aws.amazon.com/inspector/) for the audit part.
  
  To ensure machines and AWS services themselves are properly configured you may rely on AWS Config/Amazon Inspector or tools like [inspec](https://www.inspec.io/docs/reference/platforms/) (and here you may or may not need a bastion host on your customer VPC to check other machines, this mostly depends on the agreement you have with customer about direct links/VPN)
  
  
  ---
  
  