## Case Study : DevOps on AWS Services We Use
Tools We Frequently Use
The following table lists several of the tools that we typically use in implementing solutions for our customers. Though representative, it is by no means comprehensive.
Deployment & Management AWS CloudFormation, AWS OpsWorks, AWS CodeDeploy, AWS CodePipeline, AWS CodeCommit, AWS SDKs, AWS CLI, Jenkins, Github
Compute & Containers Amazon EC2, AWS Auto Scaling, AWS Elastic Load Balancing, Docker, Lambda, Packer, Vagrant
Storage & Content Delivery Amazon Simple Storage Service (S3), Amazon CloudFront, Nexus
Database AWS ElastiCache, Amazon Relational Database Service (RDS), Amazon DynamoDB
Networking Amazon Virtual Private Cloud (VPC), Amazon Route 53, AWS Direct Connect
Administration & Security AWS Identity and Access Management (IAM), AWS Trusted Advisor, CloudWatch, CloudWatch Logs, AWS Support, Janitor Monkey, New Relic, AWS CloudTrail, Cloudability, NetflixOSS
Application Services & Testing API Gateway, Amazon Simple Email Service (SES), SNS, SQS, SWF, Chef, Puppet, Ansible, Server Spec, TestKitchen, Cucumber, Chaos Monkey, JMeter, CodeClimate, Sonar.
While there are many tools listed, the source assets that are committed to your version-control repository typically include only the following:
Serverspec or Cucumber tests (in Ruby)
Chef, Ansible or Puppet scripts (in Ruby/Python or external DSL)
Sree - Founder/MD/Chief Cloud & DevOps Architect
Sree is an evangelist and thought leader in the Continuous Delivery and DevOps space. In addition to being a Cloud Architect, he also imparts training in AWS, Docker and other DevOps related technologies. Sree's core speciality is in building scripted, version-able, repeatable, auto-scaling, load-balanced and self-healing infrastructures. Sree also works in server-less architectures using AWS Lambda service and Internet of Things (IOT). Sree is also an Amazon Certified AWS Cloud Architect with 15+ years of server experience.
Know more about the author.