ACUVA

Your Accurate Search for New Technology

Restore running applications to pre-update state in Amazon Managed Service for Apache Flink

By

You can now restore your Amazon Managed Service for Apache Flink application to the previous running version and application state from the most recent, successful snapshot. This feature will work when your application is running and is most useful when you want to immediately rollback to the previous application version to mitigate downstream impact of an application update. Prior to this launch, you could only rollback applications that were in updating or autoscaling statuses.  Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Amazon Managed Service for Apache Flink reduces the complexity of building and managing Apache Flink applications and integrates with Amazon Managed Streaming for Apache Kafka (Amazon MSK), Amazon Kinesis Data Streams, Amazon OpenSearch Service, Amazon DynamoDB streams, Amazon Simple Storage Service (Amazon S3), custom integrations, and more using built-in connectors.  For a list of the AWS Regions where Amazon Managed Service for Apache Flink is available, please see the AWS Region Table. You can learn more about Amazon Managed Service for Apache Flink here.

Amazon Data Lifecycle Manager default policies now supports AWS Organizations

By

Customers can now create and manage default policies across their entire organization or organizational unit (OU) with AWS CloudFormation StackSets. Default policies work in conjunction with customers’ existing backup mechanisms to only create EBS-backed AMIs and EBS Snapshots of instances and volumes without recent backups. This helps administrators ensure that all member accounts have comprehensive backup protection without creating duplicate backups or increasing management overhead and cost.  Amazon Data Lifecycle Manager default policies target instances and/or volumes in a region and will automate the creation and retention of backups for resources which have not been recently backed-up. Customers can set their default policy to exclude non-critical workloads by specifying exclusion parameters such as volume type, resource tags, and boot volumes. Now with CloudFormation StackSets and the provided sample templates, administrators can easily create and manage default policies in all AWS Regions and in all member accounts to ensure they are all compliant with the organization’s back up requirements. Amazon Data Lifecycle Manager default policies and the CloudFormation StackSets sample template for default policies are available in all AWS Regions. There is no cost associated with creating and managing these policies. Customers only pay for the storage cost associated with any EBS Snapshots that are created. The CloudFormation StackSets sample templates to “Create and manage default policies for EBS Snapshots and EBS-backed Amazon Machine Images (AMIs)” are now available through the AWS Management Console, AWS SDKs, or the AWS Command Line Interface (CLI). To learn about this feature, read the blogpost and our documentation. 

AWS CodePipeline supports stage level manual and automated rollback

By

AWS CodePipeline V2 type pipelines now support stage level rollback to help customers to confidently deploy changes to their production environment. When a pipeline execution fails in a stage due to any action(s) failing, customers can quickly get that stage to a known good state by rolling back to a previously successful pipeline execution in that stage. Customers can roll back changes in any stage, whether succeeded or failed, except the Source stage. Customers can either manually initiate a rollback for a stage from the console, API, CLI or SDK, or configure a stage in the pipeline definition to automatically opt in to rollback in case of failure. When a rollback is initiated, a new pipeline execution is started in that stage with the changes from the selected pipeline execution (manual rollback), or with the source changes from the most recent successful pipeline execution in that stage (automated rollback).  To learn more about using manual and automated rollbacks in your pipeline, visit our documentation. For more information about AWS CodePipeline, visit our product page. Stage level rollback is available in all regions where AWS CodePipeline is supported.

Scroll Up