Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Bücher
Zeitschriften
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
ATZ-Fachkongress

Chassis.tech plus 2024


4 Kongresse in einer Veranstaltung

Treffen Sie in München die Fachleute von Chassis, Lenkung, Bremsen sowie Reifen/Räder.
Erweiterte Suche
Anmelden
nach oben

2021 | Buch

Wait, I Can Run Windows on AWS? Kapitel lesen Erstes Kapitel lesen

Running Microsoft Workloads on AWS

Active Directory, Databases, Development, and More

verfasst von: Ryan Pothecary

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten
insite
SUCHEN

Über dieses Buch

Did you know that Amazon Web Services runs nearly double the amount of Microsoft Workloads in the cloud than any other provider?

Running Microsoft Workloads in AWS is your single-source solution for learning the best practice skills and guidance that AWS consultants offer their customers in the field. Over 70% of enterprise workloads are based on Microsoft technologies and AWS has been running these technologies in the AWS Cloud for more than 12 years—far longer than Microsoft’s own Azure cloud platform.

This book introduces AWS foundations and compares them to traditional Microsoft architectures, showing you how to design your AWS Cloud platform to run your current Microsoft solutions. It covers the crucial area of identity and access control, showing how to implement Active Directory inside the AWS platform and the most secure ways of enabling Single Sign On from your own data centers and from Microsoft AzureAD.

The book goes in-depth and shows how developers across the globe are using their existing .NET skills to develop directly on top of AWS, using current AWS development services such as AWS Code Pipeline, AWS Code Build, and AWS Code Deploy to create the next generation of cloud-native applications using the most popular cloud serverless service—AWS Lambda.

What You Will Learn

Be familiar with the basic building blocks of AWS and how the terminology differs from your own data center and Microsoft AzureUnderstand Amazon Machine Images (AMI) strategies and solutions to best manage the trade-off between speed and manageabilityRun one of the most popular Microsoft products: SQL Server on AWSBe aware of the different database architecture designs for using Amazon RDS and Amazon EC2Read an overview of Serverless Development in the AWS cloud from a Microsoft .NET perspectiveKnow migration strategies for moving your Microsoft Workloads to the AWS Cloud

Who This Book Is For

Covers high-level concepts and solutions for CTOs and CCTOs; provides a solution for architects; and dives deep into the topic for administrators and DevOps engineers

Inhaltsverzeichnis

Frontmatter
Chapter 1. Wait, I Can Run Windows on AWS?
Abstract
I was speaking to a customer. We were talking about a plan to migrate thousands of Microsoft servers currently running in the company’s data centers to AWS. At one point, the customer said, “I’ve been working on AWS projects for the last 18 months and only found out last week that you can run Microsoft servers on AWS.”
Ryan Pothecary
Chapter 2. AWS 101
Abstract
If you’ve been using AWS for a while, then please feel free to skip or skim this chapter. Still here? Great! Welcome to the Amazon Web Services Cloud Platform.
Ryan Pothecary
Chapter 3. Server
Abstract
If you are considering Amazon Web Services as the cloud provider for your Microsoft workloads, then this chapter on all things Windows Server is going to be an important one for you. In later chapters of this book, we discuss containers and serverless, and we also cover AWS services such as Amazon RDS or AWS Directory Services which can replace the need to run and maintain servers. However, especially at the start of your cloud journey, you’ll predominantly be using Amazon Elastic Compute Cloud (EC2) virtual machines to act as the servers for your Microsoft workloads.
Ryan Pothecary
Chapter 4. Databases
Abstract
In a book focused on Microsoft Workloads, you’d be excused for thinking that a chapter dedicated to databases would focus on Microsoft SQL Server. You’d be right of course. I’ve certainly used MySQL and Oracle in a Windows Server environment without issue, but we need to keep in mind that there are certainly options of other database engines for your Microsoft Workloads inside AWS, because the area of databases has evolved over the last 5 years to embrace nonrelational databases as well as database engines created for specific use cases.
Ryan Pothecary
Chapter 5. Developing on AWS
Abstract
AWS has always been a welcoming home for developers. AWS’s first prelaunch services were aimed solely at the development community. Who else has a use for a scalable queuing service if not developers? And have you wondered why Amazon S3 is an object storage service rather than block based like traditional storage solutions?
Ryan Pothecary
Chapter 6. Serverless
Abstract
In retrospect, it was an obvious thing to do; AWS had for a long time developed services that abstracted the user or application away from the underlying infrastructure, such as the database service Amazon RDS.
Ryan Pothecary
Chapter 7. Containers
Abstract
Docker emerged in 2013 with their Container technology, although the term Containers can be traced back as far as 2006 with Google’s Process Containers or 2008 with LXC (Linux Containers). In reality, the idea of abstracting and isolating processes and user environments from each other can go back to the mainframe days of yore.
Ryan Pothecary
Chapter 8. Operational Integration
Abstract
“Cloud is Different” is a mantra I repeat on a daily basis. I’ve seriously thought about getting t-shirts made. The reason for banging on about this for such a long time is simple. Businesses have been doing IT in the same way for the last 40 years, and a lot of companies think that they can continue to use the same processes, tooling, and methodologies after they’ve moved to the cloud.
Ryan Pothecary
Chapter 9. Migration
Abstract
This chapter covers the business and technical aspects of migration to the AWS Cloud. From a business perspective, we’ll cover the business case, costs, and resources. From a technical perspective, we’ll cover the tools and services you’ll need to move your Microsoft workloads to AWS.
Ryan Pothecary
Chapter 10. Identity
Abstract
I remember having to create a “network user” for myself on every individual server in the office. This was back in the days of using Novell NetWare 3.11 in the early 1990s. Every morning, I’d have to connect and authenticate to several different servers because each one had something different that I needed. One was for printer access, another for my “Home Drive,” and the third for office files. In 1993, I asked my boss to allow me a day off to attend a Novell seminar at their UK offices. It was there that I saw NetWare 4.0 for the first time and heard of something called NetWare Directory Services (NDS).
Ryan Pothecary
Backmatter
Metadaten
Titel
Running Microsoft Workloads on AWS
verfasst von
Ryan Pothecary
Copyright-Jahr
2021
Verlag
Apress
Electronic ISBN
978-1-4842-6628-1
Print ISBN
978-1-4842-6627-4
DOI
https://doi.org/10.1007/978-1-4842-6628-1

Premium Partner

    Bildnachweise