Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Simplifying Hybrid Cloud Adoption with AWS

You're reading from   Simplifying Hybrid Cloud Adoption with AWS Realize edge computing and build compelling hybrid solutions on premises with AWS Outposts

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781803231754
Length 252 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Frankie Costa Negro Frankie Costa Negro
Author Profile Icon Frankie Costa Negro
Frankie Costa Negro
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1: Understanding AWS Outposts – What It Is, Its Components, and How It Works
2. Chapter 1: An Introduction to AWS Outposts FREE CHAPTER 3. Chapter 2: AWS Outposts Anatomy 4. Chapter 3: Pricing, Ordering, and Installation 5. Part 2: Security, Monitoring, and Maintenance
6. Chapter 4: Operations and Working with Outposts Resources 7. Chapter 5: Security Aspects in Outposts 8. Chapter 6: Monitoring Outposts 9. Part 3: Maintenance, Architecture References, and Additional Information
10. Chapter 7: Outposts Maintenance 11. Chapter 8: Architecture References 12. Index 13. Other Books You May Enjoy

Outposts Maintenance

Monitoring your Outposts is a critical administrative task. Outposts resources are finite, especially if you are used to the virtually unlimited capacity of an AWS Region. Customers can make the mistake of not planning the AWS Outposts capacity and run into an Insufficient Capacity error whenever it runs out of capacity to provision resources. Additionally, service link interruptions, as well as S3 and EBS (Elastic Block Store) consumption, must be monitored.

If you have an established monitoring practice, you may be able to proactively react before something bad happens most of the time. Generally, you will be able to fix the cause of alarm yourself, for example, shutting down non-productive instances, deleting stale volumes, or deleting unnecessary S3 objects in a bucket.

However, as AWS CTO Werner Vogels said, “Everything fails, all the time.” It’s an inconvenient truth that any physical hardware will inevitably degrade to a point...

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