And no, it’s not summoning a few Venture Capital rounds of funding to pour them into a business, nor wasting my life on vacations or my money on gadgets. “What makes us happy?” I have to admit I’ve pursued this goal for a large part of my life. I know that some form of success is linked to happiness, and I know that success is not that esoteric feature that only the gifted among us get to possess. Success, just like happiness, is something we all have.

As you probably know, Site24x7's AWS monitoring capabilities provide complete visibility into resource utilization and performance for key compute resources, storage, and database services powering your application in the Amazon Web Services (AWS) cloud. From here on out, you'll have the power to not only identify issues that might affect application performance, but also automatically invoke operational tasks across multiple AWS resources to resolve them quickly.

In our previous posts, I showed you how to copy your DB and Aurora snapshots to ensure they are preserved beyond the lifetime of your RDS instance. However, those copies were simply second copies in the same region as the original. In this post, I’ll show you how to copy your RDS snapshots to a second region for extra protection. Please note that I will restrict this post to unencrypted snapshots. Copying encrypted snapshots is more involved, so I’ll show that in a separate post.

January brought us many releases, new cool Icinga Web 2 themes and news about upcoming events.

RDS snapshots can be unencrypted or they can be encrypted at rest. Today, best practice is to use encryption-at-rest on your RDS instances and clusters, and to encrypt your RDS snapshots. When you create an RDS snapshot from an RDS instance or cluster, the resulting snapshot will be encrypted if the source instance or cluster is encrypted. But if the source is not encrypted, then your RDS snapshot is not encrypted. When you create an RDS snapshot, you are not given the option to encrypt it.

In terms of collaboration, Structured Threat Information eXpression (STIX) and Trusted Automated eXchange of Indicator Information (TAXII) represent a revolution in the security industry. These protocols transformed the field of threat intelligence from a fragmented collection of information to a unified standard for information sharing. In this blog, I will examine this transition and how it came about.

Frequent online shoppers, travel enthusiasts, parents seeking admissions for their wards, or the average online newsreader are all constantly plugged on to the Internet hoping to see the information they want updated on the respective websites. The only thing they can do is keep refreshing webpages and waiting for a change. Don’t you think that’s a waste of time and energy? You could instead be doing something more productive.

In part one I provided a high level overview of PowerShell and the potential risk it poses to networks. Of course we can only mitigate some PowerShell attacks if we have a trace, so going forward I am assuming that you followed part 1 of this series and enabled: Module Logging, Script Block Logging, Security Process Tracking (4688/4689)

At any given time, most cities have an ongoing infrastructure project that seems to take longer than necessary. Snarled traffic, endless lines of cars, and the ever present orange barrel. A sign has started appearing in those situations. It says "Rome wasn't built in a day. If it was, we would have hired those engineers." It’s clever way to remind people that progress requires patience. Similarly, great service provider businesses aren’t built overnight.