The keynote watch party for day one of re:Invent 2022 will begin in about 30 minutes!
#｜reinvent-2022
sturdy hamlet
🚀 FSx for ONTAP announcements 🚀
FSx for ONTAP now offers double the maximum throughput and IOPS (up to 4GB/s throughput capacity and 160K provisioned SSD IOPS, from 2GB/s and 80K respectively). With this launch, new 2GB/s and 4GB/s Single-AZ file systems also get an NVMe read cache (which previously only existed on Multi-AZ file systems), which can increase performance up to 6GB/s and 650K PIOPS for cached data reads. These performance improvements are available for new file systems in IAD, CMH, PDX, and DUB. Additionally, all new file systems created in these regions support Nitro-based encryption in transit. Check out the What’s New and redesigned performance section of the docs for more info on the performance improvements, and the Encryption in transit section of the FSx for ONTAP docs for more info on Nitro encryption.
By popular demand, you can now use an in-VPC IP address range as your Multi-AZ FSx for ONTAP file system’s endpoint IP address range, making it easier to access Multi-AZ file systems from other networks (on-premises networks and peered networks in AWS). Starting today, you can create Multi-AZ file systems that you can access from other networks over AWS Transit Gateway without needing to perform any additional routing configuration—making it even quicker and easier to get started. See the What’s New and docs for more info.
FSx for ONTAP is also announcing four new of ease-of-use features that make it even easier to configure and manage your FSx for ONTAP file systems — all of these features are live now and are available to all new and existing file systems in all regions where FSx for ONTAP is available.
You can now more easily assign a snapshot policy to your FSx for ONTAP volumes. Snapshots are browsable read-only images of a volume at a given point in time. Each FSx for ONTAP volume has a snapshot policy, which creates volume snapshots on a predefined schedule. Until today, you could only configure your volumes’ snapshot policies using the ONTAP CLI and REST API. Now, you can also assign a snapshot policy to new or existing volumes using the AWS Management Console and the Amazon FSx CLI and API, making it easier to configure when snapshots are automatically created for your volumes. See the docs for more info.
You can now more easily create FSx for ONTAP data protection (DP) volumes. DP volumes are used as the destination for NetApp SnapMirror, an ONTAP feature that enables you to efficiently replicate data to the same or different ONTAP file system. Until today, you could only create DP volumes using the ONTAP CLI and REST API. Now, you can also create DP volumes using the AWS Management Console and the Amazon FSx CLI and API, making it easier to migrate and protect your data with SnapMirror. See the docs for more info.
You can now configure FSx for ONTAP volumes so that their tags are automatically copied to backups you create. This capability makes it easier to organize, secure, track, and audit your backups. See the docs for more info.
You can now add or remove VPC route tables for your existing FSx for ONTAP Multi-AZ file systems. With Multi-AZ file systems, the endpoints you use to access and manage your data are created in VPC route tables you associate with your file system. Now, you can add or remove route tables for your existing file systems, enabling you to update your file system network configuration as your network evolves. See the docs for more info.
sturdy hamlet
I'll post more updates/announcements as they become available
runic bear
Thanks Chris!
hot tartan
hot tartan
@everyone The Day 2 keynote Watch Party from AWS re:Invent is starting now! Join us! 🤘
That is a "spare no expense" intro. Holy smokes.
Didn't facebook have Cassandra before DynamoDB?
runic bear
I believe that's correct
hot tartan
That's a big one
I need to make a supercut tiktok with all the announcements from all three days. note to self
past panther
Discord question: how can I mute the joining and leaving sounds when watching a stream?
hot tartan
Bottom left, click the gear
Notifications
I wish we could toggle that as a server default, but alas.
past panther
Last piece: I think it's the viewer join/leave sounds
hot tartan
All sounds are underneath that Disable All toggle if you want to do them individually
pastel oak
its more likely just the user Join / user Leave, if you want keep rest of the notifications up 👍
hot tartan
AWS coming after PagerDuty
median lichen
Didn't facebook have Cassandra before DynamoDB?
The author of Dynamo is actually the original developer of Cassandra and he did it when he worked at Facebook. FB released it as open source in like 2007 and it eventually was taken up by Apache (2010). I think Google had a hand in it somewhere in there.
hot tartan
Thought so. Swami out here claiming DynamoDB was the first cloud db (or something along those lines). Retcon'ing history is my fav part of keynotes.
DataZone sounds like some superhybrid of PowerBI
hot tartan
Am I the only one that hears "Tuber Scans"?
hot tartan
Thanks for joining us for today's stream of the keynote! Keep the re:Invent conversation flowing here, and we'll be back tomorrow with Werner Vogels, one of my favorite speakers. I look forward to his keynote every single year.
In case you missed yesterday's keynote from Adam Selipsky, here's the VOD!
runic bear
@here The Day 3 Keynote Watch Party from AWS re:Invent is starting now!
That intro was solid.
white pond
The definitely hit that point home. The fry-by-fry was almost painful to watch
runic bear
Looks warm on stage
white pond
I think he runs hot 🥵 Good thing he took the matrix coat off
runic bear
frozen stream... hmmm
hearty bluff
better
still dust
come on @runic bear you're better than this :-p super j/k
runic bear
Ha - I think that's a fresh half-life shirt.
runic bear
This is really cool
spark galleon
Half life 3 confirmed???? Lol
white pond
There it is... I was wondering how all this simulation talk related to async architectures
sturdy hamlet
a couple more FSx ONTAP launches related to reInvent:
Amazon FSx for NetApp ONTAP extended NVMe read cache support to Single-AZ file systems
On November 28, 2022, Amazon FSx for NetApp ONTAP extended the NVMe read cache support that is already included with Multi-AZ file systems to Single-AZ file systems. With the read cache, customers can drive up to 650,000 IOPS and 6 GB/s of read throughput when reading their frequently-accessed data.
Amazon FSx for NetApp ONTAP has always included an NVMe read cache for Multi-AZ file systems, which reduces read latencies by up to 58%, increases IOPS by up to 4x, and increases throughput by up to 50% compared to data accessed from SSD storage. As of November 28, 2022, new Single-AZ file systems provisioned with at least 2 GB/s of throughput capacity include an NVMe read cache that is up to 5.7 TB in size and provides up to 650,000 IOPS and up to 6 GB/s of throughput. Now, customers can extend the performance benefits that the NVMe read cache offers on Multi-AZ file systems to Single-AZ file systems.
NVMe read caching is included for all new Single-AZ file systems provisioned with at least 2 GB/s of throughput capacity in the following AWS Regions: US East (Ohio), US East (N. Virginia), US West (Oregon), and Europe (Ireland). For more information, please visit the FSx for ONTAP documentation and the FSx for NetApp ONTAP product page.
Amazon FSx for NetApp ONTAP now supports Nitro-based encryption of data in transit
As of November 28, 2022, Amazon FSx for NetApp ONTAP provides automatic encryption of data in transit between Nitro-based compute instances and new FSx for ONTAP file systems.
With FSx for ONTAP, before this launch, customers needed to configure Kerberos to encrypt data in transit over the SMB 3.0+ and NFSv3+ protocols. After this launch, FSx for ONTAP supports automatic, Nitro-based encryption of data in transit that doesn’t rely on Kerberos. This new feature is designed to leverage Nitro-based offload capabilities to automatically encrypt in-transit traffic with no impact on network performance. With Nitro-based encryption, data is encrypted in transit when accessed directly from supported instance types in the same VPC (or peered VPC).
Automatic encryption of data in transit is supported between new FSx for ONTAP file systems and Nitro-based compute instances in these AWS Regions: US East (Ohio), US East (N. Virginia), US West (Oregon), and Europe (Ireland). For more information, please visit the FSx for ONTAP documentation and the FSx for ONTAP product page.
hot tartan
UPDATES for Amazon FSx for NetApp ONTAP from AWS re:Invent 2022
https://youtu.be/nDFsQJdeP1k
