aws-sdk-core 2.0.45 → 2.0.46

data/apis/elasticfilesystem/2015-02-01/docs-2.json

@@ -0,0 +1,414 @@
+{
+  "version": "2.0",
+  "operations": {
+    "CreateFileSystem": "<p> Creates a new, empty file system. The operation requires a creation token in the request that Amazon EFS uses to ensure idempotent creation (calling the operation with same creation token has no effect). If a file system does not currently exist that is owned by the caller's AWS account with the specified creation token, this operation does the following: </p> <ul> <li>Creates a new, empty file system. The file system will have an Amazon EFS assigned ID, and an initial lifecycle state \"creating\". </li> <li> Returns with the description of the created file system. </li> </ul> <p>Otherwise, this operation returns a <code>FileSystemAlreadyExists</code> error with the ID of the existing file system.</p> <note>For basic use cases, you can use a randomly generated UUID for the creation token.</note> <p> The idempotent operation allows you to retry a <code>CreateFileSystem</code> call without risk of creating an extra file system. This can happen when an initial call fails in a way that leaves it uncertain whether or not a file system was actually created. An example might be that a transport level timeout occurred or your connection was reset. As long as you use the same creation token, if the initial call had succeeded in creating a file system, the client can learn of its existence from the <code>FileSystemAlreadyExists</code> error. </p> <note>The <code>CreateFileSystem</code> call returns while the file system's lifecycle state is still \"creating\". You can check the file system creation status by calling the <a>DescribeFileSystems</a> API, which among other things returns the file system state.</note> <p> After the file system is fully created, Amazon EFS sets its lifecycle state to \"available\", at which point you can create one or more mount targets for the file system (<a>CreateMountTarget</a>) in your VPC. You mount your Amazon EFS file system on an EC2 instances in your VPC via the mount target. For more information, see <a href=\"http://docs.aws.amazon.com/efs/latest/ug/how-it-works.html\">Amazon EFS: How it Works</a> </p> <p> This operation requires permission for the <code>elasticfilesystem:CreateFileSystem</code> action. </p>",
+    "CreateMountTarget": "<p>Creates a mount target for a file system. You can then mount the file system on EC2 instances via the mount target. </p> <p>You can create one mount target in each Availability Zone in your VPC. All EC2 instances in a VPC within a given Availability Zone share a single mount target for a given file system. If you have multiple subnets in an Availability Zone, you create a mount target in one of the subnets. EC2 instances do not need to be in the same subnet as the mount target in order to access their file system. For more information, see <a href=\"http://docs.aws.amazon.com/efs/latest/ug/how-it-works.html\">Amazon EFS: How it Works</a>. </p> <p>In the request, you also specify a file system ID for which you are creating the mount target and the file system's lifecycle state must be \"available\" (see <a>DescribeFileSystems</a>).</p> <p> In the request, you also provide a subnet ID, which serves several purposes:</p> <ul> <li>It determines the VPC in which Amazon EFS creates the mount target.</li> <li>It determines the Availability Zone in which Amazon EFS creates the mount target. </li> <li>It determines the IP address range from which Amazon EFS selects the IP address of the mount target if you don't specify an IP address in the request. </li> </ul> <p>After creating the mount target, Amazon EFS returns a response that includes, a <code>MountTargetId</code> and an <code>IpAddress</code>. You use this IP address when mounting the file system in an EC2 instance. You can also use the mount target's DNS name when mounting the file system. The EC2 instance on which you mount the file system via the mount target can resolve the mount target's DNS name to its IP address. For more information, see <a href=\"http://docs.aws.amazon.com/efs/latest/ug/how-it-works.html#how-it-works-implementation\">How it Works: Implementation Overview</a> </p> <p> Note that you can create mount targets for a file system in only one VPC, and there can be only one mount target per Availability Zone. That is, if the file system already has one or more mount targets created for it, the request to add another mount target must meet the following requirements: </p> <ul> <li> <p>The subnet specified in the request must belong to the same VPC as the subnets of the existing mount targets.</p> </li> <li>The subnet specified in the request must not be in the same Availability Zone as any of the subnets of the existing mount targets.</li> </ul> <p>If the request satisfies the requirements, Amazon EFS does the following:</p> <ul> <li>Creates a new mount target in the specified subnet. </li> <li>Also creates a new network interface in the subnet as follows: <ul> <li>If the request provides an <code>IpAddress</code>, Amazon EFS assigns that IP address to the network interface. Otherwise, Amazon EFS assigns a free address in the subnet (in the same way that the Amazon EC2 <code>CreateNetworkInterface</code> call does when a request does not specify a primary private IP address).</li> <li>If the request provides <code>SecurityGroups</code>, this network interface is associated with those security groups. Otherwise, it belongs to the default security group for the subnet's VPC.</li> <li>Assigns the description <code>\"Mount target <i>fsmt-id</i> for file system <i>fs-id</i>\"</code> where <code><i>fsmt-id</i></code> is the mount target ID, and <code><i>fs-id</i></code> is the <code>FileSystemId</code>.</li> <li>Sets the <code>requesterManaged</code> property of the network interface to \"true\", and the <code>requesterId</code> value to \"EFS\".</li> </ul> <p>Each Amazon EFS mount target has one corresponding requestor-managed EC2 network interface. After the network interface is created, Amazon EFS sets the <code>NetworkInterfaceId</code> field in the mount target's description to the network interface ID, and the <code>IpAddress</code> field to its address. If network interface creation fails, the entire <code>CreateMountTarget</code> operation fails.</p> </li> </ul> <note>The <code>CreateMountTarget</code> call returns only after creating the network interface, but while the mount target state is still \"creating\". You can check the mount target creation status by calling the <a>DescribeFileSystems</a> API, which among other things returns the mount target state.</note> <p>We recommend you create a mount target in each of the Availability Zones. There are cost considerations for using a file system in an Availability Zone through a mount target created in another Availability Zone. For more information, go to <a href=\"http://aws.amazon.com/efs/\">Amazon EFS</a> product detail page. In addition, by always using a mount target local to the instance's Availability Zone, you eliminate a partial failure scenario; if the Availablity Zone in which your mount target is created goes down, then you won't be able to access your file system through that mount target. </p> <p>This operation requires permission for the following action on the file system:</p> <ul> <li><code>elasticfilesystem:CreateMountTarget</code></li> </ul> <p>This operation also requires permission for the following Amazon EC2 actions:</p> <ul> <li><code>ec2:DescribeSubnets</code></li> <li><code>ec2:DescribeNetworkInterfaces</code></li> <li><code>ec2:CreateNetworkInterface</code></li> </ul>",
+    "CreateTags": "<p>Creates or overwrites tags associated with a file system. Each tag is a key-value pair. If a tag key specified in the request already exists on the file system, this operation overwrites its value with the value provided in the request. If you add the \"Name\" tag to your file system, Amazon EFS returns it in the response to the <a>DescribeFileSystems</a> API. </p> <p>This operation requires permission for the <code>elasticfilesystem:CreateTags</code> action.</p>",
+    "DeleteFileSystem": "<p> Deletes a file system, permanently severing access to its contents. Upon return, the file system no longer exists and you will not be able to access any contents of the deleted file system. </p> <p> You cannot delete a file system that is in use. That is, if the file system has any mount targets, you must first delete them. For more information, see <a>DescribeMountTargets</a> and <a>DeleteMountTarget</a>. </p> <note>The <code>DeleteFileSystem</code> call returns while the file system state is still \"deleting\". You can check the file system deletion status by calling the <a>DescribeFileSystems</a> API, which returns a list of file systems in your account. If you pass file system ID or creation token for the deleted file system, the <a>DescribeFileSystems</a> will return a 404 \"FileSystemNotFound\" error.</note> <p>This operation requires permission for the <code>elasticfilesystem:DeleteFileSystem</code> action.</p>",
+    "DeleteMountTarget": "<p>Deletes the specified mount target. </p> <p> This operation forcibly breaks any mounts of the file system via the mount target being deleted, which might disrupt instances or applications using those mounts. To avoid applications getting cut off abruptly, you might consider unmounting any mounts of the mount target, if feasible. The operation also deletes the associated network interface. Uncommitted writes may be lost, but breaking a mount target using this operation does not corrupt the file system itself. The file system you created remains. You can mount an EC2 instance in your VPC using another mount target. </p> <p> This operation requires permission for the following action on the file system: </p> <ul> <li><code>elasticfilesystem:DeleteMountTarget</code></li> </ul> <note>The <code>DeleteMountTarget</code> call returns while the mount target state is still \"deleting\". You can check the mount target deletion by calling the <a>DescribeMountTargets</a> API, which returns a list of mount target descriptions for the given file system. </note> <p>The operation also requires permission for the following Amazon EC2 action on the mount target's network interface:</p> <ul> <li><code>ec2:DeleteNetworkInterface</code></li> </ul>",
+    "DeleteTags": "<p>Deletes the specified tags from a file system. If the <code>DeleteTags</code> request includes a tag key that does not exist, Amazon EFS ignores it; it is not an error. For more information about tags and related restrictions, go to <a href=\"http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html\">Tag Restrictions</a> in the <i>AWS Billing and Cost Management User Guide</i>.</p> <p>This operation requires permission for the <code>elasticfilesystem:DeleteTags</code> action.</p>",
+    "DescribeFileSystems": "<p>Returns the description of a specific Amazon EFS file system if either the file system <code>CreationToken</code> or the <code>FileSystemId</code> is provided; otherwise, returns descriptions of all file systems owned by the caller's AWS account in the AWS region of the endpoint that you're calling.</p> <p> When retrieving all file system descriptions, you can optionally specify the <code>MaxItems</code> parameter to limit the number of descriptions in a response. If more file system descriptions remain, Amazon EFS returns a <code>NextMarker</code>, an opaque token, in the response. In this case, you should send a subsequent request with the <code>Marker</code> request parameter set to the value of <code>NextMarker</code>. </p> <p> So to retrieve a list of your file system descriptions, the expected usage of this API is an iterative process of first calling <code>DescribeFileSystems</code> without the <code>Marker</code> and then continuing to call it with the <code>Marker</code> parameter set to the value of the <code>NextMarker</code> from the previous response until the response has no <code>NextMarker</code>. </p> <p> Note that the implementation may return fewer than <code>MaxItems</code> file system descriptions while still including a <code>NextMarker</code> value. </p> <p> The order of file systems returned in the response of one <code>DescribeFileSystems</code> call, and the order of file systems returned across the responses of a multi-call iteration, is unspecified. </p> <p> This operation requires permission for the <code>elasticfilesystem:DescribeFileSystems</code> action. </p>",
+    "DescribeMountTargetSecurityGroups": "<p>Returns the security groups currently in effect for a mount target. This operation requires that the network interface of the mount target has been created and the life cycle state of the mount target is not \"deleted\".</p> <p>This operation requires permissions for the following actions:</p> <ul> <li> <code>elasticfilesystem:DescribeMountTargetSecurityGroups</code> action on the mount target's file system. </li> <li> <code>ec2:DescribeNetworkInterfaceAttribute</code> action on the mount target's network interface. </li> </ul>",
+    "DescribeMountTargets": "<p>Returns the descriptions of the current mount targets for a file system. The order of mount targets returned in the response is unspecified.</p> <p> This operation requires permission for the <code>elasticfilesystem:DescribeMountTargets</code> action on the file system <code>FileSystemId</code>. </p>",
+    "DescribeTags": "<p>Returns the tags associated with a file system. The order of tags returned in the response of one <code>DescribeTags</code> call, and the order of tags returned across the responses of a multi-call iteration (when using pagination), is unspecified. </p> <p> This operation requires permission for the <code>elasticfilesystem:DescribeTags</code> action. </p>",
+    "ModifyMountTargetSecurityGroups": "<p>Modifies the set of security groups in effect for a mount target.</p> <p>When you create a mount target, Amazon EFS also creates a new network interface (see <a>CreateMountTarget</a>). This operation replaces the security groups in effect for the network interface associated with a mount target, with the <code>SecurityGroups</code> provided in the request. This operation requires that the network interface of the mount target has been created and the life cycle state of the mount target is not \"deleted\". </p> <p>The operation requires permissions for the following actions:</p> <ul> <li> <code>elasticfilesystem:ModifyMountTargetSecurityGroups</code> action on the mount target's file system. </li> <li> <code>ec2:ModifyNetworkInterfaceAttribute</code> action on the mount target's network interface. </li> </ul>"
+  },
+  "service": "<fullname>Amazon Elastic File System</fullname>",
+  "shapes": {
+    "AwsAccountId": {
+      "base": null,
+      "refs": {
+        "FileSystemDescription$OwnerId": "<p>The AWS account that created the file system. If the file system was created by an IAM user, the parent account to which the user belongs is the owner.</p>",
+        "MountTargetDescription$OwnerId": "<p>The AWS account ID that owns the resource.</p>"
+      }
+    },
+    "BadRequest": {
+      "base": "<p>Returned if the request is malformed or contains an error such as an invalid parameter value or a missing required parameter.</p>",
+      "refs": {
+      }
+    },
+    "CreateFileSystemRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "CreateMountTargetRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "CreateTagsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "CreationToken": {
+      "base": null,
+      "refs": {
+        "CreateFileSystemRequest$CreationToken": "<p>String of up to 64 ASCII characters. Amazon EFS uses this to ensure idempotent creation.</p>",
+        "DescribeFileSystemsRequest$CreationToken": "<p> Optional string. Restricts the list to the file system with this creation token (you specify a creation token at the time of creating an Amazon EFS file system). </p>",
+        "FileSystemDescription$CreationToken": "<p>Opaque string specified in the request. </p>"
+      }
+    },
+    "DeleteFileSystemRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DeleteMountTargetRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DeleteTagsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DependencyTimeout": {
+      "base": "<p>The service timed out trying to fulfill the request, and the client should try the call again.</p>",
+      "refs": {
+      }
+    },
+    "DescribeFileSystemsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeFileSystemsResponse": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeMountTargetSecurityGroupsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeMountTargetSecurityGroupsResponse": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeMountTargetsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeMountTargetsResponse": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeTagsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "DescribeTagsResponse": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "ErrorCode": {
+      "base": null,
+      "refs": {
+        "BadRequest$ErrorCode": null,
+        "DependencyTimeout$ErrorCode": null,
+        "FileSystemAlreadyExists$ErrorCode": null,
+        "FileSystemInUse$ErrorCode": null,
+        "FileSystemLimitExceeded$ErrorCode": null,
+        "FileSystemNotFound$ErrorCode": null,
+        "IncorrectFileSystemLifeCycleState$ErrorCode": null,
+        "IncorrectMountTargetState$ErrorCode": null,
+        "InternalServerError$ErrorCode": null,
+        "IpAddressInUse$ErrorCode": null,
+        "MountTargetConflict$ErrorCode": null,
+        "MountTargetNotFound$ErrorCode": null,
+        "NetworkInterfaceLimitExceeded$ErrorCode": null,
+        "NoFreeAddressesInSubnet$ErrorCode": null,
+        "SecurityGroupLimitExceeded$ErrorCode": null,
+        "SecurityGroupNotFound$ErrorCode": null,
+        "SubnetNotFound$ErrorCode": null,
+        "UnsupportedAvailabilityZone$ErrorCode": null
+      }
+    },
+    "ErrorMessage": {
+      "base": null,
+      "refs": {
+        "BadRequest$Message": null,
+        "DependencyTimeout$Message": null,
+        "FileSystemAlreadyExists$Message": null,
+        "FileSystemInUse$Message": null,
+        "FileSystemLimitExceeded$Message": null,
+        "FileSystemNotFound$Message": null,
+        "IncorrectFileSystemLifeCycleState$Message": null,
+        "IncorrectMountTargetState$Message": null,
+        "InternalServerError$Message": null,
+        "IpAddressInUse$Message": null,
+        "MountTargetConflict$Message": null,
+        "MountTargetNotFound$Message": null,
+        "NetworkInterfaceLimitExceeded$Message": null,
+        "NoFreeAddressesInSubnet$Message": null,
+        "SecurityGroupLimitExceeded$Message": null,
+        "SecurityGroupNotFound$Message": null,
+        "SubnetNotFound$Message": null,
+        "UnsupportedAvailabilityZone$Message": null
+      }
+    },
+    "FileSystemAlreadyExists": {
+      "base": "<p>Returned if the file system you are trying to create already exists, with the creation token you provided.</p>",
+      "refs": {
+      }
+    },
+    "FileSystemDescription": {
+      "base": "<p>This object provides description of a file system.</p>",
+      "refs": {
+        "FileSystemDescriptions$member": null
+      }
+    },
+    "FileSystemDescriptions": {
+      "base": null,
+      "refs": {
+        "DescribeFileSystemsResponse$FileSystems": "<p>An array of file system descriptions.</p>"
+      }
+    },
+    "FileSystemId": {
+      "base": null,
+      "refs": {
+        "CreateMountTargetRequest$FileSystemId": "<p>The ID of the file system for which to create the mount target.</p>",
+        "CreateTagsRequest$FileSystemId": "<p>String. The ID of the file system whose tags you want to modify. This operation modifies only the tags and not the file system.</p>",
+        "DeleteFileSystemRequest$FileSystemId": "<p>The ID of the file system you want to delete.</p>",
+        "DeleteTagsRequest$FileSystemId": "<p>String. The ID of the file system whose tags you want to delete.</p>",
+        "DescribeFileSystemsRequest$FileSystemId": "<p>Optional string. File system ID whose description you want to retrieve. </p>",
+        "DescribeMountTargetsRequest$FileSystemId": "<p>String. The ID of the file system whose mount targets you want to list.</p>",
+        "DescribeTagsRequest$FileSystemId": "<p>The ID of the file system whose tag set you want to retrieve.</p>",
+        "FileSystemAlreadyExists$FileSystemId": null,
+        "FileSystemDescription$FileSystemId": "<p>The file system ID assigned by Amazon EFS.</p>",
+        "MountTargetDescription$FileSystemId": "<p>The ID of the file system for which the mount target is intended.</p>"
+      }
+    },
+    "FileSystemInUse": {
+      "base": "<p>Returned if a file system has mount targets. </p>",
+      "refs": {
+      }
+    },
+    "FileSystemLimitExceeded": {
+      "base": "<p>Returned if the AWS account has already created maximum number of file systems allowed per account. </p>",
+      "refs": {
+      }
+    },
+    "FileSystemNotFound": {
+      "base": "<p>Returned if the specified <code>FileSystemId</code> does not exist in the requester's AWS account.</p>",
+      "refs": {
+      }
+    },
+    "FileSystemSize": {
+      "base": "<p>This object provides the latest known metered size, in bytes, of data stored in the file system, in its <code>Value</code> field, and the time at which that size was determined in its <code>Timestamp</code> field. Note that the value does not represent the size of a consistent snapshot of the file system, but it is eventually consistent when there are no writes to the file system. That is, the value will represent the actual size only if the file system is not modified for a period longer than a couple of hours. Otherwise, the value is not necessarily the exact size the file system was at any instant in time.</p>",
+      "refs": {
+        "FileSystemDescription$SizeInBytes": "<p> This object provides the latest known metered size of data stored in the file system, in bytes, in its <code>Value</code> field, and the time at which that size was determined in its <code>Timestamp</code> field. The <code>Timestamp</code> value is the integer number of seconds since 1970-01-01T00:00:00Z. Note that the value does not represent the size of a consistent snapshot of the file system, but it is eventually consistent when there are no writes to the file system. That is, the value will represent actual size only if the file system is not modified for a period longer than a couple of hours. Otherwise, the value is not the exact size the file system was at any instant in time. </p>"
+      }
+    },
+    "FileSystemSizeValue": {
+      "base": null,
+      "refs": {
+        "FileSystemSize$Value": "<p>The latest known metered size, in bytes, of data stored in the file system.</p>"
+      }
+    },
+    "IncorrectFileSystemLifeCycleState": {
+      "base": "<p>Returned if the file system's life cycle state is not \"created\".</p>",
+      "refs": {
+      }
+    },
+    "IncorrectMountTargetState": {
+      "base": "<p>Returned if the mount target is not in the correct state for the operation.</p>",
+      "refs": {
+      }
+    },
+    "InternalServerError": {
+      "base": "<p>Returned if an error occurred on the server side.</p>",
+      "refs": {
+      }
+    },
+    "IpAddress": {
+      "base": null,
+      "refs": {
+        "CreateMountTargetRequest$IpAddress": "<p>A valid IPv4 address within the address range of the specified subnet.</p>",
+        "MountTargetDescription$IpAddress": "<p>The address at which the file system may be mounted via the mount target.</p>"
+      }
+    },
+    "IpAddressInUse": {
+      "base": "<p>Returned if the request specified an <code>IpAddress</code> that is already in use in the subnet.</p>",
+      "refs": {
+      }
+    },
+    "LifeCycleState": {
+      "base": null,
+      "refs": {
+        "FileSystemDescription$LifeCycleState": "<p>A predefined string value that indicates the lifecycle phase of the file system. </p>",
+        "MountTargetDescription$LifeCycleState": "<p>The lifecycle state the mount target is in.</p>"
+      }
+    },
+    "Marker": {
+      "base": null,
+      "refs": {
+        "DescribeFileSystemsRequest$Marker": "<p> Optional string. Opaque pagination token returned from a previous <code>DescribeFileSystems</code> operation. If present, specifies to continue the list from where the returning call had left off. </p>",
+        "DescribeFileSystemsResponse$Marker": "<p>A string, present if provided by caller in the request.</p>",
+        "DescribeFileSystemsResponse$NextMarker": "<p>A string, present if there are more file systems than returned in the response. You can use the <code>NextMarker</code> in the subsequent request to fetch the descriptions.</p>",
+        "DescribeMountTargetsRequest$Marker": "<p>Optional. String. Opaque pagination token returned from a previous <code>DescribeMountTargets</code> operation. If present, it specifies to continue the list from where the previous returning call left off.</p>",
+        "DescribeMountTargetsResponse$Marker": "<p>If the request included the <code>Marker</code>, the response returns that value in this field.</p>",
+        "DescribeMountTargetsResponse$NextMarker": "<p>If a value is present, there are more mount targets to return. In a subsequent request, you can provide <code>Marker</code> in your request with this value to retrieve the next set of mount targets.</p>",
+        "DescribeTagsRequest$Marker": "<p>Optional. String. Opaque pagination token returned from a previous <code>DescribeTags</code> operation. If present, it specifies to continue the list from where the previous call left off.</p>",
+        "DescribeTagsResponse$Marker": "<p>If the request included a <code>Marker</code>, the response returns that value in this field.</p>",
+        "DescribeTagsResponse$NextMarker": "<p>If a value is present, there are more tags to return. In a subsequent request, you can provide the value of <code>NextMarker</code> as the value of the <code>Marker</code> parameter in your next request to retrieve the next set of tags.</p>"
+      }
+    },
+    "MaxItems": {
+      "base": null,
+      "refs": {
+        "DescribeFileSystemsRequest$MaxItems": "<p>Optional integer. Specifies the maximum number of file systems to return in the response. This parameter value must be greater than 0. The number of items Amazon EFS returns will be the minimum of the <code>MaxItems</code> parameter specified in the request and the service's internal maximum number of items per page. </p>",
+        "DescribeMountTargetsRequest$MaxItems": "<p>Optional. Maximum number of mount targets to return in the response. It must be an integer with a value greater than zero.</p>",
+        "DescribeTagsRequest$MaxItems": "<p>Optional. Maximum number of file system tags to return in the response. It must be an integer with a value greater than zero.</p>"
+      }
+    },
+    "ModifyMountTargetSecurityGroupsRequest": {
+      "base": null,
+      "refs": {
+      }
+    },
+    "MountTargetConflict": {
+      "base": "<p>Returned if the mount target would violate one of the specified restrictions based on the file system's existing mount targets.</p>",
+      "refs": {
+      }
+    },
+    "MountTargetCount": {
+      "base": null,
+      "refs": {
+        "FileSystemDescription$NumberOfMountTargets": "<p>The current number of mount targets (see <a>CreateMountTarget</a>) the file system has.</p>"
+      }
+    },
+    "MountTargetDescription": {
+      "base": "<p>This object provides description of a mount target.</p>",
+      "refs": {
+        "MountTargetDescriptions$member": null
+      }
+    },
+    "MountTargetDescriptions": {
+      "base": null,
+      "refs": {
+        "DescribeMountTargetsResponse$MountTargets": "<p>Returns the file system's mount targets as an array of <code>MountTargetDescription</code> objects.</p>"
+      }
+    },
+    "MountTargetId": {
+      "base": null,
+      "refs": {
+        "DeleteMountTargetRequest$MountTargetId": "<p>String. The ID of the mount target to delete.</p>",
+        "DescribeMountTargetSecurityGroupsRequest$MountTargetId": "<p>The ID of the mount target whose security groups you want to retrieve.</p>",
+        "ModifyMountTargetSecurityGroupsRequest$MountTargetId": "<p>The ID of the mount target whose security groups you want to modify.</p>",
+        "MountTargetDescription$MountTargetId": "<p>The system-assigned mount target ID. </p>"
+      }
+    },
+    "MountTargetNotFound": {
+      "base": "<p>Returned if there is no mount target with the specified ID is found in the caller's account.</p>",
+      "refs": {
+      }
+    },
+    "NetworkInterfaceId": {
+      "base": null,
+      "refs": {
+        "MountTargetDescription$NetworkInterfaceId": "<p>The ID of the network interface that Amazon EFS created when it created the mount target.</p>"
+      }
+    },
+    "NetworkInterfaceLimitExceeded": {
+      "base": "<p> The calling account has reached the ENI limit for the specific AWS region. Client should try to delete some ENIs or get its account limit raised. For more information, go to <a href=\"http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Appendix_Limits.html\">Amazon VPC Limits</a> in the Amazon Virtual Private Cloud User Guide (see the Network interfaces per VPC entry in the table). </p>",
+      "refs": {
+      }
+    },
+    "NoFreeAddressesInSubnet": {
+      "base": "<p>Returned if <code>IpAddress</code> was not specified in the request and there are no free IP addresses in the subnet.</p>",
+      "refs": {
+      }
+    },
+    "SecurityGroup": {
+      "base": null,
+      "refs": {
+        "SecurityGroups$member": null
+      }
+    },
+    "SecurityGroupLimitExceeded": {
+      "base": "<p>Returned if the size of <code>SecurityGroups</code> specified in the request is greater than five.</p>",
+      "refs": {
+      }
+    },
+    "SecurityGroupNotFound": {
+      "base": "<p>Returned if one of the specified security groups does not exist in the subnet's VPC.</p>",
+      "refs": {
+      }
+    },
+    "SecurityGroups": {
+      "base": null,
+      "refs": {
+        "CreateMountTargetRequest$SecurityGroups": "<p> Up to 5 VPC security group IDs, of the form \"sg-xxxxxxxx\". These must be for the same VPC as subnet specified. </p>",
+        "DescribeMountTargetSecurityGroupsResponse$SecurityGroups": "<p>An array of security groups.</p>",
+        "ModifyMountTargetSecurityGroupsRequest$SecurityGroups": "<p>An array of up to five VPC security group IDs.</p>"
+      }
+    },
+    "SubnetId": {
+      "base": null,
+      "refs": {
+        "CreateMountTargetRequest$SubnetId": "<p>The ID of the subnet to add the mount target in.</p>",
+        "MountTargetDescription$SubnetId": "<p>The ID of the subnet that the mount target is in.</p>"
+      }
+    },
+    "SubnetNotFound": {
+      "base": "<p>Returned if there is no subnet with ID <code>SubnetId</code> provided in the request.</p>",
+      "refs": {
+      }
+    },
+    "Tag": {
+      "base": "<p>A tag is a pair of key and value. The allowed characters in keys and values are letters, whitespace, and numbers, representable in UTF-8, and the characters '+', '-', '=', '.', '_', ':', and '/'. </p>",
+      "refs": {
+        "Tags$member": null
+      }
+    },
+    "TagKey": {
+      "base": null,
+      "refs": {
+        "Tag$Key": "<p>Tag key, a string. The key must not start with \"aws:\".</p>",
+        "TagKeys$member": null
+      }
+    },
+    "TagKeys": {
+      "base": null,
+      "refs": {
+        "DeleteTagsRequest$TagKeys": "<p>A list of tag keys to delete.</p>"
+      }
+    },
+    "TagValue": {
+      "base": null,
+      "refs": {
+        "FileSystemDescription$Name": "<p>You can add tags to a file system (see <a>CreateTags</a>) including a \"Name\" tag. If the file system has a \"Name\" tag, Amazon EFS returns the value in this field. </p>",
+        "Tag$Value": "<p>Value of the tag key.</p>"
+      }
+    },
+    "Tags": {
+      "base": null,
+      "refs": {
+        "CreateTagsRequest$Tags": "<p> An array of <code>Tag</code> objects to add. Each <code>Tag</code> object is a key-value pair. </p>",
+        "DescribeTagsResponse$Tags": "<p>Returns tags associated with the file system as an array of <code>Tag</code> objects. </p>"
+      }
+    },
+    "Timestamp": {
+      "base": null,
+      "refs": {
+        "FileSystemDescription$CreationTime": "<p>The time at which the file system was created, in seconds, since 1970-01-01T00:00:00Z.</p>",
+        "FileSystemSize$Timestamp": "<p>The time at which the size of data, returned in the <code>Value</code> field, was determined. The value is the integer number of seconds since 1970-01-01T00:00:00Z.</p>"
+      }
+    },
+    "UnsupportedAvailabilityZone": {
+      "base": null,
+      "refs": {
+      }
+    }
+  }
+}

data/lib/aws-sdk-core.rb

@@ -37,6 +37,7 @@ module Aws
     DynamoDB
     EC2
     ECS
+    EFS
     ElastiCache
     ElasticBeanstalk
     ElasticLoadBalancing

data/lib/aws-sdk-core/efs.rb

@@ -0,0 +1,4 @@
+Aws.add_service(:EFS, {
+  api: "#{Aws::API_DIR}/elasticfilesystem/2015-02-01/api-2.json",
+  docs: "#{Aws::API_DIR}/elasticfilesystem/2015-02-01/docs-2.json",
+})

data/lib/aws-sdk-core/signers/s3.rb

@@ -11,7 +11,7 @@ module Aws
 
         acl delete cors lifecycle location logging notification partNumber
         policy requestPayment restore tagging torrent uploadId uploads
-        versionId versioning versions website
+        versionId versioning versions website replication requestPayment
 
         response-content-type response-content-language
         response-expires response-cache-control

data/lib/aws-sdk-core/version.rb

@@ -1,3 +1,3 @@
 module Aws
-  VERSION = '2.0.45'
+  VERSION = '2.0.46'
 end

data/lib/seahorse/client/plugins/restful_bindings.rb

@@ -69,7 +69,9 @@ module Seahorse
                 status_code = response.context.http_response.status_code
                 response.data[key] = status_code
               when 'header'
-                response.data[key] = extract_header(headers, shape)
+                if headers.key?(shape.location_name)
+                  response.data[key] = extract_header(headers, shape)
+                end
               when 'headers'
                 response.data[key] = extract_header_map(headers, shape)
               end