AWS Storage Gateway | File Gateway Flashcards
Is AWS Storage Gateway HIPAA eligible?
File Gateway
AWS Storage Gateway | Storage
Yes. AWS Storage Gateway is HIPAA eligible. If you have an executed Business Associate Agreement (BAA) with AWS, you can use Storage Gateway to store, backup and archive protected health information (PHI) on scalable, cost-effective, and secure AWS storage services, including Amazon S3, Amazon Glacier and Amazon EBS, which are also HIPAA eligible.
Information on HIPAA eligible services on AWS can be found at our HIPAA Compliance page, and you can enter into a BAA with AWS here. HIPAA eligibility for Storage Gateway applies to all gateway types (File, Volume and Tape).
What is file gateway?
File Gateway
AWS Storage Gateway | Storage
File gateway provides a virtual on-premises file server, which enables you to store and retrieve Amazon S3 objects through standard file storage protocols.
What can I do with file gateway?
File Gateway
AWS Storage Gateway | Storage
The use cases for file gateway include: (a) ingesting file-based data into S3 for object workloads, (b) “cloud-bursting”, where you can move data to AWS, run a workload, and access results within your on-premises application, (c) migrating file to objects in S3, (d) cost-effective storage for backup and archive, (f) disaster recovery, and (g) tiering on-premises file storage to S3.
What are the benefits of using file gateway to store data in S3?
File Gateway
AWS Storage Gateway | Storage
File gateway enables your existing file-based applications, devices, and workflows to use cloud storage without modification. File gateway securely and durably stores both file contents and metadata as objects in your Amazon S3 buckets using standard file protocols.
What protocols are supported? Can I use Microsoft Windows?
File Gateway
AWS Storage Gateway | Storage
File gateway supports clients connecting to the gateway using NFS v3 and v4.1. Microsoft Windows clients that support NFS v3 can connect to file gateway.
How do I create and configure a file share?
File Gateway
AWS Storage Gateway | Storage
You can create a file share using the AWS Management Console or service API, and associate it with a new or existing S3 bucket. You can configure your file share with administative controls such as limiting acces to specific NFS clients or networks, read-only or read-write, or enabling user permisssion squashing.
How does file gateway access my S3 bucket?
File Gateway
AWS Storage Gateway | Storage
File gateway uses an AWS Identity and Access Management (IAM) role to access your S3 bucket. You can set this up yourself, or have it automatically setup by the AWS Storage Gateway Management Console. For automatic setup, AWS Storage Gateway will create a new IAM role in your account and associate it with an IAM Access Policy to access your S3 bucket. The IAM role and IAM access policy are created in your account and you can fully manage them yourself.
How does my application access my file share?
File Gateway
AWS Storage Gateway | Storage
To use the file share, you mount it from your application using standard UNIX or Windows commands. For convenience, example command lines are shown in the management console
What is the relationship between files and objects?
File Gateway
AWS Storage Gateway | Storage
Files are stored as objects in your S3 buckets and you can configure the initial storage class for objects that file gateway creates. There is a one-to-one relationship between files and objects, and you can configure the initial storage class for objects that file gateway creates.
The object key is derived from the file path within the file system. For example, if you have a gateway with hostname file.amazon.com and have mapped my-bucket, then file gateway will expose a mount point called file.amazon.com:/export/my-bucket. If you then mount this locally on /mnt/my-bucket and create a file named file.html in a directory /mnt/my-bucket/dir this file will be stored as an object in the bucket my-bucket with a key of dir/file.html.
What file system operations are supported by file gateway?
File Gateway
AWS Storage Gateway | Storage
Your NFS client can create, read, update, and delete, files and directories. Files are stored as individual objects in S3. Directories are managed as folder objects in S3, using the same syntax as the S3 console.
Symbolic links and hard links are not supported. Attempting to create a link will result in an NFS error. Creating sparse files will result in a non-sparse zero-filled object in S3.
Rename operations will appear atomic to NFS clients, but S3 does not support renaming of objects. When you rename a file or directory the gateway performs copy-put requests to create a copy of the objects in S3 under the new keys and then deletes the originals. This avoids having to re-send large files over the network. Renaming directories containing a large number of files is not instantaneous and will result in 2 copies of your data being stored in S3 until the rename operation completes.
What file system metadata can my NFS client access?
File Gateway
AWS Storage Gateway | Storage
Your NFS client can access file system metadata including ownership, permissions, and timestamps, for files and directories. Ownership, permissions, and timestamps, are durably stored in S3 in the user-metadata of the object associated with the file. You can configure default ownership and permissions for objects which were stored in the S3 bucket directly, not by file gateway.
How do I set the Content-Type for files uploaded to S3?
File Gateway
AWS Storage Gateway | Storage
For each file share, you can enable guessing of MIME types for uploaded objects upon creation or enable the feature later. If enabled, file gateway will use the filename extension to determine the MIME type for the file and set the S3 objects Content-Type accordingly. This is beneficial if you are using file gateway to manage objects in S3 which you access directly via URL or distribute through Amazon CloudFront.
Can I use multiple NFS clients with a single file gateway?
File Gateway
AWS Storage Gateway | Storage
You can have multiple NFS clients accessing a single file gateway. However, as with any NFS server, concurrent modification from multiple NFS clients can lead to unpredictable behavior. Application level coordination is required to do this in a safe way.
Can I have multiple writers to my S3 bucket?
File Gateway
AWS Storage Gateway | Storage
No. We recommend a single writer to objects in your S3 bucket. If you directly overwrite or update an object previously written by file gateway, it results in undefined behavior when the object is accessed through the file share. Concurrent modification of the same object (e.g. via the S3 API and the file gateway) can lead to unpredictable results and we recommend against this configuration.
Can I have two gateways writing independent data to the same bucket?
File Gateway
AWS Storage Gateway | Storage
We do not recommend configuring multiple writers to a single bucket because it can lead to unpredictable results. You could enforce unique object names or prefixes through your application workflow. File gateway doesn’t monitor or report on conflicts in such a setup.