0

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?

Improve this question
2
  • What kind of AWS resources/services ? What do you really mean by managing/montioring/troubleshooting AWS ? AWS by itself is very vague.
    – Tensibai
    Commented Jun 28, 2018 at 15:13
  • @tensibai that's pretty much what performing 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.
    – Peter Turner ♦
    Commented Jun 28, 2018 at 15:19

1 Answer 1

Reset to default
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, Cloudwatch for the monitoring and alerting part, Cloudtrail and maybe Amazon 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 (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)

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.