AWS offers a number of tools and services to help developers, DevOps, and operations teams manage the work processes and the security of their code and data. In the AWS console, these tools fall under a number of different headings. Developer tools, code tools, security, identity and compliance, and finally analytics. We obviously don't have enough time to touch on the 30-some services contained within these headers, so instead I'll give you a really quick rundown of the different types of services offered. If you'd like to go into more detail, CloudAcademy as always offers further courses and labs designed to teach some of these very specific tools.

First up, let's take a look at the AWS developer tools. Most important to us are CodeCommit, CodeBuild, CodeDeploy, and CodePipeline. Comprised together, these services allow your dev team to run a modern, agile development process featuring continuous integration and deployment. CodeCommit lets you host private Git repositories giving you the full power of Git behind your secure cloud resources. CodeBuild is a system that automatically compiles code that you give it. And then can run tests on that code to ensure that it's working properly. CodeDeploy can take a built system and automatically deploy it to your AWS resources, making updating your system much less labor intensive and more reliable. Finally, CodePipeline ties all of these tools together. It allows for a full autonomous continuous integration and deployment process. So using CodePipeline, you can create a system where whenever you check in code-to-code commit, CodeBuild will automatically build it and test it, and if it then passes those tests, CodeDeploy will automatically deploy it to your AWS servers. CodePipeline also ties it into third-party tools. So if you want to use GitHub instead of CodeCommit, but will use CodeBuild and CodeDeploy, CodePipeline still has you covered.

Next we'll take a look at the AWS management tools. CloudWatch, CloudFormation, and CloudTrail offer advanced provisioning, login, and analytics of your AWS services. This way you can programmatically define what is running on AWS, as well as set up alerts to notify your team if any part of our app goes down, and look through logs to see who did what on your AWS system, such as when troubleshooting. Even if you're not writing code, going through these CloudAcademy courses and labs for these tools can be really useful.

AWS Identity and Access Management, or IAM, lets you create users and roles for your AWS service. This way you can give your employees access to only the parts of AWS that they actually need. For instance, developers might be allowed to use CodeCommit and to deploy EC2 instances. But only sysadmin people will need to create new VPCs, and public facing resources. Identity and Access Management would let you set up all of these rules into different roles and then quickly assign those roles to people,igving them only access to what they need. This is a great way to empower your employees to be autonomous, while preventing costs from spinning out of control.

Finally, Amazon offers a suite of analytics tools that help you monitor not only your AWS services and usage, but also to look inside your app to see what it's doing. User logging, data mining, and more are possible through these analytics tools. These services can replace having to run analytics code on your servers along side your app. Or sending that data to third-party cloud services. I'd recommend looking further at the courses and labs on Athena, EMS, Mobile Analytics and Elastic Search if you'd like to learn more.