Amazon Elastic Container Service (Amazon ECS) now supports the use of Amazon FSx for Windows File Server in Amazon ECS task definitions. With this capability, you can now use persistent, shared storage across ECS containers. Customers can use Amazon FSx for their Windows containers in task definitions compatible with the EC2 launch type. Amazon ECS tasks using Amazon FSx will automatically mount the file systems specified by the customer in the task definition and make them available to the containers in the task across all availability zones in an AWS Region.
AWS Storage Gateway enhances security by introducing access-based enumeration for File Gateway
AWS Storage Gateway introduces access-based enumeration for File Gateway, enabling you to protect sensitive information by allowing you to prevent users from seeing SMB file shares, folders, and files that they would not be able to open based on their access permissions.
AMI Lifecycle Management now available with Data Lifecycle Manager
Amazon Data Lifecycle Manager (DLM) now supports the creation and retention of EBS-backed Amazon Machine Images (AMIs). In addition to defining policies that provide a simple, automated way to back up data stored on EBS volumes, you can now create policies targeting EC2 instances to create EBS-backed AMIs . With this feature, you no longer have to rely on custom scripts to manage your AMIs. Nor will you need to manually delete associated snapshots once an AMI has been de-registered.
AWS Storage Gateway adds schedule-based network bandwidth throttling for Tape and Volume Gateway
AWS Storage Gateway now supports schedule-based network bandwidth throttling for Tape Gateway and Volume Gateway, enabling you to optimize network use between your data center and AWS for data synchronization.
AWS Storage Gateway increases local storage cache by 4x for Tape and Volume Gateway
AWS Storage Gateway now supports local storage cache of up to 64 TB for Tape Gateway and Volume Gateway, enabling low-latency access to larger working datasets at your premises. Now, you can easily scale your gateway’s local cache to manage more of your application data closer to your on-premises applications and users.
AWS Storage Gateway simplifies in-cloud processing by adding file-level upload notifications for File Gateway
AWS Storage Gateway introduces file-level upload notifications for File Gateway, enabling you to trigger automated workflows in the cloud and easily process on-premises file data stored with AWS as Amazon Simple Storage Service (Amazon S3) objects.
AWS announces 40% price reduction for Amazon Elastic Block Store (EBS) Cold HDD (sc1) volumes
Today, we are reducing the price of Amazon EBS Cold HDD (sc1) volumes by 40%, or an estimated $160 for each 16TB sc1 volume.
AWS Snowball Edge now supports Windows operating systems
AWS Snowball Edge now supports Windows operating systems, including Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019. Previously, you were able to run instances on Snowball devices using either the Ubuntu or CentOS Linux operating systems. Now, with support for Windows, you can run your Windows-based workloads at the edge on Snowball Edge Compute Optimized and Snowball Edge Storage Optimized devices.
AWS DataSync announces fully automated transfers between AWS Storage services
AWS DataSync can now transfer billions of files or objects between Amazon Simple Storage Service (Amazon S3), Amazon Elastic File System (EFS), or Amazon FSx for Windows File Server, with just a few clicks in the DataSync console. This enables you to easily replicate data between your managed file systems for business continuity, as well as copy portions of your data to different buckets or file systems as needed by evolving application requirements.
You can now adjust the network bandwidth used by a running AWS DataSync task
AWS DataSync now enables you to have more granular control over the portion of network bandwidth used to transfer your data. In addition to the existing capability allowing you to set a maximum network bandwidth limit per task, you can now increase or decrease this limit while the task is running. This enables you to minimize impact on other users or applications when a task spans multiple days.