Provision Oracle Database@AWS stack utilizing AWS CloudFormation

Oracle Database@AWS (ODB@AWS) delivers Oracle Exadata infrastructure, managed by Oracle Cloud Infrastructure (OCI), from inside AWS information facilities. It allows you to migrate Oracle databases to AWS whereas benefiting from the excessive efficiency, scalability, and superior capabilities of Exadata. Oracle Database@AWS affords deep integration with native AWS providers, together with Amazon Easy Storage Service (Amazon S3), zero-ETL pipelines, and AWS Key Administration Service (AWS KMS). Oracle databases run alongside functions deployed on Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), and extra. This tight integration simplifies information flows, enhances safety, and accelerates software growth throughout various compute environments.

At present Oracle Database@AWS affords the next Oracle Database providers

Infrastructure as code (IaC) is the method of provisioning and managing an software’s infrastructure by way of a set of configuration recordsdata. IaC is designed that will help you centralize infrastructure administration, standardize assets, and scale rapidly in order that new environments are repeatable, dependable, and constant. You possibly can deploy the assets in Oracle Database@aws utilizing IAC instruments like Terraform or AWS CloudFormation.

AWS CloudFormation is an infrastructure as code (IaC) service that permits you to simply mannequin, provision, and handle AWS and third-party assets. AWS CloudFormation helps you mannequin and arrange your AWS assets in an effort to spend much less time managing these assets and extra time focusing in your functions that run in AWS.

On this submit, we clarify find out how to arrange key parts of Oracle Database@AWS providing together with ODB community, Oracle Exadata infrastructure, Exadata VM clusters and Autonomous VM clusters utilizing AWS CloudFormation template.

Resolution overview

To get began with Oracle Database@AWS, you may view the itemizing in AWS Market. To make use of the service, you configure it inside your AWS account by way of a course of known as onboarding. To start onboarding, contact your Oracle consultant and request a Non-public Provide. After you agree on pricing, phrases and circumstances, you full the acquisition by way of AWS Market. After the acquisition is full, you hyperlink your AWS account with an OCI tenancy. That is known as multicloud linking. Primarily based in your necessities, you should use the entitlement sharing functionality to share the AWS Market entitlements for ODB@AWS throughout AWS accounts in the identical AWS group. After you full onboarding, you may start provisioning the Oracle Database@AWS system assets for Exadata Database Service on Devoted Infrastructure and Autonomous AI Database on Devoted Exadata Infrastructure. Provisioning begins with creating an ODB community and Exadata infrastructure. Primarily based in your workloads and necessities, you then create both an Exadata VM cluster for the Oracle Exadata Database Service, or an Autonomous VM Cluster for Autonomous AI Database on Devoted Exadata Infrastructure.

To start utilizing Oracle Database@AWS, you may create the next assets utilizing the Oracle Database@AWS console, AWS CLI, or APIs:

1. ODB community
2. Oracle Exadata infrastructure
3. Exadata VM cluster or Autonomous VM cluster
4. ODB peering connection

The next diagram exhibits the Oracle Database@AWS structure.

Earlier than we dive in, you will need to perceive the structure of Oracle Database@AWS and the important thing parts concerned in it.

• Amazon Digital Non-public Cloud and Subnet: An Amazon digital personal cloud (Amazon VPC) permits you to launch AWS assets right into a digital community you’ve outlined. This digital community resembles a standard community that you just function in your individual information middle, with the advantages of utilizing the scalable infrastructure of AWS. After you create an VPC, you may add subnets.
  
  A subnet is a spread of IP addresses in your Amazon VPC. You possibly can create AWS assets, resembling Amazon EC2 cases, in particular subnets.
• OCI Digital Cloud Community (VCN) and Subnet: A Digital Cloud Community (VCN) is a customizable, personal community that you just arrange in an OCI tenancy inside a specified Oracle Area. It offers a safe and scalable community atmosphere the place you may deploy and handle your OCI assets, resembling compute cases, databases, and storage. A VCN acts as a virtualized model of a standard community, together with key parts like subnets, route tables, and gateways. VCNs allow you to to isolate and section your cloud assets inside logically separated networks, enhancing safety and manageability. VCNs are divided into subnets, that are smaller subdivisions that assist you to section assets and management site visitors at a finer degree. Subnets might be both public (permitting public IP addresses and web entry) or personal (limiting direct web entry). In Oracle multicloud structure, when an ODB community with consumer and backup subnets is created in an AWS Area, a corresponding OCI VCN with subnets is routinely created in your OCI tenancy within the paired OCI area.
• OCI Area (Dad or mum Web site): An OCI Area is a geographic space that has a number of information facilities often known as availability domains. Within the Oracle multicloud mannequin, an OCI area related to a paired AWS Area known as a Dad or mum Web site. ODB@AWS is offered solely within the areas mentioned in Regional Availability.
  
  Every OCI area operates independently of different areas, offering fault tolerance and catastrophe restoration capabilities. Every area consists of a number of availability domains. An OCI availability area (AD) is a number of information facilities inside an OCI area. In areas which have a number of ADs, the ADs are bodily remoted from one another. They don’t share infrastructure, energy, cooling, or inside networking, so a failure in a single AD is unlikely to have an effect on different ADs in the identical area.
• OCI Little one Web site: An OCI youngster web site is a knowledge middle that extends an OCI availability area (AD) to an Availability Zone (AZ) in an AWS area. With the OCI youngster web site mannequin, the Exadata infrastructure used for Oracle Database@AWS bodily resides in an AWS information middle (an AZ inside an AWS area), however is logically mapped to an OCI area and its community parts.
• ODB Community: The ODB community is a non-public and remoted community that hosts Oracle Exadata VM Clusters and Autonomous VM Clusters inside a specified AWS Availability Zone (AZ). The ODB community consists of a CIDR vary of IP addresses. The ODB community maps on to the community that exists inside the OCI youngster web site and permits communication between AWS and OCI. In Oracle’s multicloud structure, the ODB community offers community connectivity for the OCI parts which are a part of the Oracle Database@AWS service.
  
  If you create an ODB community, you specify data resembling the next:
  1. Availability Zone — The ODB community is restricted to an AZ.
     
     On the time of scripting this submit, you should use Oracle Database@AWS within the following AWS Areas:
     
     US East (N. Virginia)
     
     You should use the AZs with the bodily IDs use1-az4 and use1-az6.
     
     US West (Oregon)
     
     You should use the AZs with the bodily IDs usw2-az3 and usw2-az4.
     
     Asia Pacific (Tokyo)
     
     You should use the AZs with the bodily IDs apne1-az1 and apne1-az4.
     
     US East (Ohio)
     
     You should use the AZs with the bodily IDs use2-az1 and use2-az2.
     
     Europe (Frankfurt)
     
     You should use the AZs with the bodily IDs euc1-az1 and euc1-az2.

     Run the next command to seek out the logical AZ names in your account that map to the previous bodily AZ IDs.

     aws ec2 describe-availability-zones 
      --region us-east-1 
     --query "AvailabilityZones[*].{ZoneName:ZoneName, ZoneId:ZoneId}" 
     --output desk

  2. Consumer CIDR addresses — The ODB community requires a consumer subnet CIDR for Exadata VM clusters and Autonomous VM clusters.
  3. Backup CIDR addresses — The ODB community requires a backup subnet CIDR for managed database backups of VM clusters. The backup subnet is non-compulsory for Exadata VM clusters.
  4. AWS service integrations — You possibly can configure a community path for AWS service integrations resembling Amazon S3 and zero-ETL with Amazon Redshift. For extra data, see AWS service integrations.
     
     Seek advice from ODB Community creation for extra data on CIDR necessities.
• Oracle Exadata Infrastructure: Oracle Exadata infrastructure is a high-performance, built-in {hardware} and software program platform designed for working Oracle Databases. Exadata is a pre-configured and pre-tested full-stack platform, that means all the required {hardware} and software program parts are built-in and optimized to work collectively seamlessly. Exadata includes a scale-out structure with database servers and clever storage servers that may be independently scaled to satisfy altering workload calls for. Exadata storage servers transcend conventional storage by having their very own CPUs and specialised software program that allow them to carry out database operations resembling SQL question processing near the info. Exadata makes use of a high-bandwidth, low-latency community material (resembling RDMA over Converged Ethernet or RoCE) to attach database servers and storage servers, making certain fast information entry and switch charges. In Oracle multicloud structure, Exadata infrastructure is the underlying {hardware} for each Oracle Exadata Database Service and Oracle Autonomous AI Database.
  
  If you create Exadata infrastructure in Oracle Database@AWS, you specify data resembling the next:

  Seek advice from Exadata Infrastructure for extra data.

• Exadata VM clusters: An Exadata VM cluster is a set of tightly coupled Exadata VMs. Every VM has an entire Oracle database set up that features all options of Oracle Enterprise Version, together with Oracle Actual Utility Clusters (Oracle RAC) and Oracle Grid Infrastructure. You possibly can create a number of Oracle Exadata databases on a VM cluster.

  For diagrams that present the structure of VMs and VM clusters, see Exadata Database Service on Devoted Infrastructure Technical Structure
  
  If you create a VM cluster, you specify data that features the next:

  • An ODB community
  • An Oracle Exadata infrastructure
  • The database servers on which to put the VMs within the cluster
  • The whole quantity of usable Exadata storage

  For extra data on find out how to create consult with Exadata VM Cluster

• Autonomous VM clusters: Autonomous VM Clusters (AVMCs) enable a bodily Exadata Cluster (Machine) to be partitioned into a number of digital clusters. They can be utilized to isolate environments for various database workloads by way of separate entry guidelines, community configurations, in addition to customizable compute reminiscence, and storage assets. The AVMC is without doubt one of the infrastructure parts of the four-level database structure mannequin on which an Autonomous Container Database is constructed. A number of AVMCs are provisioned inside an Exadata Infrastructure (EI) useful resource, offering the hyperlink between the EI and the Autonomous Container Database assets in your deployment. AVMCs present remoted environments for various database workloads by way of separate entry guidelines, community configurations, in addition to customizable compute reminiscence, and storage assets. You possibly can configure the ECPU core depend per VM, database reminiscence per CPU, database storage, and most variety of autonomous container databases whereas creating Autonomous VM Cluster. For extra data consult with Create Autonomous VM Cluster
• ODB Peering: ODB peering is a user-created community connection that enables site visitors to be routed privately between an Amazon VPC and an ODB community. In Oracle multicloud structure, site visitors between your functions within the VPC and the Oracle Database within the ODB community is routed privately by way of ODB peering with out traversing the general public web. For extra data consult with creating ODB peering connection.
• Oracle Exadata databases: With Oracle Database@AWS, you employ the AWS console to create the Oracle Exadata infrastructure and VM clusters that host the Exadata databases. You then use OCI APIs to create and handle the Oracle databases. For extra data on find out how to create the database consult with Exadata Database and Autonomous Database

For extra particulars on parts of Oracle Database@AWS consult with Structure.

For detailes steps on find out how to create above assets consult with creating assets in your Oracle Database@AWS

Conditions

Earlier than you start, be sure you have the next stipulations:

You should use the next AWS CloudFormation templates to provision varied assets in Oracle Database@AWS. Customise the parameters based on what you are promoting necessities. You will need to perceive the importance of every parameter and their allowed values.

The next are the templates obtainable on the time of scripting this weblog. For the newest data, consult with Provisioning Oracle Database@AWS by way of AWS CloudFormation.

Step 1: Create an ODB community in Oracle Database@AWS

Sort: AWS::ODB::OdbNetwork
Properties:
  AvailabilityZone: String
  AvailabilityZoneId: String
  BackupSubnetCidr: String
  ClientSubnetCidr: String
  CustomDomainName: String
  DefaultDnsPrefix: String
  DeleteAssociatedResources: Boolean
  DisplayName: String
  S3Access: String
  S3PolicyDocument: String
  Tags: 
    - Tag
  ZeroEtlAccess: String

For extra data on IP handle necessities consult with Planning IP handle house in Oracle Database@AWS

Step 2: Create an Oracle Exadata infrastructure in Oracle Database@AWS

Sort: AWS::ODB::CloudExadataInfrastructure
Properties:
  AvailabilityZone: String
  AvailabilityZoneId: String
  ComputeCount: Integer
  CustomerContactsToSendToOCI: 
    - CustomerContact
  DatabaseServerType: String
  DisplayName: String
  MaintenanceWindow: 
    MaintenanceWindow
  Form: String
  StorageCount: Integer
  StorageServerType: String
  Tags: 
    - Tag

Step 3: Create an Exadata VM cluster or Autonomous VM cluster in Oracle Database@AWS

 Sort: AWS::ODB::CloudVmCluster
Properties:
  CloudExadataInfrastructureId: String
  ClusterName: String
  CpuCoreCount: Integer
  DataCollectionOptions: 
    DataCollectionOptions
  DataStorageSizeInTBs: Quantity
  DbNodes: 
    - DbNode
  DbNodeStorageSizeInGBs: Integer
  DbServers: 
    - String
  DisplayName: String
  GiVersion: String
  Hostname: String
  IsLocalBackupEnabled: Boolean
  IsSparseDiskgroupEnabled: Boolean
  LicenseModel: String
  MemorySizeInGBs: Integer
  OdbNetworkId: String
  ScanListenerPortTcp: Integer
  SshPublicKeys: 
    - String
  SystemVersion: String
  Tags: 
    - Tag
  TimeZone: String
        
Sort: AWS::ODB::CloudAutonomousVmCluster
Properties:
  AutonomousDataStorageSizeInTBs: Quantity
  CloudExadataInfrastructureId: String
  CpuCoreCountPerNode: Integer
  DbServers: 
    - String
  Description: String
  DisplayName: String
  IsMtlsEnabledVmCluster: Boolean
  LicenseModel: String
  MaintenanceWindow: 
    MaintenanceWindow
  MemoryPerOracleComputeUnitInGBs: Integer
  OdbNetworkId: String
  ScanListenerPortNonTls: Integer
  ScanListenerPortTls: Integer
  Tags: 
    - Tag
  TimeZone: String
  TotalContainerDatabases: Integer

Step 4: Create ODB Peering Connection

Sort: AWS::ODB::OdbPeeringConnection
Properties:
  DisplayName: String
  OdbNetworkId: String
  PeerNetworkId: String
  Tags: 
    - Tag

Create the CloudFormation stack

To provision your assets with AWS CloudFormation, full the next steps:This CloudFormation template creates the next assets:

• A VPC
• An web gateway
• Two public subnets
• Two personal subnets
• A public route desk
• A personal route desk
• A public route
• Route desk associations for all 4 subnets
• An ODB community
• An ODB peering connection
• An Exadata infrastructure
• An Exadata VM Cluster
• An Autonomous VM Cluster

Earlier than deploying, overview the template rigorously, and for those who don’t want any of those assets, modify the template accordingly.

1. Clone the GitHub repository to your native machine or obtain the script from AWS Samples.
2. Observe the GitHub readme to confirm the stipulations and deploy the CloudFormation stack.
3. Confirm the completion of the stack deployment.

Necessary: When deploying ODB@AWS utilizing AWS CloudFormation, remember that sure useful resource property modifications require full useful resource substitute fairly than in-place updates. Properties resembling CpuCoreCount and DbServers configurations will set off a substitute when modified. Assessment the AWS CloudFormation documentation for an entire record of properties that require substitute earlier than implementing any modifications.

As soon as you’re performed with creating assets you may configure connectivity between the AWS Digital Non-public Cloud (VPC) and the ODB Community for Oracle Database@AWS by

1. Configuring VPC route tables for OdbPeeringConnection
2. Configuring DNS for Oracle Database@AWS
   • An outbound endpoint
     
     The endpoint is required to ship DNS queries to the ODB community.
   • A resolver rule
     
     This rule specifies the area title of the DNS queries that the Route 53 Resolver forwards to the DNS for the ODB community.

Seek advice from community configuration for extra particulars.

Clear up

If you happen to now not require this setup and need to keep away from future expenses, you may delete the assets that you just created as a part of this setup, particularly the ODB community, Exadata Infrastructure and VM ClustersTo delete all different assets that had been launched as a part of the AWS CloudFormation stack, full the next steps:

1. On the AWS CloudFormation console, select Stacks within the navigation pane.
2. Select the stack you created, then select Delete.
3. Select Delete stack when prompted.

For extra data, consult with Deleting a stack on the AWS CloudFormation console.

Abstract

On this submit, we confirmed how you should use AWS CloudFormation to deploy assets in Oracle Database@AWS.

To be taught extra on find out how to get began consult with Getting began with Oracle Database@AWS

In regards to the authors