Menu
AWS Schema Conversion Tool
User Guide (Version 1.0)

The AWS Schema Conversion Tool Extension Pack and AWS Services for Databases

When you convert your database schema, the AWS Schema Conversion Tool (AWS SCT) adds an additional schema to your target DB instance. This schema implements system functions of the source database that are required when writing your converted schema to your target DB instance. The schema is called the extension pack schema.

If you are converting a data warehouse to Amazon Redshift, instead see The AWS Schema Conversion Tool Extension Pack and Python Libraries for Data Warehouses.

The extension pack schema is named according to your source database as follows:

  • Microsoft SQL Server: AWS_SQLSERVER_EXT

  • MySQL: AWS_MYSQL_EXT

  • Oracle: AWS_ORACLE_EXT

  • PostgreSQL: AWS_POSTGRESQL_EXT

In two cases, you might want to install the extension pack manually:

  • You accidentally delete the extension pack database schema from your target database.

  • You want to use AWS services to emulate database functionality.

Using AWS Services to Emulate Database Functionality

In some cases, database features can't be converted to equivalent Amazon Relational Database Service (Amazon RDS) features. Some examples are Oracle send email calls that use UTL_SMTP, and Microsoft SQL Server jobs that use a job scheduler. If you host and self-manage a database on the Amazon Elastic Compute Cloud (Amazon EC2) platform, you can emulate these features by substituting AWS services for them.

The AWS SCT extension pack wizard helps you install, create, and configure AWS Lambda functions to emulate email, job scheduling, and other features.

Before You Begin

Almost all work you do with the AWS SCT starts with the following three steps:

  1. Create an AWS SCT project.

  2. Connect to your source database.

  3. Connect to your target database.

If you have not created an AWS SCT project yet, see Getting Started with the AWS Schema Conversion Tool.

Before you install the extension pack, you need to convert your database schema. For more information, see Converting Database Schema to Amazon RDS by Using the AWS Schema Conversion Tool.

Applying the Extension Pack

Use the following procedure to apply the extension pack.

Important

The AWS service emulation features are supported only for databases installed and self-managed on the Amazon EC2 platform. Don't install the service emulation features if your target database is on an Amazon RDS DB instance.

To apply the extension pack

  1. In the AWS Schema Conversion Tool, in the target database tree, open the context (right-click) menu, and choose Apply Extension Pack.

    
                        Apply Extension Pack context menu

    The extension pack wizard appears.

  2. Read the Welcome page, and then choose Next.

  3. On the AWS Services Settings page, do the following:

    • If you are reinstalling the extension pack database schema only, choose Skip this step for now, and then choose Next.

    • If you are installing AWS services, provide the credentials to connect to your AWS account. You can use your AWS Command Line Interface (AWS CLI) credentials if you have the AWS CLI installed. You can also use credentials that you previously stored in a profile in the global application settings and associated with the project. If necessary, choose Navigate to Project Settings to associate a different profile with the project. If necessary, choose Global Settings to create a new profile. For more information, see Storing AWS Profiles in the AWS Schema Conversion Tool.

  4. On the Email Sending Service page, do the following:

    • If you are reinstalling the extension pack database schema only, choose Skip this step for now, and then choose Next.

    • If you are installing AWS services and you have an existing AWS Lambda function, you can provide it. Otherwise the wizard creates it for you. When you are done, choose Next.

  5. On the Job Emulation Service page, do the following:

    • If you are reinstalling the extension pack database schema only, choose Skip this step for now, and then choose Next.

    • If you are installing AWS services and you have an existing AWS Lambda function, you can provide it. Otherwise the wizard creates it for you. When you are done, choose Next.

  6. On the Functions Emulation page, choose Create Extension Pack. Messages appear with the status of the extension pack operations. When you are done, choose Finish.