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
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Simplifying Hybrid Cloud Adoption with AWS
Simplifying Hybrid Cloud Adoption with AWS

Simplifying Hybrid Cloud Adoption with AWS: Realize edge computing and build compelling hybrid solutions on premises with AWS Outposts

eBook
€25.99 €28.99
Paperback
€35.99
Subscription
Free Trial
Renews at €18.99p/m

What do you get with Print?

Product feature icon Instant access to your digital copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Redeem a companion digital copy on all Print orders
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
OR
Modal Close icon
Payment Processing...
tick Completed

Shipping Address

Billing Address

Shipping Methods
Table of content icon View table of contents Preview book icon Preview Book

Simplifying Hybrid Cloud Adoption with AWS

An Introduction to AWS Outposts

After prevailing over the initial hype cycle, the cloud has truly evolved as the de facto platform of choice to run IT services, by overcoming what seemed to be an insurmountable gap between customer premises and the cloud. There have been several attempts to bridge both these worlds.

The term hybrid was initially coined as a reference to solutions that purported to operate as a cloud would in the customer data center. Ever since then, several of these kinds of denominations in the Information Technology realm have evolved and consolidated into what is now referred to as the edge. Amazon Web Services (AWS) now delivers managed cloud infrastructure in the form of AWS Outposts, which lives in the very same edge.

This chapter explores the concept of the edge and then transitions into exploring the key concepts and terminology of AWS Outposts. Finally, we will wrap up with the use cases for this product.

In this chapter, you will cover the following:

  • Identifying the edge space in the Information Technology domain
  • Understanding the purpose of AWS Outposts
  • Identifying how Outposts fits into the edge space
  • Understanding what business problems Outposts solves

Defining hybrid, edge, and rugged edge IT spaces

Amazon as an enterprise has rapidly evolved from the challenges it endured that could neither have been addressed technically nor economically at the time when running large-scale applications. This fact may have led us to conclude that AWS was unlikely to develop a product that would resemble a traditional server rack you could find in any regular data center.

As with any market or industry, things change. New technologies arise, paradigms shift, and new trends pose new challenges and require new solutions. It was no different from the way enterprises consume corporate IT services. In the past couple of years, the hybrid phenomenon gained a lot of momentum to become one of the preferred ways for enterprises to run their business.

This is not strange by any means. You have the start-up sector, which is cloud-native and certainly does not see any reason to have a physical infrastructure of its own. Start-up companies only need a solid connection to the internet and personal equipment to carry out the development work and the administrative work with cloud providers.

At the other end of the spectrum, we had companies over the past few decades doing IT the traditional way, operating fully on-premises. But in recent years, the market has developed the perception that it does not need to be one way or the other.

Back then, your option to run IT infrastructure outside your own local data center relied on offerings from third-party specialized data center providers. Offerings such as hosting, location, and co-location were extremely popular at the time, and are still available today. If you could order a good leased line to connect your site(s) with the provider’s site, any of the options would be available to you.

At best, you could have one of these providers supplying and managing all the necessary equipment to run your business while leveraging the OPEX financial model. Your IT team would take care of services and Line-Of-Business (LOB) applications and you would be in business. For some companies, the CAPEX model made sense as purchased equipment became assets for the company and added value to the balance sheets.

Times change and the advent of the cloud challenged the constraints and limitations of traditional data centers. Andrew Jassy, currently the president and CEO of Amazon, in an interview for the site TechCrunch (https://techcrunch.com/2016/07/02/andy-jassys-brief-history-of-the-genesis-of-aws/), described how AWS was conceived to be the Operating System for the internet at its inception, designed to reliably run applications and services at massive scale.

When AWS came to life in 2006, it wasn’t too clear that it would become what it is today. From humble beginnings with no clear ambition and marketing to turning into a cloud behemoth just 15 years later, AWS and the cloud were just yet another technology trend that remained to prove reliable and solid. The early adopters pioneered the new cloud paradigm and got their feet wet with infrastructure and services that existed beyond their reach when they could not even schedule a visit to the data center.

Adopting cloud services was an exercise of a dual IT landscape design. Either one given service lived on-premises or lived in the cloud. The connection between the two was basically to exchange data for migration or backup and, eventually, very simple interaction between systems with multiple components. It was difficult to consider a three-tier architecture where one of the tiers would sit in the cloud with the other on-premises. Internet bandwidth was scarce, connections were not strongly reliable, and you often had to resort to VPNs for security because it was challenging to procure dedicated links to directly connect with cloud providers at the time.

As the cloud trend reached critical mass and established itself as a valid path, businesses faced a new reality: the cloud had to be considered within their technology plans and a thorough assessment of the IT landscape was necessary to devise a strategy that could somehow encompass cloud offerings and to a serious extent. A vague statement about the cloud just being hype was no longer acceptable to business owners – it was here to stay.

This new way of consuming corporate IT services was dubbed hybrid cloud and described as a combination of cloud services running alongside the traditional on-premises data center solutions. Not surprisingly, the point of view of this model was oriented from the data center out into the outside world, stretching toward the cloud, because it was primarily articulated by on-premises infrastructure providers whose vision centered around the traditional model.

The possibility of a business going all in with the cloud while shutting down all traditional data centers was somewhat far-fetched, but it was delineated as a real alternative. While it is clear that not all workloads will be a fit for the cloud and some may remain on-premises, a significant shift of IT infrastructure to the cloud can realistically be envisioned.

Further developments in this trend revealed that one piece of the puzzle was missing. If considered as a binary choice, an on-premises data center versus the cloud, any move could be a significant risk because there was no middle ground. IT teams were facing an all-or-nothing situation where systems with multiple components would have to be moved as a whole, likely in one go.

Evaluating how a system would perform when running on the cloud was complex because tests had to be carried out in terms of production size and capacity without close contact with all other surrounding systems and services. Even with extensible tests, a cutover date was an event of high significance, full of anxiety, and likely to have a long maintenance window. Clearly, an intermediary infrastructure bridging both worlds would be beneficial.

Initial attempts to fill this gap were made by traditional software providers, offering solutions to be run on-premises that used the type of technologies and solutions offered by cloud providers. This was the private cloud – one attempt to bring the cloud operational model to customer on-premises data centers. Running on their own infrastructure at their data centers or co-location sites, the promise was to leverage cloud-like services and technologies at your facility or closer to you.

It was a good approach and makes good sense. IT teams can become familiar with cloud technologies and how system operations are carried out in the cloud while relatively comfortable at home with their own equipment, learning at their own pace. As IT professionals became familiar with the cloud model, the transition to a cloud provider could be facilitated as the value and challenges became clearer.

Even with a good portion of the market leveraging the private cloud offering, there was still the inescapable fact that on-premises, you could not leverage the cloud-specific services and technologies. Moreover, you would never benefit from the scalability and economies of scale offered by cloud providers. It was you running cloud-like services and still managing the necessary infrastructure.

Cloud adoption has gained significant momentum in recent years and we can see now how start-up companies are said to be born in the cloud or cloud natives. These businesses would have never considered creating their products and applications using the on-premises infrastructure. Such offerings would not be possible if they were conceived within the limitations and paradigms of traditional technologies.

Systems have become increasingly complex, made up of many moving parts as opposed to the monolithic approach of yesterday. Technologies favored distributed systems and highly specialized and smaller microservices. This movement highly favored the appeal of the cloud, built on top of pay-per-use, faster innovation, elasticity, and scale. For more information, refer to this video (https://www.youtube.com/watch?v=yMJ75k9X5_8), The Six Main Benefits of Cloud Computing.

Fast forward to today and considering the latest world developments, the cloud has completely solidified its position and, to be fair, has exploded in adoption, which was significantly accelerated because of the challenges imposed by recent events such as the pandemic. The cloud model was battle-tested and made it through, to the point that it became the de facto standard model to be considered the foundation of technology.

While the future of the cloud seems to be clear skies, there is another fact that still holds: the vast majority of IT spending is still on traditional infrastructure and data centers. While this seems to be a wonderful opportunity to thrive in a market where the largest chunk of business is yet to be conquered, it also means that the missing key piece to act as the catalyst for the widespread adoption of the cloud is more crucial than ever.

As the next step toward blurring the boundaries between the cloud and the so-called physical world, the concept of a hybrid has been redefined. Hybrid is considered to be this enabler, the indistinguishable middle ground where on-premises and the cloud live together in a harmonic symbiosis where both parties benefit from each other. To amplify that notion, the term edge was added to the vernacular.

What we are now seeing is the original hybrid concept in reverse. Now, it originates in the cloud and branches out to the world in the form of edge nodes, where any given data center is considered to be one of these nodes. Effectively, the cloud aims to be everywhere, encompassing all kinds of businesses and places, powered by the recent advancements in high-speed wireless connectivity through 5G networks and IoT devices and sensors.

To make it clearer, an edge node is considered to be anywhere you could run some form of computing, be it large, small, or tiny. Naturally, a family house, a hospital, a restaurant, a crop field, an underground mine, and a cargo ship are significantly different places in nature. Suitability to accommodate electronic components and connectivity conditions change radically and the mileage of the IT equipment running will vary.

To describe these components better when deployed in harmful and aggressive environments, this space is conceptualized as the rugged edge, where equipment must withstand harsh usage conditions and must incorporate design characteristics and features that allow prolonged, normal operation under those circumstances. Equipment built for this purpose boasts specs that allow for severe thermal, mechanical, and environmental conditions.

Today, cloud companies are challenging themselves to create technologies that will propel the ultra-connected world where technology is pervasive, data is collected massively everywhere, and information is nearly real-time. Hybrid solutions play a fundamental role in this game, paving the way for cloud providers to extend all over the world and become the infrastructure, not one infrastructure.

What is AWS Outposts?

For years, AWS was clear on its messaging that customers should stop spending money on undifferentiated heavy lifting. This is AWS verbatim, as can be seen in the design principles for the Cost Optimization pillar of the AWS Well-Architected Framework (https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html). As it says, racking, stacking, and powering servers fall into this category, with customers advised to explore managed services to focus on business objectives rather than IT infrastructure.

From that statement, it would be reasonable to conclude that AWS would hardly give customers an offering that could resemble the dreaded kind of equipment that needs power, racking, and stacking. The early strides of AWS bringing physical equipment to customers were in the form of the AWS Snow family: AWS Snowball Edge devices and their variants (computing, data transfer, and storage).

It does sport the title of being the first product that could run AWS compute technology on customer premises, being able to deliver compute using specific Amazon Elastic Compute Cloud (EC2) instance types and the AWS Lambda function, locally powered by AWS IoT Greengrass functions. Despite this fact, it was advertised as a migration device that enabled customers to move large local datasets to and from the cloud, supporting independent local workloads in remote locations.

In addition, Snowball Edge devices can be clustered together and locally grow or shrink storage and compute jobs on demand. AWS Snowball Edge supports a subset of Amazon Simple Storage Service (S3) APIs for data transfer. Being able to create users and generate AWS Identity and Access Management (IAM) keys locally, it can run in disconnected environments and has Graphic Processing Unit (GPU) options.

Launched in 2015, the first generation was called AWS Snowball and did not have compute capabilities, which would appear in 2016 when the product was rebranded as Snowball Edge. Today, AWS Snowball refers to the name of the overall service. The specs are impressive, with 100 GB network options and the ability to cluster up to 400 TB of S3 compatible storage. SBE-C instances are no less impressive, featuring 52 vCPUs and 208 GB of memory.

AWS invested a great deal to make the cloud not only appealing but also accessible. Remove that scary thought of having to change something drastically and radically, that awful sensation of having to rebuild the IT infrastructure on top of a completely different platform. AWS even gave various customers a soft landing and easy path to AWS when they announced (https://aws.amazon.com/blogs/aws/in-the-works-vmware-cloud-on-aws/) their joint work with VMware in 2016 to bring its capabilities to the cloud, which debuted in 2017 (https://aws.amazon.com/blogs/aws/vmware-cloud-on-aws-now-available/).

With these capabilities and Edge appended to the service name, it seemed that moving forward, the path was set with Snowball. It was not without surprise that AWS Outposts was announced in November 2018 during Andy Jassy’s keynote at re:Invent. On stage, it was shown as a conceptualized model, but one could clearly see it had the shape and form of a server rack.

AWS Outposts debuted on video in 2019 (https://youtu.be/Q6OgRawyjIQ), introduced by Anthony Liguori, the VP and distinguished engineer at AWS. By that time, it became clear that a server rack was in the making inside AWS and it was targeting the traditional data center realm. However, it was against the AWS philosophy of asking customers to stop spending money on traditional infrastructure. Anyone staring at an AWS Outposts rack could be intrigued.

At re:Invent in 2019, Andy Jassy revealed the use case for Outposts during his keynote. He started by acknowledging some workloads that would have to remain on-premises because even companies who had been strong advocates for cloud adoption had also struggled at times to move certain workloads that proved to be very challenging, and eventually stumbled along their way.

Outposts was characterized as a solution to run AWS infrastructure on-premises for a truly consistent hybrid experience. The feature set was enticing: the same hardware that AWS runs on its data centers, seamlessly connecting to all AWS services, with the same APIs, control plane, functionality, and tools as used when operating in the Region. On top of it, it is fully managed by AWS. In the same opportunity, he showcased one specific Outposts variant for VMware, which was a bold move for a cloud company advocating to stop investing in data centers.

That was not the only announcement targeting the edge space. At that same event, AWS Local Zones and AWS Wavelength were announced. While these offerings fall beyond the scope of this book, it’s worth noting that they weave together to compound an array of capabilities to address the requirements and gaps in the edge space and get a strong foothold in it. So, it suffices to say, AWS Local Zones are built using slightly modified (multi-tenant) AWS Outposts racks.

Now, we have finally set the stage to introduce AWS Outposts. Let us begin with the product landing page (https://aws.amazon.com/outposts/). At the time of writing, it is now dubbed Outposts Family, due to the introduction of two new form factors at re:Invent in 2021. The 42U Rack version, the first to be launched, is now called an AWS Outposts rack. The new 1U and 2U versions are called AWS Outposts servers.

Regardless of family type, three outstanding statements that are valid across the family and strongly establish the value proposition of this offering:

  • Fully managed infrastructure: Operated, monitored, patched, and serviced by AWS
  • Run AWS Services on-premises: The same infrastructure as used in AWS data centers, built on top of the AWS Nitro System
  • Truly consistent hybrid experience: The same APIs and tools used in the region, a single pane of management for a seamless experience

Let us cover each in detail.

One of the key aspects of positioning AWS Outposts in customer conversations revolves around explaining how AWS Outposts is different from ordering commodity hardware from traditional hardware vendors. That is exactly where these three statements come into play, highlighting differentiators that cannot be matched by competing offerings.

AWS Outposts is fully managed by AWS. While others may claim their products are also fully managed, AWS takes it to the ultimate level: it is an AWS product end to end. The hardware is AWS, purchase and delivery are managed and conducted by AWS, product requirements are strongly enforced by AWS, and site survey, installation, and servicing are conducted by AWS. No third parties are involved – the customer’s point of contact is AWS.

AWS Outposts enables customers to run a subset of AWS services on-premises and allows applications running on Outposts to seamlessly integrate with AWS products in the region. Single-handedly, the first line itself knocks out traditional hardware. For example, you can’t run EC2 on it. To amend the case, while applications running on traditional hardware can interact with AWS via API calls, AWS Outposts once again takes it to a whole new level, stretching an AWS Availability Zone in a given Region to the confines of an Outposts rack, allowing workloads to operate as if they lived in the same Region.

Customers are extremely sensitive to consistent processes. The use of multiple tools, multiple management consoles, and various scripting languages is cumbersome and error-prone. When you craft a solution where multiple parts come from multiple vendors and are all assembled, that is what ends up happening.

You will need to use a myriad of tools, interfaces, and scripts to configure and make it work. Long and complex setup processes, multiple vendors involved in troubleshooting errors, and multiple teams conducting various stages of the process lead to inefficiency, inconsistency, security problems, and significant delays in being ready for production.

IT professionals normally try to avoid this pitfall by pursuing a solution provided by a single vendor, even with the risk of the infamous single vendor lock-in. However, one hardware provider hardly ever designs and manufactures all the constituent technologies involved, such as the compute, storage, networking, power, cooling, and rack structures. More often than not, the OEM of some of the components is a third-party vendor, if not a third-party brand itself. In the end, these solutions are a collection of individual parts with some degree of consistency.

Here is another significant differentiator of AWS Outposts, which is a thoroughbred AWS solution. AWS Outposts employs the same technology used in AWS data centers whose hardware designs and solutions have undergone significant advancements over time and have been battle-tested in production for several years. With this level of integration and control, AWS can explore and tweak the components for highly specialized tasks, as opposed to the more general-purpose approach of commodity hardware.

AWS developed a technology called the AWS Nitro System (https://aws.amazon.com/ec2/nitro/), which is a set of custom application-specific integrated circuits (ASICs) dedicated to handling very specialized functions. AWS Outposts uses the same technology, standing in line to receive any of the latest and greatest advancements AWS can bring into the hardware technology space. Being such a uniform and purpose-built solution, it benefits from a fully automated, zero-touch deployment for maximum frictionless operations.

Now, we are equipped to widely understand the AWS Outposts offering as a stepping stone deployed outside the AWS cloud, with strong network connection requirements to an AWS Region, capable of running a subset of AWS services and capabilities, and conceived and designed by AWS with its own DNA.

AWS Outposts is not a hardware sell, it is not a general-purpose infrastructure to deploy traditional software solutions, and it is not meant to run disconnected from an AWS Region. AWS Outposts is a cloud adoption decision because you are running your workloads not in a cloud-like infrastructure but rather, in a downscaled cloud infrastructure. This is evident because, during the due-diligence phase, an AWS Outposts opportunity can be disqualified by the field teams if the customer workloads are capable of running in an AWS Region. AWS believes in the philosophy that if workloads are capable of running in AWS Region, they should run in an AWS Region.

Basically, AWS is asking what the use cases and business requirements are that prevent certain workloads from operating in the cloud, something that could defy common sense. Does that mean AWS is trying to discourage the customers from taking the Outposts route in favor of bringing them from the edge to the core Region?

Very much the reverse – AWS wants to make sure customers are making informed decisions. It wants them to understand the use cases for Outposts. Fundamentally, they understand they are effectively setting foot in the cloud with Outposts being the enabler to galvanize cloud adoption and the catalyst for companies to upskill their teams to build a cloud operations model and become trained in AWS technologies and services.

At this point, you should be able to identify the edge IT space, the gap between the cloud and the on-premises data center, and also understand the historical challenges associated with operating infrastructure spanning these significantly different domains.

As the initial solutions to address this problem were not good enough, AWS developed Outposts to be the answer to seamlessly bridging these two worlds. Now, it is time to frame AWS Outposts in this edge space to see how it handles the assignment.

Left arrow icon Right arrow icon
Download code icon Download Code

Key benefits

  • Learn AWS Outposts from the ground up guided by an AWS hybrid edge solutions architect
  • Master hybrid edge concepts, use cases, and architectures and discover how AWS Outposts fits into this space
  • Become the go-to professional for designing, deploying, operating, and maintaining AWS Outposts

Description

The hybrid edge specialty is often misunderstood because it began with an on-premises-focused view encompassing everything not running inside the traditional data center. If you too have workloads that need to live on premises and need a solution to bridge the gap between both worlds, this book will show you how AWS Outposts allows workloads to leverage the benefits of the cloud running on top of AWS technology. In this book, you’ll learn what the Edge space is, the capabilities to look for when selecting a solution to operate in this realm, and how AWS Outposts delivers. The use cases for Outposts are thoroughly explained and the physical characteristics are detailed alongside the service logical constructs and facility requirements. You’ll gain a comprehensive understanding of the sales process—from order placement to rack delivery to your location. As you advance, you’ll explore how AWS Outposts works in real life with step-by-step examples using AWS CLI and AWS Console before concluding your journey with an extensive overview of security and business continuity for maximizing the value delivered by the product. By the end of this book, you’ll be able to create compelling hybrid architectures, solve complex use cases for hybrid scenarios, and get ready for your way forward with the help of expert guidance.

Who is this book for?

If you are a seasoned data center professional, this book will empower you to support businesses to build hybrid edge solutions with AWS technology. It will also help AWS Cloud professionals to master a unique offering in the AWS portfolio that takes Amazon web services beyond the regions. Familiarity with AWS services and traditional data center concepts is assumed.

What you will learn

  • Discover the role of AWS Outposts in the hybrid edge space
  • Understand rack components with typical use cases for AWS Outposts
  • Explore AWS services running on Outposts and its capabilities
  • Select, order, and successfully deploy your Outposts
  • Work with Outposts resources for hands-on operations
  • Assess logical and physical security aspects and considerations
  • Monitor and log configuration and usage to improve your architecture
  • Maintain and troubleshoot hardware and software that run AWS services
Estimated delivery fee Deliver to Slovenia

Premium delivery 7 - 10 business days

€25.95
(Includes tracking information)

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : Nov 28, 2022
Length: 252 pages
Edition : 1st
Language : English
ISBN-13 : 9781803231754
Tools :

What do you get with Print?

Product feature icon Instant access to your digital copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Redeem a companion digital copy on all Print orders
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
OR
Modal Close icon
Payment Processing...
tick Completed

Shipping Address

Billing Address

Shipping Methods
Estimated delivery fee Deliver to Slovenia

Premium delivery 7 - 10 business days

€25.95
(Includes tracking information)

Product Details

Publication date : Nov 28, 2022
Length: 252 pages
Edition : 1st
Language : English
ISBN-13 : 9781803231754
Tools :

Packt Subscriptions

See our plans and pricing
Modal Close icon
€18.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
€189.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts
€264.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total 103.97
Ansible for Real-Life Automation
€31.99
Hybrid Cloud Security Patterns
€35.99
Simplifying Hybrid Cloud Adoption with AWS
€35.99
Total 103.97 Stars icon

Table of Contents

13 Chapters
Part 1: Understanding AWS Outposts – What It Is, Its Components, and How It Works Chevron down icon Chevron up icon
Chapter 1: An Introduction to AWS Outposts Chevron down icon Chevron up icon
Chapter 2: AWS Outposts Anatomy Chevron down icon Chevron up icon
Chapter 3: Pricing, Ordering, and Installation Chevron down icon Chevron up icon
Part 2: Security, Monitoring, and Maintenance Chevron down icon Chevron up icon
Chapter 4: Operations and Working with Outposts Resources Chevron down icon Chevron up icon
Chapter 5: Security Aspects in Outposts Chevron down icon Chevron up icon
Chapter 6: Monitoring Outposts Chevron down icon Chevron up icon
Part 3: Maintenance, Architecture References, and Additional Information Chevron down icon Chevron up icon
Chapter 7: Outposts Maintenance Chevron down icon Chevron up icon
Chapter 8: Architecture References Chevron down icon Chevron up icon
Index Chevron down icon Chevron up icon
Other Books You May Enjoy Chevron down icon Chevron up icon

Customer reviews

Rating distribution
Full star icon Full star icon Full star icon Full star icon Full star icon 5
(2 Ratings)
5 star 100%
4 star 0%
3 star 0%
2 star 0%
1 star 0%
Dwayne Natwick Dec 13, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This book is amazing and learned so much about utilizing AWS Outpost to accelerate the use of AWS services on-premises. Highly recommended if you are planning to move to the cloud or updating your datacenter technology. The diagrams and added shared responsibility understanding for AWS Outpost are extremely helpful.
Amazon Verified review Amazon
Karen Tovmasyan Apr 06, 2023
Full star icon Full star icon Full star icon Full star icon Full star icon 5
Packt is famous for publishing applicable books that you read to know the theory and get your hands dirty.When I was introduced to this Outposts book, I was surprised about the topic and Packt's approach to content - how can I get my hands dirty with Outposts? I can't just run it on my laptop; I need to order a rack.Of course, the Outpost rack does not arrive with a book, and the reader is expected to know their DC content. But what is essential is that you get a noticeable and precise answer on how and WHY you want to use Outposts. For example, what kind of workloads does it serve, what limits does it have, how does it interact with the AWS region, and so on? How does an IAM session to an Outpost handle the global IAM or a service link outage?I managed to get all the answers from this book. Highly recommend it to infrastructure architects evaluating hybrid and edge computing for their businesses.
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

What is the digital copy I get with my Print order? Chevron down icon Chevron up icon

When you buy any Print edition of our Books, you can redeem (for free) the eBook edition of the Print Book you’ve purchased. This gives you instant access to your book when you make an order via PDF, EPUB or our online Reader experience.

What is the delivery time and cost of print book? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela
What is custom duty/charge? Chevron down icon Chevron up icon

Customs duty are charges levied on goods when they cross international borders. It is a tax that is imposed on imported goods. These duties are charged by special authorities and bodies created by local governments and are meant to protect local industries, economies, and businesses.

Do I have to pay customs charges for the print book order? Chevron down icon Chevron up icon

The orders shipped to the countries that are listed under EU27 will not bear custom charges. They are paid by Packt as part of the order.

List of EU27 countries: www.gov.uk/eu-eea:

A custom duty or localized taxes may be applicable on the shipment and would be charged by the recipient country outside of the EU27 which should be paid by the customer and these duties are not included in the shipping charges been charged on the order.

How do I know my custom duty charges? Chevron down icon Chevron up icon

The amount of duty payable varies greatly depending on the imported goods, the country of origin and several other factors like the total invoice amount or dimensions like weight, and other such criteria applicable in your country.

For example:

  • If you live in Mexico, and the declared value of your ordered items is over $ 50, for you to receive a package, you will have to pay additional import tax of 19% which will be $ 9.50 to the courier service.
  • Whereas if you live in Turkey, and the declared value of your ordered items is over € 22, for you to receive a package, you will have to pay additional import tax of 18% which will be € 3.96 to the courier service.
How can I cancel my order? Chevron down icon Chevron up icon

Cancellation Policy for Published Printed Books:

You can cancel any order within 1 hour of placing the order. Simply contact customercare@packt.com with your order details or payment transaction id. If your order has already started the shipment process, we will do our best to stop it. However, if it is already on the way to you then when you receive it, you can contact us at customercare@packt.com using the returns and refund process.

Please understand that Packt Publishing cannot provide refunds or cancel any order except for the cases described in our Return Policy (i.e. Packt Publishing agrees to replace your printed book because it arrives damaged or material defect in book), Packt Publishing will not accept returns.

What is your returns and refunds policy? Chevron down icon Chevron up icon

Return Policy:

We want you to be happy with your purchase from Packtpub.com. We will not hassle you with returning print books to us. If the print book you receive from us is incorrect, damaged, doesn't work or is unacceptably late, please contact Customer Relations Team on customercare@packt.com with the order number and issue details as explained below:

  1. If you ordered (eBook, Video or Print Book) incorrectly or accidentally, please contact Customer Relations Team on customercare@packt.com within one hour of placing the order and we will replace/refund you the item cost.
  2. Sadly, if your eBook or Video file is faulty or a fault occurs during the eBook or Video being made available to you, i.e. during download then you should contact Customer Relations Team within 14 days of purchase on customercare@packt.com who will be able to resolve this issue for you.
  3. You will have a choice of replacement or refund of the problem items.(damaged, defective or incorrect)
  4. Once Customer Care Team confirms that you will be refunded, you should receive the refund within 10 to 12 working days.
  5. If you are only requesting a refund of one book from a multiple order, then we will refund you the appropriate single item.
  6. Where the items were shipped under a free shipping offer, there will be no shipping costs to refund.

On the off chance your printed book arrives damaged, with book material defect, contact our Customer Relation Team on customercare@packt.com within 14 days of receipt of the book with appropriate evidence of damage and we will work with you to secure a replacement copy, if necessary. Please note that each printed book you order from us is individually made by Packt's professional book-printing partner which is on a print-on-demand basis.

What tax is charged? Chevron down icon Chevron up icon

Currently, no tax is charged on the purchase of any print book (subject to change based on the laws and regulations). A localized VAT fee is charged only to our European and UK customers on eBooks, Video and subscriptions that they buy. GST is charged to Indian customers for eBooks and video purchases.

What payment methods can I use? Chevron down icon Chevron up icon

You can pay with the following card types:

  1. Visa Debit
  2. Visa Credit
  3. MasterCard
  4. PayPal
What is the delivery time and cost of print books? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela