Amazon AWS Reviews

We are primarily using the solution as real-time streaming to our data-lake. We also have microservices publishing to APIs. It's a customer 360 application. 

We also used the product for migration from on-prem Hadoop to AWS EMR.

We used to spend about $57,000 on-perm with another solution. Then we lifted and shifted to AWS. It came down in cost to about $33,000 while maintaining the same inner software with Apache Kafka. However, we then got into ECS Fargate, and that brought costs down further to about $22,000. When we removed ECS, we moved into a serverless Lambda for 45 million, and our billing is now $8000 per month. It's an amazing amount of savings.

Our clients are the users. We recommend AWS to most of our clients, from the UK government, a shipping company in London, to companies in Washington and Sydney. We maintain their infrastructure on AWS.

We are not partners with AWS. We create and maintain the client's accounts, but the ownership remains with the clients. They pay directly for the AWS services, while we are the administrators who maintain their infrastructure.

AWS offers a lot of services; it's basically all microservices. As the client grows, we scale up to different data centers, security systems, and servers at different levels. We gradually migrate their emails, text messages, and everything else into the AWS infrastructure.

There's something called EC2, which are application servers. They are automatically scalable. They can increase, for example, during peak times like Christmas, depending on the load, and then decrease so the customer doesn't pay a huge amount. It's only during peak times that they automatically increase and then decrease. That's one of the best features of AWS.

Moreover, many Amazon products provide built-in firewalls and security features, eliminating the need for external security solutions. 

To access systems of partner/vendor companies, we maintain an instance to transfer data to our instance, then privately back to us. Basically, a BRAS, B-RAS or BBRAS device.

It improves the speed for us to access vendors, etc. AWS is extremely slow over the internet. Where we have GigE fiber over dedicated OC48 links, and when ping times to Dallas, TX from San Francisco is 30ms RTT on average, AWS is always 20ms higher. To AWS East, it is 70-110ms RTT, and the data transfer almost seems throttled. So I spun up an instance, made a BRAS image, like how DSL customers access the internet, and set up a peer with AWS to transfer data privately, then publicly from our instance to the AWS IP of our vendor, or partner and it has improved response times dramatically. The average API access latency was 250ms, horribly slow - already authenticated, etc. 

We also use it for our Amazon Seller Account and Amazon Vendor Account, where Amazon's systems run. Amazon recently moved their systems to CloudFront, but AWS DNS is awful slow. So the BRAS helps with the DNS as well.

I build infrastructure from the ground up. VPCs, in-depth virtual machines, new websites, migrations from on-prem to AWS, or even between cloud providers. 

Recently, I started building chatbots using Amazon Connect, IVRs, and Lambda. Lambda is also used for the contact center's business logic.

Based on what I do, it's not one service; they're interconnected. For example, when migrating a website from one cloud provider to another, I use EC2, a database system, and Route 53 for DNS. They really depend on each other. 

Now, if I had to pick just one... I like EC2. I can spin up applications and shut them down. When I work on security groups, opening and closing ports, EC2 allows it.

I work on the AWS - the AWS Lambda portions of the Amazon cloud.

It's a good cloud for beginners.

There is no downtime. The solution is reliable. 

Deploying resources on AWS is fairly easy and more secure than any other cloud. That's what our initial impressions are.

I run applications on Amazon AWS. The applications operate on their infrastructure, and I use Amazon AWS to manage this.

Amazon AWS offers flexibility and scalability. The integration process is straightforward, and they provide a reliable backup solution so that applications run without interruptions. Amazon AWS ensures that in the event of downtime for any reason, recovery is straightforward. Their infrastructure is robust, allowing for increased capacity as user volume grows.

I use Amazon AWS for ERP implementation. My responsibility is to integrate our application into the AWS cloud and provide AI solutions to the infrastructure.

AWS is stable and has provided a reliable infrastructure for my organization.

I use it to run our production workload.

I like the auto-scaling functionality and compliance requirements, whichever they are requesting. 

I also appreciate new setup services, which allow customers to easily manage their entire AWS infrastructure through code, and the managed services that handle the heavy lifting for us.