Amazon Elastic Compute Cloud (EC2) vs Oracle Cloud Infrastructure

• EC2 has wide variety of machine configurations. If the intended solutions are memory heavy, CPU heavy, GPU heavy or IO heavy, EC2 will provide proper machine configurations as per the requirements.
• EC2 has lot of Machine Images to setup OS and required softwares. It also allows you to create the image of your own disk. This facilitates user to stop the EC2 instance without loosing the work. It helps to reduce the bill. The image can be attached again to EC2 to start from the same place from where it was left.
• Amazon allows different way to obtain instances like on-demand, spot and reserved. Depending upon the need, one can take wise decision to save cost and address the situation in the best possible way.

Read full review

• Block Volume provides durability and stability to data. IOPS can be changed on the fly. Always stay true to the promised performance.
• Block Volume can be encrypted with ease to meet compliance. Can also be easily integrated with OCI vault service for extra security.
• Object Storage and File Storage are other forms of storage that are secure and extremely easy to configure. FSS is one of the best in the industry when it comes to reliability and performance.
• SSD block volumes are persistent in OCI unlike many other clouds.

Read full review

• The UI of AWS is quite hard to familiarize with, along with the infrastructure setup. It's a conglomeration of hundreds of acronyms specific to AWS that must be understood including their minutiae to effectively run a cloud deployment. While AWS' documentation is extensive, their beginner-focused guides could use work.
• Instances become incredibly hard to manage after a critical mass, forcing companies to create their own management applications to fill the void that AWS leaves. Along with this, AWS' SDKs can be very poorly documented making this task exponentially more difficult.
• If you lose your SSH key that is released with the creation of the instance, you lose complete access to the server. While I understand the reasoning behind this decision, MFA recovery would be a nice touch.

Read full review

• Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) is a fully managed service that makes it a little hard sometimes to fine tune HPC workloads, for example AI/Deep learning training where a lot of data transfer and compute is needed.
• The initial setup can certainly be improved with less steps to make it faster and easier to deploy compared to the competition, for example Google Kubernetes Engine (GKE).
• Documentation and best practice documentation for OKE can be improved especially since there are not a lot of customer references available for large scale deployments that need fine tuned performance.

Read full review

• Instance procurement time has become negligible with EC2. Any developer can provision an instance very quickly and companies can move towards automation of CI/CD pipelines and auto provisioning of EC2s.
• Companies do not have to spend money in managing infrastructures, data centers, staff to manage these, networking, connectivity etc. All this will be taken care by AWS and EC2 can be used to run your enterprise softwares and custom applications.
• If not correctly monitored EC2 prices can run up very quickly. So proper monitoring has to be in place in your organization. Non-prod and dev EC2 servers should be brought down in evening and night.

Read full review

• We have been able to test at low scale complex solutions using OCI
• The Free Tier option can be used to test easy of configuration and deployment
• Since pricing is in U.S. Dollars, it can be a problem in countries with less stable currencies

Read full review