Changes in technology are typically fast-paced and evolution is always imminent. AWS is great for providing an IaaS platform and Oracle is well-known for its platform solutions. Oracle on the AWS platform is a strong choice for customers to consider. The AWS IaaS platform offers a scalable, secure, highly available and secure infrastructure for Oracle platform solutions such as Database, Middleware and applications. Also, Oracle allows customers to choose IaaS solutions for their platform technology. Interestingly, AWS also offers solid platform solutions on Database on which Oracle Database workloads can be migrated. There are a lot of options, but they all come with complexity regarding choice, commercial and contractual positions.
Three critical factors to consider when moving an Oracle workload to AWS are:
1.) Flavors available on AWS for Oracle, there are two options:
- Using Amazon Relational Database Service (Amazon RDS) for Oracle
- Running a self –managed Oracle Database directly on Amazon Elastic Compute Cloud (Amazon EC2)
- Migrating a full Oracle workload to Amazon Aurora or PostgreSQL on AWS
2.) Understanding the technical limitations of your options:
- Amazon RDS can support up to 6TB and a maximum of 30,000 IOPS
- Amazon RDS is not suitable for functionalities of managing backups or point in time recoveries
- AWS does not currently enable Oracle Real Application Clusters (RAC) natively on either Amazon RDS or EC2
- AWS does allow all major version instances of Oracle products to be deployed on AWS.
- AWS offers its best of breed solutions for scalability, security and high availability
3.) Understanding the licensing and commercial implications:
- Except for one option of Amazon RDS for Oracle database (standard one), all other options on AWS requires Bring Your Own License (BYOL) of Oracle
- With the recent changes of Oracle licensing policies since April, 2017, the BYOL Oracle license requirement on AWS has doubled, however, the customer needs to adhere to Oracle support policy restrictions for such scenarios. Oracle’s own PaaS (DBaaS and other flavors) don’t require BYOL
Overall, any decision to move Oracle workloads into AWS needs information backup and experienced advisory services regarding existing Oracle usage, contracts, licensing, technology dependency and commercial models. Additional detailed inferences are available at this blog.
SoftwareONE has a dedicated team of experts to address this challenge and provide expert advisory services on this important decision making process.