Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
AWS Certified Advanced Networking - Specialty Exam Guide

You're reading from   AWS Certified Advanced Networking - Specialty Exam Guide Build your knowledge and technical expertise as an AWS-certified networking specialist

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781789952315
Length 308 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Marko Sluga Marko Sluga
Author Profile Icon Marko Sluga
Marko Sluga
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: Introduction FREE CHAPTER
2. Overview of AWS Certified Advanced Networking - Specialty Certification 3. Section 2: Managing Networks in AWS
4. Networking with the Virtual Private Cloud 5. VPC Network Security 6. Connecting On-Premises and AWS 7. Section 3: Managing and Securing Network-Attached Platform Services in AWS
8. Managing and Securing Servers with ELB 9. Managing and Securing Content Distribution with CloudFront 10. Managing and Securing the Route 53 Domain Name System 11. Managing and Securing API Gateway 12. Section 4: Monitoring and Operating the AWS Networks
13. Monitoring and Troubleshooting Networks in AWS 14. Section 5: Network automation in AWS
15. Network Automation with CloudFormation 16. Section 6: The Exam
17. Exam Tips and Tricks 18. Mock Tests 19. Assessments 20. Other Books You May Enjoy

Monitoring the API gateway

Similarly to the ELB and CloudFront, we can monitor the performance of the API gateway by selecting the metrics related to each API. In this example, we have chosen to select all the metrics of the Test API. The API was tested externally during a 15-minute EST window and as we can see, traffic was recorded during that time. We have chosen to examine both 400 and 500 error codes, the latency of the API, and the integration latency, which measures the performance from the API gateway to the backend. We also have a count metric selected, but the counts are really small so they are not registering well on this chart:

However, what we can see from this chart is a nice correlation between the integration latency and the overall latency of the API. This means that our API is performing well and the larger chunk of the latency is due to the backend responding...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image