Share your experience using Oracle Compute Cloud Service

In this course that I'm doing of Terraform, we use Amazon EC2 Auto Scaling to create the instances to run all the pipelines, integrating to S3 and also EMR, but not at work. This is just by course.

Professionally, this is my first time working with this solution. Currently, I'm using S3 and AWS Glue. From personal experience, I have used Amazon EC2 Auto Scaling, Athena, Glue, S3, Redshift, and EMR (Elastic MapReduce).

The auto scaling feature is beneficial. Users don't need Terraform or another tool to automate this kind of situation. Obviously, if something bigger is required, another tool would be necessary, but when configuring Amazon EC2 Auto Scaling without wanting to spend excessive money, it can be scaled up during peak demand times and scaled down during particular days or periods.

It is straightforward because all the tools at AWS can be visualized. Users can interact with this in a visual way without needing to use the terminal for configuration. The documentation is very straightforward, and if someone understands the concept of other virtual machines, transitioning to Amazon EC2 Auto Scaling is simple.

The service offers 99.9999% availability. We have high availability, and I haven't experienced any downtime during my usage periods.

Integration with LLM would be beneficial as many services are implementing this functionality. This could help people configure the service.

The ability to ask questions about documentation through a chat interface would be valuable.

I am uncertain about describing issues because I don't have deep knowledge about this. I understand how this works and have used this to run some pipelines, but I may not have sufficient knowledge to describe specific problems.

I haven't experienced any deployment issues.

The stability of Amazon EC2 Auto Scaling rates a 10. This feature performs exceptionally.

I implemented scaling in the AWS environment. I completed a lab where we used CloudWatch to scale down and scale up at specified times.

This was implemented in an AWS lab environment. The scaling feature appears to be embedded in the Amazon EC2 Auto Scaling price.

The only alternative solution would be on-premise, though virtual machines can be created using Docker on-premise, but it isn't quite the same. A comparable solution would be on Azure, but I haven't used that platform.

The setup process is very straightforward. Everything can be configured using the interface, including choosing images, storage, processing, and CPUs. It is easier than Docker configuration. For anyone familiar with virtual machine deployment who wants to use this service, the process is very simple and shouldn't present any problems.

It has been valuable learning more about how this service is used.

The service requires version specification to maintain control over pipelines. Users can decide whether to let Amazon manage the EC2 images or manage them independently.

I rate Amazon EC2 Auto Scaling a 10 out of 10.

Our main use case for Amazon Virtual Private Cloud is that it is our main network solution. It is mainly used to connect our nodes and also connect our on-premise nodes to the AWS VPC using the site-to-site connection.

The most beneficial feature of Amazon Virtual Private Cloud for our use case is the site-to-site connection, allowing our data centers to connect to the AWS EC2 nodes, which is currently the most useful feature for us.

The Elastic Network Interface is the main component of our networking services within Amazon Virtual Private Cloud, allowing us to connect to our nodes and enabling all node-to-node communication, node-to-customer, and customer-to-node interactions. It is a really helpful feature for us.

Amazon Virtual Private Cloud allows the nodes to talk to each other, enhances our security with its security group feature, and the network access list can isolate attackers, while the subnet service organizes our nodes' network topology and provides access to customers. It is a really great feature, and I would highly recommend it.

It would be great if we could use the AWS Direct Connect in Mongolia. That is our only issue with Amazon Virtual Private Cloud; other than that, it works well.

Our company has been working with the Amazon Virtual Private Cloud service for two years now.

We haven't had any challenges with the initial setup of Amazon Virtual Private Cloud. Everything was set up smoothly with just a few clicks.

I don't have any issues with Amazon Virtual Private Cloud so far, as most of it has been really great.

We haven't had any issues with data breaches and DDoS attacks.

We haven't asked anything regarding the EKS from AWS customer support for the Amazon Virtual Private Cloud product.

We mainly talked about other billing solutions, and while we have discussed Amazon Virtual Private Cloud with customer support, there were no questions regarding EKS.

Positive

Our previous network infrastructure before moving to Amazon Virtual Private Cloud was based on the VSphere, the VMware solution.

We decided to switch to Amazon Virtual Private Cloud mainly because it's AWS's native networking solution, providing us with peace of mind and fewer issues in the future.

We haven't had any challenges with the initial setup of Amazon Virtual Private Cloud. Everything was set up smoothly with just a few clicks.

I find the pricing of Amazon Virtual Private Cloud reasonable.

We've looked into other cloud solutions before moving to Amazon Virtual Private Cloud, but we haven't considered the benefits and disadvantages of the networking services, just the main cloud as a whole.

We have considered using the AWS Direct Connect, but there isn't any available solution for AWS Direct Connect in Mongolia, so we've opted for the site-to-site connection through Amazon Virtual Private Cloud.

We are doing fine with our other services. Most of our services are performing well regarding any other products or solutions that we're working with.

For the Amazon Virtual Private Cloud service, we haven't seen any measurable improvements in our workflow; we just moved from one networking infrastructure to another, so we haven't had any challenges. The only upside I can think of is that we can easily migrate to Amazon Virtual Private Cloud from our data centers.

I'm not really familiar with the pros and cons of Amazon Virtual Private Cloud compared to other competitors on the market, as I think it's just a standard networking service similar to other clouds.

I would recommend Amazon Virtual Private Cloud to other organizations considering it for their environment.

On a scale of 1-10, I rate Amazon Virtual Private Cloud a 9 out of 10.