Notes from our work with AWS, DevOps and security: news and new features, fixes for common problems, and how we solved real client issues.
Recently AWS announced support for Elasticsearch 5.1 in their Elasticsearch Service. Today, I tried to upgrade an existing CloudFormation stack, previously using Elasticsearch 2.3, to the new version and, after a very long wait, CloudFormation rolled back the stack with the following error: “Creating Elasticsearch Domain did not stabilize”. Here’s what I did to solve it.
Management page of Redshift in AWS Console does not currently allow you to add or modify tags on your clusters. That doesn’t mean that Redshift resources cannot be tagged - almost everything from clusters to parameters groups can be tagged through the Tag Editor.
Since AWS released CloudWatch Logs and allowed for automated streaming of CloudTrail events into CloudWatch, monitoring API usage with CloudWatch metrics and alerts has become increasingly popular. It’s incredibly easy to set up and add custom alerts on almost any API event. But is it actually going to notify you when an unauthorized person gains access?
AWS Redshift is a big data storage (“data warehousing”) solution for analytics. Based on PostgreSQL 8, it can combine up to 128 largest nodes, giving you 2 petabytes for your data. Well, almost. You don’t get ALL that for your data.
Since publishing this post, AWS reached out to us about the RR pricing. See bottom of the post for the update.
When storing data in S3, at some point everyone asks the question about storage classes. At first glance it looks more or less simple - if you’re accessing your data less often, or it’s not very important, you can pay less. Until you look into details, find all the asterisks and compare the actual numbers.
