Solution overviewįor our use case, we take a scenario in which our company mandates the following: You then save the AMI as a golden image to create a CEV and create Amazon RDS Custom for SQL Server instances by choosing the CEV. You can then install other third-party applications on the OS or customize the configuration of the OS and SQL Server to meet your enterprise needs. You choose an AMI from the Amazon EC2 Windows AMI list to use as a base image. Overview of CEVĪ custom engine version (CEV) for Amazon RDS Custom for SQL Server is, essentially, an Amazon Machine Image (AMI) with Microsoft SQL Server pre-installed. We also demonstrate how you can persist the changes even when Amazon RDS chooses to do a host replacement using a custom engine version (CEV). In this post, we examine a use case in which you make changes at the OS level of the RDS Custom for SQL Server instance by installing software. With Amazon RDS Custom, you get the automation of Amazon RDS with flexibility similar to Amazon Elastic Compute Cloud (Amazon EC2). Amazon RDS Custom for SQL Server automates the setup, operation, and backup of databases in the AWS cloud while granting you access to the database and underlying OS. Amazon RDS Custom is a managed database service for legacy, custom, and packaged applications that require access to the underlying OS and database environment. In the context of RDS Custom for SQL Server, a host replacement is when the OS disk (C:\ drive) is replaced with a new OS image.Ĭustomers with commercial-of-the-shelf (COTS) applications often require administrative access to the SQL Server instance and its underlying OS. Customers running their Microsoft SQL Server workloads on Amazon Relational Database Service (Amazon RDS) Custom for SQL Server ask us how they can persist changes at the operating system (OS) level even if Amazon RDS chooses to perform a host replacement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |