Skip to main content

Amazon Web Services (AWS) - Request Limit Exceeded

We are using Amazon Web Services (AWS) hosting our little project Today, we are down for quite some time. I will be able to know how long the outage took place once is back online again, thanks to Pingdom monitoring service. As of this time 5:41pm EST AWS Service Health Dashboard ( status for North Virginia delays or not accessible.
  • Amazon CloudWatch (N.Virginia) - Delays is CloudWatch metrics for RDS, ELB and ElasticCache since 12:03 PM PDT
  • Amazon Elastic Compute Cloud (N.Virginia) - Degraded EBS performance in a single Availability Zone since 10:38 AM PDT, still posting updates ...
  • Amazon ElasticCache (N. Virginia) - ElasticCache Cache Nodes experiencing connectivity issues in a single Availability Zone since 11:39 AM PDT ...
  • Amazon Relational Database Service (N. Virginia) - RDS Database instances are experiencing connectivity issues in a single Availability Zone since 11:03 AM PDT
  • AWS Elastic Beanstalk (N. Virginia) - Elevated API failures and delays in Environment since 11:06 AM PDT.
  • And AWS Management Console - Elevated Error Rates since 12:07 PM PDT.
The time posted here is through Service Health Dashboard, so the outage time might be earlier 10-15 minutes of posting.

Cloud service suppose to give businesses a dependable service, 24x7 accesssibility, scalability and uptime 99.95%. Not at this time. Remember what happened to GoDaddy's hosting service last September 10, 2012 millions of businesses (their websites) are down due to their router data table problem. And last October 19, 2012 that took down portion of its customer emails.

Just remember, Cloud Computing Technology still a machine, a pool of servers that managed by human. Hopefully will be back online shortly.

Update: Pingdom Alert: is UP again at 10/22/12/ 06:04:30PM, after 4h 19m of downtime.


Post a Comment

Popular posts from this blog

Office365 - This resource doesn't accept meetings longer than 1440 minutes

When you create a meeting schedule for number of days , you will see an error  "This resource doesn't accept meetings longer than 1440 minutes". By default the mailbox or room was set for a maximum limit of 1440 minutes. Here's how you can disable this limit. Login to the Office 365 Administration Console In Microsoft Office 365 Exchange, click on Manage . In Manage My Orgnization , click the drop down arrow, and click on Select on Another User . This will prompt you to select the mailbox or room to manage. Select a Mailbox or Room , click OK . In Option, click on Settings. In Scheduling Options, un-check the "Limit meeting duration", then click on Save. That's all. You can now schedule a meeting or reserve a room for number of days. Hope this help you. If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

VMware ESXi to add storage

Have you tried to add storage in your VMware environment after the initial setup and configuration? In my case, I needed to add storage for more space to copy virtual machine files. This is also the same approach to access a USB drive to import a vmx and vmdk files (virtual machine and data storage). For this article, I will provide a step by step procedure on how to add your USB drive from one of your Windows Server (or workstation). Let's use a Windows Server 2003 for reading your USB drive. By default, the NFS service is not enable. So, you have to add this service first. Go to Start , Control Panel , Add or Remove Programs , Add/Remove Windows Components , Other Network and Print Services , and select all for Microsoft Services for NFS . You asked, Why enable NFS Service? The VMware is based using Linux, so you need to enable NFS service to share your network drive or folder. Share a USB drive or folder. Open your Windows Explorer and browse your USB drive. In your

Out of Office Reply for Termed Employee

This is a sample Out of Office message that I used for termed employees, unless HR staff specified a different message. === Example for KING.NET Employee === John Doe (employee or consultant)  is no longer with KING.NET effective  June 1, 2013  (termination date). For matters relating to " Project Name here " please direct your concerns to  John Smith at (Manager or Supervisor) . For all other matters, please direct your email to Mary Smith HR at Please call our main office 703-345-6789 if you have other concerns. Thank you. === End of message === I posted this article year 2008 from my old blog. If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn