Menu
Amazon Relational Database Service
User Guide (API Version 2014-10-31)

Setting Up Amazon RDS to Host Tools and Third-Party Software for Oracle

You can use Amazon RDS to host an Oracle DB instance that supports software and components such as the following:

  • Siebel Customer Relationship Management (CRM)

  • Oracle Fusion Middleware Metadata — installed by the Repository Creation Utility (RCU)

The following procedures help you create an Oracle DB instance on Amazon RDS that you can use to host additional software and components for Oracle.

Creating an Amazon VPC for Use with an Oracle Database

In the following procedure, you create an Amazon VPC, a private subnet, and a security group. Because your Amazon RDS DB instance needs to be available only to your middle-tier components, and not to the public Internet, your Amazon RDS DB instance is hosted in a private subnet, providing greater security.

To create an Amazon VPC

  1. Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the top-right corner of the AWS Management Console, choose the AWS Region for your VPC. This example uses the US West (Oregon) region.

  3. In the upper-left corner, choose VPC Dashboard and then choose Start VPC Wizard.

  4. On the page Step 1: Select a VPC Configuration, choose VPC with Public and Private Subnets, and then choose Select.

  5. On the page Step 2: VPC with Public and Private Subnets, shown following, set these values:

    Option Value
    IP CIDR block

    10.0.0.0/16

    For more information about selecting CIDR blocks for your VPC, see VPC Sizing.

    VPC name

    The name for your VPC, for example vpc-1.

    Public subnet

    10.0.0.0/24

    For more information about subnet sizing, see Subnet Sizing.

    Availability Zone An Availability Zone for your AWS Region.
    Public subnet name

    The name for your public subnet, for example subnet-public-1.

    Private subnet

    10.0.1.0/24

    For more information about subnet sizing, see Subnet Sizing.

    Availability Zone

    An Availability Zone for your AWS Region.

    Private subnet name

    The name for your private subnet, for example subnet-private-1.

    Instance type

    An instance type for your NAT instance, for example t2.micro.

    Note

    If you don't see Instance type in the console, choose Use a NAT instance instead.

    Key pair name

    No key pair

    Subnet

    None

    Enable DNS hostnames

    Yes

    Hardware tenancy

    Default

    
                            VPC with Public and Private Subnets Wizard
  6. Choose Create VPC.

An Amazon RDS DB instance in a VPC requires at least two private subnets or at least two public subnets, to support Multi-AZ deployment. For more information about working with multiple Availability Zones, see Regions and Availability Zones. Because your database is private, add a second private subnet to your VPC.

To create an additional subnet

  1. Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the top-right corner of the AWS Management Console, confirm that you are in the correct AWS Region for your VPC.

  3. In the upper-left corner, choose VPC Dashboard, choose Subnets, and then choose Create Subnet.

  4. On the Create Subnet page, set these values:

    Option Value
    Name tag

    The name for your second private subnet, for example subnet-private-2.

    VPC

    Your VPC, for example vpc.

    Availability Zone

    An Availability Zone for your AWS Region.

    Note

    Choose an Availability Zone different from the one that you chose for the first private subnet.

    CIDR block

    10.0.2.0/24

  5. Choose Yes, Create.

Both private subnets must use the same route table. In the following procedure, you check to make sure the route tables match, and if not you edit one of them.

To ensure the subnets use the same route table.

  1. Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the top-right corner of the AWS Management Console, confirm that you are in the correct AWS Region for your VPC.

  3. In the upper-left corner, choose VPC Dashboard, choose Subnets, and then choose your first private subnet, for example subnet-private-1.

  4. At the bottom of the console, choose the Route Table tab, shown following.

    
                            Route Table information
  5. Make a note of the route table, for example rtb-0d9fc668.

  6. In the list of subnets, choose the second private subnet, for example subnet-private-2.

  7. At the bottom of the console, choose the Route Table tab.

  8. If the route table for the second subnet is not the same as the route table for the first subnet, edit it to match:

    1. Choose Edit.

    2. For Change to, select the route table that matches your first subnet.

    3. Choose Save.

A security group acts as a virtual firewall for your DB instance to control inbound and outbound traffic. In the following procedure, you create a security group for your DB instance. For more information about security groups, see Security Groups for Your VPC.

To create a VPC security group for a Private Amazon RDS DB Instance

  1. Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the top-right corner of the AWS Management Console, confirm that you are in the correct AWS Region for your VPC.

  3. In the upper-left corner, choose VPC Dashboard, choose Security Groups, and then choose Create Security Group.

  4. On the page Create Security Group, set these values:

    Option Value
    Name tag

    The name for your security group, for example sg-db-1.

    Group name

    The name for your security group, for example sg-db-1.

    Description

    A description for your security group.

    VPC

    Your VPC, for example vpc-1.

  5. Choose Yes, Create.

In the following procedure, you add rules to your security group to control inbound traffic to your DB instance. For more information about inbound rules, see Security Group Rules.

To add inbound rules to the security group

  1. Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the top-right corner of the AWS Management Console, confirm that you are in the correct AWS Region for your VPC.

  3. In the upper-left corner, choose VPC Dashboard, choose Security Groups, and then choose your security group, for example sg-db-1.

  4. At the bottom of the console, choose the Inbound Rules tab, and then choose Edit.

  5. Set these values, as shown following:

    Option Value
    Type

    Oracle (1521)

    Protocol

    TCP (6)

    Port Range

    1521

    Source

    The identifier of your security group. When you choose the box, you see the name of your vpc, for example vpc-1.

    
                            Inbound Rules information
  6. Choose Save.

Creating an Oracle DB Instance

You can use Amazon RDS to host an Oracle DB instance. In the following procedure, you create the Oracle DB instance.

To launch an Oracle DB instance

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.

  2. In the top-right corner of the AWS Management Console, choose the AWS Region for your DB instance. Choose the same AWS Region as your VPC.

  3. In the upper-left corner, choose RDS Dashboard and then choose Launch a DB Instance.

  4. On the page Step 1: Select Engine, choose Oracle, and then choose the Select button for the Oracle Database Enterprise Edition.

    
                            Engine selection
  5. On the page Step 2: Production?, choose Production, and then choose Next Step.

    Note

    For a DB instance for development and testing you can choose Dev/Test.

  6. On the page Step 3: Specify DB Details, shown following, set these values:

    Option Value
    DB Engine

    oracle-ee

    License Model

    bring-your-own-license

    DB Engine Version

    The Oracle version you want to use. You can use Oracle 12c, version 12.1.0.1.0 or 12.1.0.2.0.

    DB Instance Class

    The DB instance class you want to use. For more information, see DB Instance Class.

    Multi-AZ Deployment

    Yes. Multi-AZ deployment creates a standby replica of your DB instance in another Availability Zone for failover support. Multi-AZ is recommended for production workloads. For more information about multiple Availability Zones, see Regions and Availability Zones.

    Note

    For development and testing, you can choose No.

    Storage Type

    Provisioned IOPS (SSD). Provisioned IOPS (input/output operations per second) is recommended for production workloads. For more information about storage, see Storage for Amazon RDS.

    Note

    For development and testing, you can choose General Purpose (SSD).

    Allocated Storage

    The storage to allocate for your database. Allocate at least 20 GB of storage for your database. In some cases, allocating a higher amount of storage for your DB instance than the size of your database can improve I/O performance. For more information about storage allocation, see Amazon RDS Storage Types and Guidelines for Creating Oracle Database Tablespaces.

    Provisioned IOPS

    The amount of Provisioned IOPS to be initially allocated for the DB instance. This value must be a multiple between 3 and 10 of the storage amount for the DB instance. This value must also be an integer multiple of 1,000.

    Note

    For development and testing, you do not need Provisioned IOPS.

    DB Instance Identifier

    The name for DB instance, for example oracle-instance.

    Master User Name

    The master user name for the DB instance, for example oracle_mu.

    Master User Password and Confirm Password

    A password that contains from 8 to 30 printable ASCII characters (excluding /,", and @) for your master user password. Retype the password in the Confirm Password box.

    
                            Specify DB Details form
  7. Choose Next Step.

  8. On the page Step 4: Configure Advanced Settings, shown following, set these values:

    Option Value
    VPC

    Your VPC, for example vpc-1.

    Subnet Group

    Create new DB Subnet Group

    Publicly Accessible

    No

    Availability Zone

    No Preference

    VPC Security Group

    Your VPC security group, for example sg-db-1.

    Database Name

    The name for your database, for example db1.

    Database Port

    1521

    Parameter Group

    The default parameter group.

    Option Group

    The default option group.

    Copy Tags To Snapshots

    This option, when chosen, specifies to have any DB instance tags copied to a DB snapshot when you create a snapshot. For more information, see Tagging Amazon RDS Resources.

    Character Set Name

    A character set for your DB instance. The default value of AL32UTF8 is for the Unicode 5.0 UTF-8 Universal character set. You can't change the character set after the DB instance is created.

    Enable Encryption

    Yes or No. A value of Yes enables encryption at rest for this DB instance. For more information, see Encrypting Amazon RDS Resources.

    Backup Retention Period

    The number of days you want to retain automatic backups of your database. For most DB instances, you should set this value to 1 or greater.

    Backup Window

    Unless you have a specific time that you want to have your database backup, use the default of No Preference.

    Auto Minor Version Upgrade

    Select Yes to enable your DB instance to receive minor DB engine version upgrades automatically when they become available.

    Maintenance Window

    Select the 30 minute window in which pending modifications to your DB instance are applied. If you the time period doesn't matter, select No Preference.

    
                            Specify DB Details form
  9. Choose Launch DB Instance.

    On the RDS console, the new DB instance appears in the list of DB instances. The DB instance has a status of creating until it's ready to use. When the status of the DB instance changes to available, you can connect to it. Depending on the DB instance configuration, it can take several minutes for the new DB instance to become available.

Additional Amazon RDS Interfaces

In the preceding procedures, we use the AWS Management Console to perform tasks. Amazon Web Services also provides the AWS Command Line Interface (AWS CLI), and an application programming interface (API). You can use the AWS CLI or the API to automate many of the tasks for managing Amazon RDS, including tasks to manage an Oracle DB instance with Amazon RDS.

For more information, see AWS Command Line Interface Reference for Amazon RDS and Amazon Relational Database Service API Reference.

Related Topics