aws-sdk-organizations 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f218d7f19e603e12ee28b3dac1f9793085cdb363
-  data.tar.gz: 8cb7b529af5bae4076ac6286cfa542f84c3218ea
+  metadata.gz: 674bb4fbb99f4a9c8e335b983bf78adf5a73125c
+  data.tar.gz: 6a532b7e1991c5bde5738921d282732fdc8a06b5
 SHA512:
-  metadata.gz: 9306a204f4ee9100446af9f5510a48930dfac6b29fc689e227b5f604e11a134ec5114e9415e9db55e441937456f01222dad60d562f03b90653670bb8951675ee
-  data.tar.gz: 7ced4295c8a43abd196b587703a4b3d0ce7c760dcf3c26d7e101cc6a60e524659ca48c30aa6f39dd335e6b93d2d31212e8869682798b6e7b48d31e4c06ad22bb
+  metadata.gz: d7bc4abfed3458ba08e92a7c5e46d275dc3ab6d738e3c174850188362a960758cbfc4a454c91250aca0f001968073eb8123c2697418fe69b469c201b1e402529
+  data.tar.gz: 2950c52d165a420586d997e5adb624aba73ed9b73414fb40c8b152a76b4d474f77b05f3b373b19a17acd556995f5fd74025a663b6914ad9a6370608c83ce8cd6

data/lib/aws-sdk-organizations.rb

@@ -42,6 +42,6 @@ require_relative 'aws-sdk-organizations/customizations'
 # @service
 module Aws::Organizations
 
-  GEM_VERSION = '1.0.0'
+  GEM_VERSION = '1.1.0'
 
 end

data/lib/aws-sdk-organizations/client.rb

@@ -539,10 +539,15 @@ module Aws::Organizations
     # Account in Your Organization][1] in the *AWS Organizations User
     # Guide*.
     #
-    # You cannot remove accounts that are created with this operation from
-    # an organization. That also means that you cannot delete an
-    # organization that contains an account that is created with this
-    # operation.
+    # When you create an account in an organization using the AWS
+    # Organizations console, API, or CLI commands, the information required
+    # for the account to operate as a standalone account, such as a payment
+    # method and signing the End User Licence Agreement (EULA) is *not*
+    # automatically collected. If you must remove an account from your
+    # organization later, you can do so only after you provide the missing
+    # information. Follow the steps at [ To leave an organization when all
+    # required account information has not yet been provided][2] in the *AWS
+    # Organizations User Guide*.
     #
     # <note markdown="1"> When you create a member account with this operation, you can choose
     # whether to create the account with the **IAM User and Role Access to
@@ -551,17 +556,24 @@ module Aws::Organizations
     # for the account. If you disable this, then only the account root user
     # can access billing information. For information about how to disable
     # this for an account, see [Granting Access to Your Billing Information
-    # and Tools][2].
+    # and Tools][3].
     #
     #  </note>
     #
     # This operation can be called only from the organization's master
     # account.
     #
+    # If you get an exception that indicates that you exceeded your account
+    # limits for the organization or that you can"t add an account because
+    # your organization is still initializing, please contact [ AWS Customer
+    # Support][4].
+    #
     #
     #
     # [1]: http://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_create.html
-    # [2]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html
+    # [2]: http://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_remove.html#leave-without-all-info
+    # [3]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html
+    # [4]: https://console.aws.amazon.com/support/home#/
     #
     # @option params [required, String] :email
     #   The email address of the owner to assign to the new member account.
@@ -1099,10 +1111,6 @@ module Aws::Organizations
     # credentials from the master account. The organization must be empty of
     # member accounts, OUs, and policies.
     #
-    # If you create any accounts using Organizations operations or the
-    # Organizations console, you can't remove those accounts from the
-    # organization, which means that you can't delete the organization.
-    #
     # @return [Struct] Returns an empty {Seahorse::Client::Response response}.
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/organizations-2016-11-28/DeleteOrganization AWS API Documentation
@@ -1975,19 +1983,26 @@ module Aws::Organizations
     # invitation is implemented as a Handshake whose details are in the
     # response.
     #
-    # You can invite AWS accounts only from the same reseller as the master
+    # You can invite AWS accounts only from the same seller as the master
     # account. For example, if your organization's master account was
-    # created by Amazon Internet Services Pvt. Ltd (AISPL), an AWS reseller
-    # in India, then you can only invite other AISPL accounts to your
-    # organization. You can't combine accounts from AISPL and AWS. For more
-    # information, see [Consolidated Billing in India][1].
+    # created by Amazon Internet Services Pvt. Ltd (AISPL), an AWS seller in
+    # India, then you can only invite other AISPL accounts to your
+    # organization. You can't combine accounts from AISPL and AWS, or any
+    # other AWS seller. For more information, see [Consolidated Billing in
+    # India][1].
     #
     # This operation can be called only from the organization's master
     # account.
     #
+    # If you get an exception that indicates that you exceeded your account
+    # limits for the organization or that you can"t add an account because
+    # your organization is still initializing, please contact [ AWS Customer
+    # Support][2].
+    #
     #
     #
     # [1]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/useconsolidatedbilliing-India.html
+    # [2]: https://console.aws.amazon.com/support/home#/
     #
     # @option params [required, Types::HandshakeParty] :target
     #   The identifier (ID) of the AWS account that you want to invite to join
@@ -2124,18 +2139,30 @@ module Aws::Organizations
     #   from successfully calling `LeaveOrganization` and leaving the
     #   organization.
     #
-    # * If you created the account using the AWS Organizations console, the
-    #   Organizations API, or the Organizations CLI commands, then you
-    #   cannot remove the account.
+    # * You can leave an organization as a member account only if the
+    #   account is configured with the information required to operate as a
+    #   standalone account. When you create an account in an organization
+    #   using the AWS Organizations console, API, or CLI commands, the
+    #   information required of standalone accounts is *not* automatically
+    #   collected. For each account that you want to make standalone, you
+    #   must accept the End User License Agreement (EULA), choose a support
+    #   plan, provide and verify the required contact information, and
+    #   provide a current payment method. AWS uses the payment method to
+    #   charge for any billable (not free tier) AWS activity that occurs
+    #   while the account is not attached to an organization. Follow the
+    #   steps at [ To leave an organization when all required account
+    #   information has not yet been provided][1] in the *AWS Organizations
+    #   User Guide*.
     #
     # * You can leave an organization only after you enable IAM user access
     #   to billing in your account. For more information, see [Activating
-    #   Access to the Billing and Cost Management Console][1] in the *AWS
+    #   Access to the Billing and Cost Management Console][2] in the *AWS
     #   Billing and Cost Management User Guide*.
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html#ControllingAccessWebsite-Activate
+    # [1]: http://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_remove.html#leave-without-all-info
+    # [2]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html#ControllingAccessWebsite-Activate
     #
     # @return [Struct] Returns an empty {Seahorse::Client::Response response}.
     #
@@ -3558,19 +3585,31 @@ module Aws::Organizations
     # account. Member accounts can remove themselves with LeaveOrganization
     # instead.
     #
-    # * You can remove only accounts that were created outside your
-    #   organization and invited to join. If you created the account using
-    #   the AWS Organizations console, the Organizations API, or the
-    #   Organizations CLI commands, then you cannot remove the account.
+    # * You can remove an account from your organization only if the account
+    #   is configured with the information required to operate as a
+    #   standalone account. When you create an account in an organization
+    #   using the AWS Organizations console, API, or CLI commands, the
+    #   information required of standalone accounts is *not* automatically
+    #   collected. For an account that you want to make standalone, you must
+    #   accept the End User License Agreement (EULA), choose a support plan,
+    #   provide and verify the required contact information, and provide a
+    #   current payment method. AWS uses the payment method to charge for
+    #   any billable (not free tier) AWS activity that occurs while the
+    #   account is not attached to an organization. To remove an account
+    #   that does not yet have this information, you must sign in as the
+    #   member account and follow the steps at [ To leave an organization
+    #   when all required account information has not yet been provided][1]
+    #   in the *AWS Organizations User Guide*.
     #
     # * You can remove a member account only after you enable IAM user
     #   access to billing in the member account. For more information, see
-    #   [Activating Access to the Billing and Cost Management Console][1] in
+    #   [Activating Access to the Billing and Cost Management Console][2] in
     #   the *AWS Billing and Cost Management User Guide*.
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html#ControllingAccessWebsite-Activate
+    # [1]: http://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_remove.html#leave-without-all-info
+    # [2]: http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html#ControllingAccessWebsite-Activate
     #
     # @option params [required, String] :account_id
     #   The unique identifier (ID) of the member account that you want to
@@ -3819,7 +3858,7 @@ module Aws::Organizations
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-organizations'
-      context[:gem_version] = '1.0.0'
+      context[:gem_version] = '1.1.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-organizations
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-08-29 00:00:00.000000000 Z
+date: 2017-08-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core