Sign Iowa Travel Agency Agreement Online

Document type sign travel agency agreement iowa online

all right well thanks for joining us today my name is Joe travel Eenie I'm one of the product managers on the Amazon ESS to a NAB Darrell Osbourne I'm a Solutions Architect with the Amazon file services teams and we're gonna go over a new cost optimized storage class for Amazon Elastic file system called infrequent access so here's what we plan on covering today first we're going to go over EFS at a high level for those that might not be familiar with the FS or need a refresher then we'll talk about the new I a infrequent access storage class once designed for how it works and then we'll go over the the relatively new AWS data sink service and show how it can be used to quickly load data into an EFS file system and finally we'll go over any questions you might have so with that let's jump right in so when we designed the FS we had a couple of core tenants in mind first and foremost EFS is simple so we removed the complexity of deploying patching maintaining any infrastructure needed to provide file system storage and it's a fully managed service it's super easy to use with just a few clicks you can create a scaleable native file system in just seconds and next another tenant is that EFS is fully elastic meaning you don't need to provision your capacity up front your file system automatically grows and shrinks as you add or remove files and finally EFS is scalable so each EFS file system is able to grow to petabytes of capacity in performance even scales automatically with the size of the file system if you wanted to we do have knobs available for tuning performance if that's something you're interested in and we'll talk a little bit about that in just a bit and across these tenants we designed the FS as a platform to provide highly available and highly durable data storage so EFS is designed for 11 nines of data durability we we offer a service level agreement that's targeting three nines of availability for your file system resources okay so beyond those tenants you know simple elastic scalable let's talk a little bit more about some of the other features that EFS provides you know first from a performance perspective EFS offers two different file system performance modes a general-purpose mode in another that we call max IO so the trade-off between those two performance modes is essentially one has lower metadata latency versus the other having in operations per second limit so GP mode provides the lowest metadata operational agencies that EFS can can offer while max i oh mon is not subject to the io limits and can provide the highest level of aggregate throughput that EFS can offer so speaking of throughput EFS also Orford offers two throughput modes there's the default bursting throughput mode where throughput will scale linearly with the size of the filesystem it allows for periodic bursting above that that fixed rate as well as a provisioned throughput mode where you can provision exactly what you need for more consistent in deterministic throughput performance another key feature is the shared access model of EFS so you can access EFS across thousands of clients simultaneously and across multiple availability zones and we also support accessing EFS across V PC peered connections over VPN or from a data center Colo via AWS direct connect and just one other highlight - from a security and compliance perspective EFS supports encryption of data at rest and in transit and we offer compliance with you know a number of programs such as sauk ISO PCI DSS as well as HIPAA among others okay so just a little bit more depth on how EFS works before moving on to talk about infrequent access so to provide the high levels of availability and durability EFS replicates data within in across availability zones under the hood we're creating resources called mount targets and those are in your V PC as a customer and those are used to serve the EFS traffic so you don't really need to have high touch points with your mount targets if you mount a file system using its dns name and EFS actually provides a mount helper that makes this even simpler you just provide the file system ID will automatically resolve the dns - to the mount target that's in the same availability zone as your clients so it's co-located you get max wear performance in that way you know having any cross ez network charges or anything like that I mean there's no single points of failure the mountain targets themselves are also designed to be highly available and then on the backend file systems are distributed across an unconstrained number of storage servers so you're avoiding any typical bottleneck associated with the traditional network filer and EFS is available in 1280 of AWS regions all across the world with more to come okay so let's briefly talk about some of the economics of using EFS and we'll actually go over a total cost of ownership model later on in the webinar so it's pretty simple there are no minimum commitments or upfront fees as we mentioned earlier no need to provision storage and advance and there's no other hidden fees or charges that you need to worry about okay so that that's a quick recap of EFS overall and now we're going to focus on the new EFS infrequent access storage class and Darrel will will demonstrate how to use data singh to quickly load data into EFS and take advantage of all these cool features so recall that you know when you're using EFS like I just mentioned on top of it being fully managed you're getting all those features the high availability high durability elasticity and scalability natively right out of the box and customers often tell us they love how simple EFS is to use but it can become quite expensive to store large amounts of data for long periods of time so what we did we went off and we looked at different ways that we can extend the lowest possible price point while still providing all those features that customers expect so EFS has been in general availability for almost three years now we have plenty of usage data to analyze what we found is that most files that customers store in EFS aren't really accessed a lot and they actually tend to be accessed less frequently as they get older basically after they've been created you might see a flurry of activity to start an active workload and then they kind of aged off over time and then they're they're not frequently access but they need to be there they need to be accessible and readily available and called upon so right there was an opportunity what if we could automatically lower the cost of boring files as their access patterns are changing into again our tailing off and becoming access less frequently so that's exactly what we did so the Amazon infrequent acts Amazon EFS infrequent access or EFS ia it's a new storage class that can save customers up to 85 percent compared to the pre-existent storage class which were not we're now calling EFS standard customers can use EFS ia to cost-effectively store larger amounts of data in in their file systems in by doing so expand their their usage of EFS to an even wider set of applications in beta in using EFS ia just like EFS overall it's super easy it doesn't require any changes to existing applications EFS provides a single file system namespace and it's transparently serving data from both storage classes standard and ia to get data into the FSIA you're just enabling a lifecycle management capability for your file system and that automatically moves files from standard into IA and by doing so allows you to realize that that savings of up to 85% okay so how does it work first you just create a file system like I just mentioned the file systems are transparently serving data from both storage classes you have that common file system namespace so you don't have to worry about which of your files are actively used and which are infrequently accessed then all you need to do is really just enable lifecycle management for your file system and when you do that any files that aren't accessed for 30 days automatically get moved from the EFS standard class into the infrequent access storage class so with both you know the I is storage class and lifecycle management we're eliminating the need to manually manage your data to optimize for cost and again all EFS features are supported in conjunction with IA all right so when should you use the FSIA so let's talk a little bit about the use cases that we see so again generally speaking EFS ia we designed it to cost-effectively store files that aren't access to every day but again need to be readily accessible to applications so we see you know different applications with that profile in a number of different areas for starters sometimes you know you simply need to keep files around whether that's for a regular regulatory retention purpose or for satisfying an audit requirement other times you might just want to keep a quick backup or failover site around and help you meet a tight recovery time objective for RTO and we also have customers running simulations and other types of iterative algorithms performing data analytics so you see that in areas like genomics Health Sciences electronic design automation geospatial analytics in oil and gas like oftentimes those those out algorithms and applications need to reference a historical data set which you know isn't accessed very often but again needs to be readily accessible in another area where EF si is a good fit is in the document management space so things like legal research in HR staffing systems they have a treasure trove of documents that mostly sit idle but otherwise are well served by a file system in applications that expect file system compatibility so it's a really you know I is a really good cost optimization measure for those types of use cases so as I mentioned a little bit ago we're now calling the pre-existent EFS product our general purpose offering the standard storage class it has a super simple all up price point of 30 cents per gigabyte per month there are no network charges no other fees and you only pay for what you use with EFS IA its cost optimized again for files that aren't accessed every day so in addition to a storage price point you also pay a fee each time you access or read or write to a file that's stored in AIA so this price structure allows us to extend the lowest possible storage cost for infrequently access files in that storage cost EFS ia cost four and a half gigabyte four and a half cents per gigabyte per month in an access to I files cost one cent per gigabyte and those prices are in the u.s. Northern Virginia region i fs is priced similarly to EFS standard in other regions and you can see that on our website and the pricing table okay so with the basics out of the way I'm gonna go a little bit deeper on how lifecycle management actually works so like we talked about there's a predefined policy that automatically moves files after 30 days of not being accessed so for file systems that were created after the launch of Yee FSIA you can enable or disable lifecycle management at any time but you know keep in mind that once lifecycle management moves a file from the standard storage class into the ia storage class that file will remain there indefinitely so you can always bring it back by creating a copy of the file you know somewhere else in the file system within the same folder or different folder you know if you find that ok now you have us that have become frequently access you want to bring them back into standard you can do that by creating a file and you would do that for performance reasons and I'll talk about that in just a minute so for the purposes of lifecycle management in the aiya storage class you know what we mean by data access so what we mean is any read from or write to the file content so EFS uses an internal timer that's tracking the reads and writes on a per file things like doing an LS you know listing the contents of her directory any sort of file metadata operation doesn't constitute access from an ia perspective in a lifecycle management perspective so that doesn't affect the timer we're using internally to track the last time you know any file was read from or written to so speaking of metadata we're keeping file metadata itself so things like the file name the owners of the file its attributes you know access control and so on that's all stored on EFS standard so we chose to do that to provide consistent metadata performance across files in standard and ia right so again keep in mind you have that single file system namespace in what storage class any files on is transparent to users and applications and I'll talk again about ia performance in just a second but what we're storing we're also storing files that are smaller than 128 kilobytes will always store those on EFS standard so that allows us to provide the best user experience at the lowest possible cost and that was based on our analysis of EFS usage patterns overall so on the performance front EFS ia has slightly higher first by agencies as compared to EFS standard you'll see on average single-digit millisecond latency s4 reads and writes to standard whereas you'll see double-digit millisecond latency is on average for reads and writes to infrequent access that being said you can drive the same level of throughput against files in IA as files in EFS standard and it doesn't matter what per throughput mode you're using whether that's the default EFS bursting throughput mode or if you're using EFS provision throughput so one thing to keep in mind there is that your file systems baseline throughput it's going to scale with the amount of storage you have in the EFS standard storage class that baseline throughput that's used to calculate your burst credits and your burst rate if you're in EFS bursting mode and it's also used to calculate the amount you build when using provision throughput so for provision through but you only pay for the premium of throughput that you've provisioned relative to what you're entitled to with the ESS bursting model so it's kind of the best of both worlds when it comes to that and finally workload priorities so lifecycle management is the mechanism that's transitioning files from one class to another those transitions happen in the background and add a lower priority than act to file system workload so until a file is fully transitioned by lifecycle management into ia it's stored on EFS standard and build at standard grade so speaking of billing just a few more details on how we meet her in bill for EFS IA so EFS IA storage just like EFS standard storage is metered in four kilobyte increments so reads from the FSIA and lifecycle transitions to EFS ia are metered in one megabyte increments so you might have noticed why did I say lifecycle transitions and not rights well I kind of mean the same thing by that so all rights to EFS first land on EFS standard and then lifecycle track lifecycle management transitions them from the standard storage class into the ia storage class so if you update you know if you write to a file you know you overwrite a file append to it that's an EFS IA already lifecycle management will transition that updated file content a maximum of once per day and then finally when you look at your EFS bill you'll see your infrequent access storage you know split out separately from your standard storage and you'll also see read requests in rate request I a broken out separately so when you see a write request on your bill what you really are seeing are the lifecycle management transitions of file content into I okay so that's that's it really just in terms of what EFS ia is and how it works it's really easy to get started you you just create a file system and you click the check box in the console to enable lifecycle manager cool so now we're gonna talk a little bit about AWS data sink and then I'll hand it off to Daryl to you know to show you know live how we you know piece the puzzle the puzzle pieces together to make this all work in confluence okay so what is AWS data sink fundamentally you know it's its name as its name reflects to say it's a online transfer service so what we're doing with data sink is we're combining the speed and reliability of you know traditional network acceleration techniques with t e cost-effectiveness of open source software so you can use Data Sync to transfer at up to 10 times as fast compared to you know open source tools so it's it's really fast it's easy to use it's secure and reliable it's natively integrated with services like EFS and its cost effective so here's a little diagram on how data sync works so it's compatible with NFS file systems including EFS you'll deploy a Data Sync agent you know you typically on-premises Dera will show you some some things we have in the in the pipeline coming soon it uses TLS to securely transfer data to you know the data sink service endpoint and then from there it's optimized to read from and write to both Amazon s3 as well as Amazon EFS so under the hood Data Sync is using a purpose-built protocol it's multi-threaded it takes advantage of parallelism it can scale across multiple agents there's some optimization techniques in terms of incremental transfers compression sparse file detection so you're only you know you're only sending over the wire what what absolutely needs to be sent to get the job done and like we talked about before you know integrated with both s3 and EFS to be you know native and optimized and you can also configure you know there's some knobs to tune on you know throughput and other sorts of performance characteristics so data sync helps you simplify the management of moving data you can set it up in the console you or you can use a programmatic technique like the AWS CLI the command-line interface or the SDK the software development kit there's a really minimal infrastructure to deploy or manage in AWS you have that agent but you know that agents is fully managed in terms of updating its software providing patching that's not something that you really need to care and feed that's all automated in streamline for you and you don't have to get into the business of like building a manifest and preserving you know your file system structure like that metadata across different storage systems in storage services is all handled by data sake so in addition to transferring you know in transferring over the wire using TLS Data Sync also supports the key management servicer can ask for encryption of data at rest with the various Adobe of services namely s3 and EFS it can access services within your VPC it has built-in validation and automatic recovery from any sort of failure in transmission in on top of just the s3 and EFS integration you also have integration with things like Amazon Cloud wash for monitoring you can use cloud watch logs you can track your data movement you can audit your usage it's integrated with iam permissions so you can kind of lock down which of your users can perform these activities and you have cloud trail to audit the API call stack as well likewise Data Sync is also compliant with PCI DSS and in HIPAA and other compliance programs finally it allows you to save money it's cost effective so you only pay for four cents per gigabyte of data transferred in a blank EFS itself no minimum commitments no upfront fees so just for example if you wanted to transfer a hundred gigabytes of data into EFS that would cost you $4 using data set so the service infrastructure is fully managed it scales automatically the one piece that you're responsible for is that is the agents but we'll show you some tips and tricks on how to optimize to streamline that in just a second but those agents again are automatically updated and patched ok so with that I'm gonna hand it over to Darryl who's gonna walk through how to piece these things together great thanks Joe some of you may be wondering why we're talking about AWS data sync in an amazon EFS ia webinar well as Joe mentioned AWS Data Sync is a great way to quickly as and securely ingest or transfer data from on-prem to AWS but soon you'll be able to do these transfers to and from in cloud resources this will include transferring files from an EFS standard file system to an EFS and frequent access file system that has lifecycle management enabled so we know and understand that there is a need to transfer files data to and from different storage platforms and we also know that transferring large amounts of data is difficult that's why we built a AWS data sync but we know and have heard from you that you want to use AWS data setting to transfer to and from more storage platforms specifically EFS - EFS in cloud NFS running on ec2 - EFS objects in s3 - EFS and objects in s3 - in cloud NFS on ec2 so there are a number of reasons why you want to do this it could be for disaster recovery purposes or loading data from an object store to a file system for data analytics because most of these applications require file system semantics to this data your application may be distributed across multiple regions and you want your file data to be eventually consistent across all these regions or you could just be migrating data from one file system to another to leverage this new functionality you'll be able to develop deploy an AWS Data Sync agent as an ec2 instance using a specific Amazon machine image or am I this will open up new source locations like in cloud NFS on ec2 or EFS or even s3 keep in mind that with AWS Data Sync a source and destination location could be in different AWS regions or they could be in the same region but not all source and destination combinations are supported one use case for this functionality is to use AWS data sync to quickly and securely transfer file data from an EFS standard storage class file system to a new EFS file system that supports the infrequent access storage class and lifecycle management so this architecture could look something like this first you have your source region and within that source region you have your source Amazon EFS file system in the destination region you have your destination EFS filesystem and remember the source and destination file systems could be in the same region in the source region you launch an ec2 instance using a specific ami that runs the Data Sync agent then you create and configure data sync resources using the data sync service in the destination region this will allow you to transfer file data from the source EFS filesystem to the decimation EFS filesystem to create and configure the data sync resources in the destination region you identify the data singh agent running in the source region you identify the source location which is the source EFS filesystem you identify the destination location which is the destination file system then you create a task to transfer your files using these data sync resources to help you get started using AWS data sync in cloud transfers we've created a quick start and scheduler this is an easy to launch AWS CloudFormation template that creates a stack with all the required resources including the AWS data sync agent ec2 instance and the optional scheduling mechanism used to to schedule the transfer of this data before you launch the AWS CloudFormation stack you need to have the source and destination file systems already created the first version of this quick start and scheduler supports transferring from an in cloud NFS source either NFS on ec2 or EFS to an EFS filesystem there is no additional cost to use the Quick Start and scheduler but you're still responsible for any compute storage or data transfer charges that it creates to give you a glimpse of what the QuickStart looks like let's take a look at a diagram here's a diagram of the in the environment that it creates you launch the AWS CloudFormation stack in this source region the source and destination regions could be in the same region but if you're setting up cross region replication your files of your filesystem you need to launch the stack in this source region the source and destination file systems must already exist but the cloud formation template creates the rest of the environment so let's go ahead and take a look at this in action so I'm going to hop over to the AWS management console and we see here that we don't have any cloud formation stacks created we also see that within Data Sync if I do a refresh we don't have any data sync resources created here either but I do have two file systems I have a file system that does not support the infrequent access storage class so I don't have the ability to enable lifecycle management and I also have a second file system that does support the infrequent access storage class and I have a life cycle management policy enabled for this file system so what I want to do and you can see the size of the file systems I'm approximately a hundred and sixty-seven gigabytes of data that I want to transfer from my EFS standard storage class file system to my EFS infrequent access storage class file system that I have a life cycle management policy enabled for so let's go ahead and set up and use the ws quick start and scheduler CloudFormation template to create a task to transfer this data from one file system to another so from the cloud formation management console we click on create stack and I actually browse out to where I have this stack this template created so it's it's just local on my machine I'll go ahead and open this up and click on the next step so from here actually have also a parameter file created that has some of these parameters already set up so though I use this when I oughta mate some of my the creation of the stack so I'm gonna go ahead and flip over to that so I can get some of these parameters so the first thing I want to do is just go ahead and and create a name of the stack so I'm gonna hop back and forth I'm going to enter the name of the stack here next I want to assign the ec2 key pair to the AWS data sync ec2 agent so again this is an ec2 instance that is running the Data Sync agent so there's a specific ami that's going to be launched for this I'll go ahead and select my ec2 key pair that I want to use I select the instance type so we recommend starting with the c5 to extra-large there are other instance types that have similar network performance characteristics and and attributes but for this example I'll start with the c5 to extra-large then the source subnet ID so again this is the subnet ID that the AWS Data Sync agent is going to be launched in so this subnet ID will need to have access to the source file system so in this example I'm just going to go ahead and select my friendly name sub subnet and I'm also going to select a security group that again also has access to the source file system so again I'm going to select my friendly name security group now the source NFS file system needs to be identified here so because we we are creating a look and NFS location for the source we need to include the DNS name of the file system so what I want to do is is go back to my EFS console I'll select the DNS name of the source location I'm gonna paste that here now if there's a specific no sub directory that I wanted to only copy that data over to the destination file system I could I could enter that in here I'm gonna go ahead and transfer the rotor everything in this file system over next I need to identify the destination location of this file system or sorry the destination region so what we're going to be doing is I'm going to be transferring within the same region so I'm going to select yes a US East one here as well next is the destination file system so here I want to go ahead and select the file system ID of the destination file system so we'll go ahead and copy that and paste it into here next the subnet ID so again this is a subnet that has access to the destination EFS file system so I'm already have this information in my parameter file so here's the destination subnet ID I'm gonna go and grab this and paste it into into my cloud formation parameters and a security group ID as well again this security group ID needs to have access to the destination EFS file system I also have that stored here as well if I wanted to copy or transfer this data to a specific directory within the destination EFS file system I could go ahead and identify this here but I'm just going to go ahead and transfer from root to root from source to destination I could also set up a a schedule of when this task should run maybe it's a on a regular basis maybe every 30 minutes you want it to sync these two file systems or maybe if it's a one-time so if it's going to be a one-time what I I recommend is go ahead and set it in a date that is far in the past so you can actually set this to January the 1st 1970 which what I did here so the schedule task will never run so what I'd have to actually manually start the task in order to for the task to run if I change this and wanted to run every 30 minutes I could go ahead and do this this is using a standard cron expression I'll go ahead and click on next review any of the stack options or Advanced Options don't have to make any changes here click on next again do a quick review of everything that I've entered in as my parameters I'll go and click accept that I am going to create some IM resources and click create stack so it'll take about three minutes for this stack to be created so let's actually go back and take a look at what's being created as a part of this stack so as you see here in the diagram and I'll move my cursor the AWS CloudFormation stack is being created in the source location so this is where the source file system resides it is right now creating an ec2 instance this ec2 instance is based on an ami that is running the data cicada I identified the security group and subnet ID where this agent is going to reside and both the subnet ID and security group needs access to this EFS file system as a part of the stack it's also creating an SSM document and SSM maintenance window these are the scheduling mechanisms that it uses to actually schedule this on a regular basis once this environment is set up and that agent is running it will actually create the data sync resources in the destination region so it's going to set up the agent the location the source location the destination location and create the task for you based on that's source directory and the destination directory so all of that will be created as a part of this so after about three minutes you'll be able to see the you have the CloudFormation stack completed you have an ec2 instance running and you have all of these resources created within the destination region so let's hop back to the management console and see where we are with the creation of the stack so we're getting very close we're about two minutes we're about about two minutes into it so far so if we take a look at the data sink resources in the destination region again the destination source region in this example are going to be the same but we see that we don't have any resources created yet because it hasn't gone to that part of the cloud formation stack very soon though you'll be able to start seeing some of these resources being created also it will create the ec2 instance this is going to be the ec2 instance that's running the data sake agent and again just very soon you'll be able to see an agent being launched here and running within the destination region so if we go back and we do a quick refresh we'll see how close we are so the agent fleet has been created so very soon we'll be able to see an ec2 instance being launched here then within a few minutes we'll be able to see the entire really within the next few seconds we'll be able to see the entire stack being created so right now it's creating the task execution task which is the SSM maintenance window then within a few more seconds it'll be it'll be completed now that the task is actually or the entire stack is created we should start to see the instance being launched there it is we see the interest the instance is initializing it's in in running state so within the next few minutes this instance will be running we could take a look at our data sink resource so again this is going to be maybe another 30 seconds maybe 45 seconds we'll start to see some of these resources being created if we go back to the cloud formation stack I created some of the outputs which is very what I think useful for users as you're as you want to manage the stack so first there's an SSM command that you can run to actually disable the task execution schedule so if you need to disable that schedule for any reason you can go ahead and click onto this copy this into command show window and go ahead and execute this and this will disable the maintenance window if you want to enable the maintenance window back you can go ahead and run this other command if you want to run the command just on demand there's also an SSM command here that you can execute that'll actually start that transfer you can either do it here using an SSM command or you can go into the data sync service at the destination and region and go ahead and just start the task yourself you also have a command - it actually updates the schedule if you need it to change the the cron expression to change that scheduled command this is useful - is because this is a command that we can run within show window and what this does is this will actually run an SSM SSM command against that instance and it will actually take a look and return the log file that's created when it's creating all of those data sync resources at the destination so we see that it created the agent it created the source location and the destination location so all of these resources have been created now so if we go back to the console if we go ahead and refresh the data sync in the destination region we'll see that we'll have a task created we have the two locations we have our source location and our destination location and we have that agent is online so everything is ready for us to actually kick off that kick off that task so let's go ahead and do that now so we can go ahead and select that task and then we can start this task so right now that task is running we can take a look at the history of this task and see how it's actually performing so you'll notice that the status of the task is going to change from launching it's actually starting to transfer some of that data and we'll see how fast were able to de transport data from this EFS file system the standard storage class ZFS file system to a storage class file system that's very EFS file system that supports the infrequent access towards class so now it's in the preparing mode and here within the next few seconds we'll start to see we'll see some some megabytes per second throughput here displayed in the history of the task while it's doing that let's go ahead and go to the management console I'll show you some of the resources that it created the stack created is a part of that so this is the mechanism that it actually schedules the execution of that if you set up a cron expression within the templates so this is the expression that I used I could go and actually change this and to have a different schedule or I could disable this the schedule event altogether and I can rename it here as well so you can manage the scheduling aspect of it using the SSM aeneas windows or you can manually launch the task using the data sync service in the in the destination region so let's go back to the data sync and see how we're going so right now we're already we've already transferred seven percent of the data we're at around two hundred and ten megabytes per second throughput so we're transferring a lot of data from this one filesystem to another so it'll take I think I tested this to take about 12 maybe 15 minutes to transfer the hundred and sixty seven gigabytes of data from this one file system to another file system at the Eno verify on both file systems make sure that I got all of the data transferred over then the task will stop at that point we can go ahead and turn you know delete all of these resources so keep in mind though because not all the resources were created as a part of natively as a part of the cloud formation stack it's recommended that you use this method to do to delete the resources so at the very end I actually created an SMS command that creates the delete commands to delete these resources so if I actually go ahead and copy this into a shell and run this you'll see the delete commands that you want to run so to actually delete all these resources in the right order go ahead and copy this paste in another command show and execute so first it will delete the time ask they'll then delete the locations of source and destination locations then create deletes or it will delete the agent then it will delete the cloud formation stack so by the end you'll have none of the AWS data sync resources created or running and the only thing you'll have is your source and destination file systems but now with all the data from the source in the destination file system and that's it so pretty easy to get up and running we have this and this quick start and scheduler ready the user guide has all the documentation to to walk you through this step-by-step and give you some pretty in-depth details on how to use it in all the different settings and the parameters that you need to use when you when you launch the stack so let's walk through a quick TCO example of the infrequent access so you know before we said you know EFS was about 70% more cost effective than a do-it-yourself setup so if we update this example to include EFS ia and a cost optimized doing yourself setup with multiple storage tiers you can see that EFS with ia is closer to 90 percent more cost-effective than building it yourself and don't forget these are just your hard costs you know soft costs like managing the soft or patching your infrastructure aren't included in these TCO in this TCO analysis let's take it one step further so here's a TCO example the a dealer AWS data sync in cloud transfer quick start and scheduler that I just ran so say we want to use this to migrate data from an EFS standard storage class to an EFS IA so again in this example five hundred gigabytes of data in this store the standard storage class would cost $150 per month if you wanted to take advantage of the FSIA and get your monthly storage cost down to 52 dollars per month because 40 or 400 gigabytes of data is actually in frequently accessed you would use the AWS data sync in cloud transfer quick start and scheduler to transfer all 500 gigabytes of data to a file system that supports EFS IA with lifecycle management enabled this one time this one time transfer would cost about $2 sorry 20 dollars and 20 cents once you're done with the transfer you can shut down that cloud formation stack all those transfer all the resources created as a part of that transfer will be deleted and now your EFS cost would be you know 52 dollars per month once your data has been transitioned from the standard storage class over to the infrequent access storage class that concludes the webinar today what I'd like to do is open it up for some Q&A