A month ago, Skeddly added a Disable EBS Fast Snapshot Restores action. This action is a fantastic way to ensure you don’t leave EBS snapshots around with Fast Snapshot Restores enabled. That will just be a waste of money. Today, I’m happy to announce a new Skeddly action: Enable EBS Fast Snapshot Restores. This new action allows you to enable, and optionally disable Fast Snapshot Restores on your EBS snapshots.
Redis is an in-memory data store. It’s predominantly a key/value store, so it does not have features in many relational databases. It can be used as a simple database, a cache, or as a pub/sub system. Since it’s all in-memory, it is very fast, but it also requires alot of memory. Amazon Web Services, Microsoft Azure, and Google Cloud Platform all provide their own managed Redis services. The available versions and features vary from provider to provider. Let’s take a closer look.
At Skeddly we’re focused on bringing you the best in AWS help tutorials, AWS scheduler services, and AWS backup services. However, from time to time we like to reach out to other leaders in the AWS space to help you, our blog readers, stay on top of the latest developments and news within the AWS ecosystem.
A few weeks ago, Amazon announced a new feature for EBS snapshots: Amazon EBS Fast Snapshot Restore (FSR). Normally, accessing data on new EBS volumes was quite slow as the data is lazy-loaded from S3. When Fast Snapshot Restore (FSR) has been enabled on an EBS snapshot, new EBS volumes created from that snapshot will allow fast data access. While this feature is very good, it’s very expensive to keep enabled on an EBS snapshot for a long time.
Today, I’m happy to announce a significant new feature to Skeddly: Managed Backups. Once you have created your plan and added resources, Skeddly will create the necessary actions to create and delete those backups according to your desired schedules.
Amazon has enabled a great new feature for cloud security: Default Encryption for New EBS Volumes. When enabled in a region, any new EBS volume that is created will automatically by encrypted with the configured KMS key. At first glance, this sounds great. However, here there be monsters, as the saying goes, if you are copying EBS snapshots or AMI images across AWS accounts.
AWS CodeDeploy is a deployment management service offered by AWS. You can use it to deploy updates of your applications to your EC2 instances, Lambda functions, and on-premises servers. This can be a powerful tool in your CI/CD pipeline. Today, I’m happy to announce a new action: Deploy CodeDeploy Application.
As your AWS usage grows, so will your stockpile of EBS snapshots and AMI images. Many of these are used for backups, while others are used to launch EC2 instances from Auto Scaling groups and EC2 launch templates. As your collection of AMI images grows, you will need to start rotating out the old AMI images.
Today, we’re excited to announce support for Google Cloud Platform. Now, you can manage your Google Compute Engine virtual machine instances using the same advanced scheduling options already available in Skeddly.
When creating EBS snapshots, it’s important that the snapshots be “consistent”. This means that the data on the snapshot is whole and complete. An EBS snapshot can be considered “inconsistent” if not all data was flushed to the filesystem, and/or if an application running on the EC2 instance was mid-write when the EBS snapshot was initiated.
