This course provides detail on the AWS Management & Governance services relevant to the AWS Certified Developer - Associate exam.
- Learn how AWS AppConfig can reduce errors in configuration changes and prevent application downtime
- Understand how the AWS Cloud Development Kit (CDK) can be used to model and provision application resources using common programming languages
- Get a high-level understanding of Amazon CloudWatch
- Learn about the features and use cases of the service
- Create your own CloudWatch dashboard to monitor the items that are important to you
- Understand how CloudWatch dashboards can be shared across accounts
- Understand the cost structure of CloudWatch dashboards and the limitations of the service
- Review how monitored metrics go into an ALARM state
- Learn about the challenges of creating CloudWatch Alarms and the benefits of using machine learning in alarm management
- Know how to create a CloudWatch Alarm using Anomaly Detection
- Learn what types of metrics are suitable for use with Anomaly Detection
- Create your own CloudWatch log subscription
- Learn how AWS CloudTrail enables auditing and governance of your AWS account
- Understand how Amazon CloudWatch Logs enables you to monitor and store your system, application, and custom log files
- Explain what AWS CloudFormation is and what it’s used for
- Determine the benefits of AWS CloudFormation
- Understand what each of the core components are and what they are used for
- Create a CloudFormation Stack using an existing AWS template
- Learn what VPC flow logs are and what they are used for
- Determine options for operating programmatically with AWS, including the AWS CLI, APIs, and SDKs
- Learn about the capabilities of AWS Systems Manager for managing applications and infrastructure
- Understand how AWS Secrets Manager can be used to securely encrypt application secrets
Once you have credentials set up, it’s time to use the AWS CLI. Remember, with the CLI, all you’re doing is making API calls that are structured using a particular syntax. The syntax is as follows:
Each command is broken up into four parts. The first part that remains consistent regardless of the command you type is the “aws” keyword. This is how the CLI knows you’re calling AWS.
The second part is the service you’re calling, such as EC2, DynamoDB, S3, and more.
Then you have the operation, which is the API call you’d like to make. For example, if you want to list your EC2 instances, you would use the describe-instances API call. Or if you wanted to create a dynamoDB table, you’d want to use the aws dynamodb create-table operation.
After the operation, is the final part, which is the parameters you write to that API call. These parameters change based on the operation you run. For example, if you ran the ‘aws dynamodb create-table’ command, you would specify a parameter of ‘--table-name’, then you can specify a table name, such as cars. Or if you wanted to list details about a particular EC2 instance, you would use the ‘aws ec2 describe-instances’ operation with a parameter to specify the instance id using –instance-ids, and then specify an instance id.
Notice that each of these parameters is prefixed by two dashes.
All right, let’s take one of these commands and run it in the terminal. For example, I’ll run aws ec2 describe-instances –instance-ids and then I’ll specify an instance ID I know is in my account.
Once I press enter and run this command, I get a response in the default output format that I specified in my default profile. In this case, you can see the output is in the YAML format, and it lists all details regarding the instance that has the ID that I specified. By pressing the down key or enter, I can go through each line of the response. Then, I can press the letter q to exit the response.
If you get stuck with structuring commands at any point, there is help functionality built into the CLI. For example, you can type in aws help and it will provide you a list of options, as well as a list of services you can use.
You can scroll on this list and see that there’s a service you may want to use in the future. Here, I see the service CE. Maybe I don’t know what that's abbreviated for - so I can take the help functionality one step further and use it with the service, so now the command would be ‘aws ce help’. This will provide a list of all operations I can perform with the service.
You can then even take this one step further, and use help on the operation. Let’s take the first operation in the list, in this case, create-anomaly-monitor and use the command ‘aws ce create-anomaly-monitor help’. Then you can see what parameters this operation takes and any additional information about the operation you may need to know.
So if you ever need some light bedtime reading, consider reading through the descriptions for one of these parameters - this information will definitely put you straight to sleep. Okay, that’s all for this one - see you next time.
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.