One difficult task for the AWS account administrator is to keep track of used and unused resources. That’s why we’re adding more actions to help track down unused resources. Today, we’re happy to announce a new action: Delete Unused Elastic IP Addresses.
Sometimes it's necessary to run a maintenance API script in your LogicMonitor portal. For example, I move decommissioned devices into a specific folder because I no longer want to receive any alerts on these devices. An API script helps automate the process by running once a day to disable alerts on any new devices added to this folder.
Last week, I wrote A Beginner’s Guide to Deadlocks in Amazon RDS. This week, I’d like to lay out my 10 years of experience about how to avoid deadlocks altogether. Often times, this will be out of the hands of operations people, but you can still move for dev changes based on issues in production. The more knowledgeable you are about deadlocks in general, the more they will lean on you as a resource with wisdom, not a totalitarian barking rules.
We’re back with another giveaway, and this time it includes every icon released by Amazon in their AWS Architecture Icon PowerPoint deck. You can find the original deck here. The link below provides an svg file for every service and resource icon provided by Amazon in the PowerPoint file each grouped by the service category. That is a total of over 300 icons for you to use when creating your architecture diagrams, in SVG format so you never have to worry about size or screen resolution.
Amazon Web Services (AWS) is one of the most popular public cloud providers today. Over the years, AWS’ services have expanded from cloud computing to application development and security. To retain the reliability, availability, and performance of your AWS instances, an AWS cloud monitoring solution is a must. It’s critical for AWS monitoring tools to collect data from all parts of your AWS service, so that multi-point failure can be easily debugged.
With the adoption of Agile methodology, it is expected to add new features quickly to an application or product. However, if the process of moving from Dev > Test > Stage > Prod is taking weeks or months – then you have a problem at hand (big or small, varies on the type of app/product). Customer will be demanding new features and the development team will be able to build/ create them quickly, which is a good thing!
My career as a software engineer started in 2007 at Purdue University. I was working in the Linux kernel and researching how data was shuffled between the kernel and the user application layers. This was happening in huge clusters of machines that all talked to each other using OpenMPI — how supercomputers, like those at Los Alamos National Labs, operate to perform their enormous calculations around meteorology, physics, chemistry, etc.
A few weeks back, eG Innovations collaborated with David Wilkinson and conducted a webinar on the topic “Is Citrix Cloud Enterprise Ready? Best Practices to get the Most Out of Citrix Cloud Deployments.” Citrix Cloud implementations are growing in the industry today, and as organizations begin evaluating their cloud options, Citrix administration teams want to understand how Citrix Cloud will sustain, scale and be supported in lieu of on-premises Citrix deployments.
Although AWS sometimes feels like magic, it’s just software that controls capacity and allocation on their previously provisioned hardware. RDS is one of the services that can feel especially magic, because of the general difficulty and drudgery required to set up and manage a production database. In a matter of minutes, anyone can have a production database, complete with replication, automatic failover, backup schedules, and point-in-time recovery.
A little over a month ago, Jeremy Daly introduced the concept of the #serverless bubble coming out of #ServerlessNYC. In his tweet he said “if you’re in it, a serverless solution seems intuitive. If you’re not, the paradigm shift can seem overwhelming (& unapproachable).”
