Managing your AWS Europe credit card payment verifications

Managing your AWS Europe credit card payment verifications

To comply with the recent EU regulation, your bank might ask you for verification whenever you use a credit card to pay AWS online, add or update a credit card, or register a new AWS account. Banks typically verify by sending unique security codes to credit card holders before online purchases are completed. If your bank needs to verify your payment, you will receive an email from AWS. After verification, you’re redirected to the AWS website.

If you prefer not to verify payments, register a bank account as your payment method. For more information about direct debit payment eligibility, see Managing your SEPA direct debit payment methods.

To learn more about the EU regulation, see the European Commission’s website .

Considerations before you close your AWS account

Before closing your AWS account, consider the following:

Topics

Your agreement with AWS

Your closure of your AWS account serves as a notice to us that you want to terminate the AWS customer agreement or other agreements with AWS that governs your AWS account, solely with respect to the specific AWS account. If you reopen your AWS account during the post-closure period (that is, within 90 days after your account is closed), you agree that the same agreement terms will govern your access to and use of the service offerings through your reopened AWS account.

If you close the account that you’re using for the AWS Firewall Manager administrator, AWS and Firewall Manager handle the closure as follows:

AWS retains the policy data for the account for 90 days from the effective date of the administrator account closure. At the end of the 90 day period, AWS permanently deletes all policy data for the account.

To retain findings for more than 90 days, you can archive the policies. You can also use a custom action with an EventBridge rule to store the findings in an S3 bucket.

As long as AWS retains the policy data, when you reopen the closed account, AWS reassigns the account as the service administrator and recovers the service policy data for the account.

For customers in the AWS GovCloud (US) Regions:

Before closing your account, back up and then delete your policy data and other account resources. You will no longer have access to them after you close the account.

AWS management console access

Your access to the AWS Management Console for the closed AWS account is restricted. During the post-closure period, you can still sign in to your AWS account to view your past billing information and access AWS Support. You can’t access any other AWS services or start any new AWS services in the closed account.

Existing content and services still in use

Before you close your AWS account, we recommend that you retrieve the content that you want to keep and delete the remaining resources. For instructions on how to retrieve data and delete resources, see the documentation for that service.

After the post-closure period, any remaining content in your AWS account is deleted, and services that are still in use are terminated. For more information about the post-closure period, see Accessing your AWS account after closure.

Your payment method

We charge you through your designated payment method for any usage fees incurred before you closed your AWS account. We might issue you any refunds that are due through that same payment method. If you have active subscriptions, even after your account is closed, you might continue to be charged for the subscription until the subscription expires or is sold according to the terms governing the subscription. If you’re charged, you’re charged through your designated payment method. This situation might apply to you if, for example, you have a Reserved Instance that you pay for on a monthly basis. These charges and refunds might occur after you close your account.

In addition, if you reopen your account, you might be charged for the cost of running AWS services during the post-closure period. This is specifically for any services that you didn’t terminate before closing your account.

Closing your AWS account doesn’t affect payment methods that you use on Amazon.com or other Amazon websites.

Accounts protected by MFA

If you’ve turned on multi-factor authentication (MFA) on your AWS account root user, or configured an MFA device on an IAM user, the MFA isn’t removed automatically when you close the account. If you choose to leave the MFA turned on during the 90 days post-closure period, keep the virtual hardware MFA device active until the post-closure period expired in case you need to access the account during that time.

You have the option to turn off the MFA device before closing the account. MFA devices for IAM users must be deleted by the account administrator.

On-Demand charges

During the post-closure period, billing for On-Demand charges stops. However, you’re billed for any usage that has accrued up until the time you closed your account. You’ll be charged for that usage at the beginning of the next month. In addition, if you purchased any subscriptions with ongoing payment obligations, you might continue to be charged for them after your account is closed.

If you don’t terminate your resources, you will continue to generate costs.

Domains registered with Amazon RouteВ 53

Domains that are registered with RouteВ 53 are not deleted automatically. When you’re closing your AWS account, you have three options:

You can disable automatic renewal, and the domains are deleted when the registration period expires. For more information, see Enabling or Disabling Automatic Renewal for a Domain in the Amazon RouteВ 53 Developer Guide.

You can transfer the domains to another AWS account. For more information, see Transferring a Domain to a Different AWS account.

You can transfer the domains to another domain registrar. For more information, see Transferring a Domain from RouteВ 53 to Another Registrar.

If you already closed the account, you can open a case with AWS Support to get help with disabling automatic renewal or transferring your domains. For more information, see Contacting AWS Support About Domain Registration Issues. There is no charge to open a case for domain registration issues.

Charges if you reopen your AWS account

If you reopen your AWS account during the post-closure period, you might be billed for the cost of any AWS services that aren’t terminated before you closed your account.

Example

You reopen your AWS account 30 days after closure, and your AWS account had only an active t-example.example Amazon EC2 instance at closure. The price for a t-example.example Amazon EC2 instance in your AWS Region is

Closing your AWS account

You can close your AWS account using the following procedure.

To close your AWS account

Open the Billing and Cost Management console at https://console.aws.amazon.com/billing/home#/ .

On the navigation bar in the upper-right corner, choose your account name (or alias), and choose Account.

Scroll to the end of the page to the Close Account section. Read and ensure that you understand the text next to the check box. After you close an AWS account, you can no longer use it to access AWS services.

If the account has a multi-factor authentication (MFA) device turned on, keep your MFA device until the 90 day post-closure period expires, or turn off before closing the account.

Select the check box to accept the terms, and choose Close Account.

In the confirmation box, choose Close Account.

.01 each hour. In this case, you might be charged for 30 days x 24 hours x

After the post-closure period

After the Post-Closure Period, we permanently close your AWS account, and you can’t reopen it. Any content that you didn’t delete is deleted, and any AWS services that you didn’t terminate are terminated. Service attributes can be retained as long as needed for billing and administration purposes. You also can’t create a new AWS account using the same alias or email address that was registered to your AWS account at the time of its closure.

If you close the account that you’re using for the AWS Firewall Manager administrator, AWS and Firewall Manager handle the closure as follows:

AWS retains the policy data for the account for 90 days from the effective date of the administrator account closure. At the end of the 90 day period, AWS permanently deletes all policy data for the account.

To retain findings for more than 90 days, you can archive the policies. You can also use a custom action with an EventBridge rule to store the findings in an S3 bucket.

Читать еще:  Рецепты хреновухи на спирту: из чего и как сделать настойку в домашних условиях, от каких болезней она помогает и есть ли у нее противопоказания?

As long as AWS retains the policy data, when you reopen the closed account, AWS reassigns the account as the service administrator and recovers the service policy data for the account.

For customers in the AWS GovCloud (US) Regions:

Before closing your account, back up and then delete your policy data and other account resources. You will no longer have access to them after you close the account.

.01 per hour = $7.20 for your AWS services.

Closing a member account

When you close an account that was created with AWS Organizations, that account isn’t removed from the organization until after the post-closure period. During the post-closure period, a closed member account still counts toward your quota of accounts in the organization.

To avoid having the account count against the limit, remove member accounts from the organization before closing it. For more information, see Closing an AWS account in the AWS Organizations User Guide.

Cross-account access to the account you’re closing

After you close your AWS account, any access requests to your closed account’s AWS services from other AWS accounts fail. This occurs even if you have granted the other accounts permission to access your account’s AWS services. If you reopen your AWS account, other AWS accounts can access your account’s AWS services if you have granted the other accounts the necessary permissions.

Removing Amazon VPC peering connection

AWS currently doesn’t delete Amazon VPC peering connections when you close one of the accounts participating in the VPC peering connection. Any traffic that’s destined for the VPC peering connection and originates from other active accounts is dropped. This is because AWS terminates instances and deletes any security groups in the closed account. To remove the VPC peering connection, you can delete it from your account using the Amazon VPC console, AWS CLI, or Amazon EC2 API.

Make a payment using a credit or debit card

You can use the console to pay your AISPL bills.

To pay your AISPL bill

Sign in to the AWS Management Console and open the AWS Billing console at https://console.aws.amazon.com/billing/ .

In the navigation pane, choose Orders and invoices.

Next to the invoice that you want to pay, choose Verify and pay. You’re redirected to your payment methods.

On the Payment Methods page, select the payment method that you want to use.

In the Make Payment box, enter the three-digit or four-digit security code of your payment method and then choose Make Payment.

In the dialog box, choose Ok.

For Visa and Mastercard payment methods, you’re redirected to your bank to verify your payment. For American Express payment methods, your bank processes your payment with no action required from you. After your payment is verified, you’re redirected to your account page. Your invoice shows the Verify and pay link until your bank processes your payment.

Resolution

Account considerations

Consider the following when closing your account:

Before closing your account

  • You must have completed the account sign up process.
  • Sign in as the AWS account root user. If you sign in to an account with an AWS Identity and Access Management (IAM) user or role, you can’t close the account.
  • Back up any resources or data that you want to keep. For instructions about how to back up a particular resource, see the AWS documentation for that service.
  • For AWS Organization accounts:
    By default, member accounts don’t have a root password. Before you can sign in as the root user, you must reset the root user password for these accounts.
    If your account is the management account of an organization, you must make sure that all member accounts are closed or removed from your organization. For more information, see Removing a member account from your organization.
    To close the payer account in an organization, first delete the organization.

After closing your account

  • You can still sign in and file an AWS Support case or contact Support for 90 days.
  • After 90 days, any content remaining in your account will be permanently deleted, and AWS services that aren’t already terminated will be terminated. However, service attributes might be retained as long as necessary for billing and administration purposes. AWS retains your account information as described in the Privacy Notice. You can’t permanently delete your account before 90 days. You can’t reopen the account after 90 days.
    Note: The account resources in AWS China (Beijing) and AWS China (Ningxia) Regions are subject to the policies of operating partners (Sinnet in the Beijing Region and NWCD in the Ningxia Region). Account closure procedures in China might take longer than in other AWS Regions.
  • You can’t create new AWS accounts using the email address that was associated with your account at the time of its closure.

Billing considerations

Consider the following before closing your account:

  • If you purchased any subscriptions with ongoing payment commitments, such as Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instances (RIs) and Savings Plans, then you are charged for these subscriptions until the plan term ends even after you close your account.
  • After your AWS account is closed, your designated payment method is charged for any usage fees that were incurred before closure. If applicable, refunds are issued through the same payment method.
  • You must add a valid credit card, debit card, or another payment method to close your account.
  • If you reopen your closed AWS account within 90 days, you might be charged for any AWS services that aren’t terminated before you closed the account.

Terminate all your resources before closing your account

Closing your account might not automatically terminate all your active resources. You might continue to incur charges for some of your active resources even after you close your account. You’re charged for any usage fees incurred before closure.

Before closing your account, do the following:

Pay your outstanding bills

View your outstanding bills and be sure that there are no overdue payments:

  1. Open the Billing and Cost Management console.
  2. Choose Payments in the navigation pane. You can see your overdue payments in the Payments Due section.
  3. Choose Verify and pay next to unpaid bills.

Close your account

To close your AWS account, do the following:

  1. Sign in to the AWS Management Console as the root user of the account.
  2. From the navigation bar, choose your account name, and then choose Account.
  3. Scroll to the Close Account section.
  4. Read and understand the terms of closing your account.
  5. Select all check boxes, and then choose Close Account.
  6. In the confirmation box, choose Close Account.

Within a few minutes, you receive email confirmation that your account is closed successfully.

You can choose to sign in to your account three days after closing the account to check if all the resources are terminated. Open the AWS Billing and Cost Management console to monitor whether you continue to incur charges. You can contact AWS Support if you continue to incur charges after terminating all resources.

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

For information about the errors that are common to all actions, see Common Errors.

You don’t have permissions to perform the requested operation. The user or role that is making the request must have at least one IAM permissions policy attached that grants the required permissions. For more information, see Access Management in the IAM User Guide.

HTTP Status Code: 400

AccountNotFoundException

We can’t find an AWS account with the AccountId that you specified, or the account whose credentials you used to make this request isn’t a member of an organization.

HTTP Status Code: 400

AWSOrganizationsNotInUseException

Your account isn’t a member of an organization. To make this request, you must use the credentials of an account that belongs to an organization.

HTTP Status Code: 400

ConcurrentModificationException

The target of the operation is currently being modified by a different request. Try again later.

HTTP Status Code: 400

ConstraintViolationException

Performing this operation violates a minimum or maximum value limit. For example, attempting to remove the last service control policy (SCP) from an OU or root, inviting or creating too many accounts to the organization, or attaching too many policies to an account, OU, or root. This exception includes a reason that contains additional information about the violated limit:

Some of the reasons in the following list might not be applicable to this specific API or operation.

ACCOUNT_CANNOT_LEAVE_ORGANIZATION: You attempted to remove the management account from the organization. You can’t remove the management account. Instead, after you remove all member accounts, delete the organization itself.

Читать еще:  Выращивания грибов в домашних условиях

ACCOUNT_CANNOT_LEAVE_WITHOUT_PHONE_VERIFICATION: You attempted to remove an account from the organization that doesn’t yet have enough information to exist as a standalone account. This account requires you to first complete phone verification. Follow the steps at Removing a member account from your organization in the AWS Organizations User Guide.

ACCOUNT_CREATION_RATE_LIMIT_EXCEEDED: You attempted to exceed the number of accounts that you can create in one day.

ACCOUNT_NUMBER_LIMIT_EXCEEDED: You attempted to exceed the limit on the number of accounts in an organization. If you need more accounts, contact AWS Support to request an increase in your limit.

Or the number of invitations that you tried to send would cause you to exceed the limit of accounts in your organization. Send fewer invitations or contact AWS Support to request an increase in the number of accounts.

Deleted and closed accounts still count toward your limit.

If you get this exception when running a command immediately after creating the organization, wait one hour and try again. After an hour, if the command continues to fail with this error, contact AWS Support.

CANNOT_REGISTER_MASTER_AS_DELEGATED_ADMINISTRATOR: You attempted to register the management account of the organization as a delegated administrator for an AWS service integrated with Organizations. You can designate only a member account as a delegated administrator.

CANNOT_CLOSE_MANAGEMENT_ACCOUNT: You attempted to close the management account. To close the management account for the organization, you must first either remove or close all member accounts in the organization. Follow standard account closure process using root credentials.​

CANNOT_REMOVE_DELEGATED_ADMINISTRATOR_FROM_ORG: You attempted to remove an account that is registered as a delegated administrator for a service integrated with your organization. To complete this operation, you must first deregister this account as a delegated administrator.

CLOSE_ACCOUNT_QUOTA_EXCEEDED: You have exceeded close account quota for the past 30 days.

CLOSE_ACCOUNT_REQUESTS_LIMIT_EXCEEDED: You attempted to exceed the number of accounts that you can close at a time. ​

CREATE_ORGANIZATION_IN_BILLING_MODE_UNSUPPORTED_REGION: To create an organization in the specified region, you must enable all features mode.

DELEGATED_ADMINISTRATOR_EXISTS_FOR_THIS_SERVICE: You attempted to register an AWS account as a delegated administrator for an AWS service that already has a delegated administrator. To complete this operation, you must first deregister any existing delegated administrators for this service.

EMAIL_VERIFICATION_CODE_EXPIRED: The email verification code is only valid for a limited period of time. You must resubmit the request and generate a new verfication code.

HANDSHAKE_RATE_LIMIT_EXCEEDED: You attempted to exceed the number of handshakes that you can send in one day.

INVALID_PAYMENT_INSTRUMENT: You cannot remove an account because no supported payment method is associated with the account. AWS does not support cards issued by financial institutions in Russia or Belarus. For more information, see Managing your AWS payments.

MASTER_ACCOUNT_ADDRESS_DOES_NOT_MATCH_MARKETPLACE: To create an account in this organization, you first must migrate the organization’s management account to the marketplace that corresponds to the management account’s address. For example, accounts with India addresses must be associated with the AISPL marketplace. All accounts in an organization must be associated with the same marketplace.

MASTER_ACCOUNT_MISSING_BUSINESS_LICENSE: Applies only to the AWS /> Regions in China. To create an organization, the master must have a valid business license. For more information, contact customer support.

MASTER_ACCOUNT_MISSING_CONTACT_INFO: To complete this operation, you must first provide a valid contact address and phone number for the management account. Then try the operation again.

MASTER_ACCOUNT_NOT_GOVCLOUD_ENABLED: To complete this operation, the management account must have an associated account in the AWS GovCloud (US-West) Region. For more information, see AWS Organizations in the AWS GovCloud User Guide.

MASTER_ACCOUNT_PAYMENT_INSTRUMENT_REQUIRED: To create an organization with this management account, you first must associate a valid payment instrument, such as a credit card, with the account. Follow the steps at To leave an organization when all required account information has not yet been provided in the AWS Organizations User Guide.

MAX_DELEGATED_ADMINISTRATORS_FOR_SERVICE_LIMIT_EXCEEDED: You attempted to register more delegated administrators than allowed for the service principal.

MAX_POLICY_TYPE_ATTACHMENT_LIMIT_EXCEEDED: You attempted to exceed the number of policies of a certain type that can be attached to an entity at one time.

MAX_TAG_LIMIT_EXCEEDED: You have exceeded the number of tags allowed on this resource.

MEMBER_ACCOUNT_PAYMENT_INSTRUMENT_REQUIRED: To complete this operation with this member account, you first must associate a valid payment instrument, such as a credit card, with the account. Follow the steps at To leave an organization when all required account information has not yet been provided in the AWS Organizations User Guide.

MIN_POLICY_TYPE_ATTACHMENT_LIMIT_EXCEEDED: You attempted to detach a policy from an entity that would cause the entity to have fewer than the minimum number of policies of a certain type required.

ORGANIZATION_NOT_IN_ALL_FEATURES_MODE: You attempted to perform an operation that requires the organization to be configured to support all features. An organization that supports only consolidated billing features can’t perform this operation.

OU_DEPTH_LIMIT_EXCEEDED: You attempted to create an OU tree that is too many levels deep.

OU_NUMBER_LIMIT_EXCEEDED: You attempted to exceed the number of OUs that you can have in an organization.

POLICY_CONTENT_LIMIT_EXCEEDED: You attempted to create a policy that is larger than the maximum size.

POLICY_NUMBER_LIMIT_EXCEEDED: You attempted to exceed the number of policies that you can have in an organization.

SERVICE_ACCESS_NOT_ENABLED: You attempted to register a delegated administrator before you enabled service access. Call the EnableAWSServiceAccess API first.

TAG_POLICY_VIOLATION: You attempted to create or update a resource with tags that are not compliant with the tag policy requirements for this account.

WAIT_PERIOD_ACTIVE: After you create an AWS account, there is a waiting period before you can remove it from the organization. If you get an error that indicates that a wait period is required, try again in a few days.

HTTP Status Code: 400

InvalidInputException

The requested operation failed because you provided invalid values for one or more of the request parameters. This exception includes a reason that contains additional information about the violated limit:

Some of the reasons in the following list might not be applicable to this specific API or operation.

DUPLICATE_TAG_KEY: Tag keys must be unique among the tags attached to the same entity.

IMMUTABLE_POLICY: You specified a policy that is managed by AWS and can’t be modified.

INPUT_REQUIRED: You must include a value for all required parameters.

INVALID_EMAIL_ADDRESS_TARGET: You specified an invalid email address for the invited account owner.

INVALID_ENUM: You specified an invalid value.

INVALID_ENUM_POLICY_TYPE: You specified an invalid policy type string.

INVALID_FULL_NAME_TARGET: You specified a full name that contains invalid characters.

INVALID_LIST_MEMBER: You provided a list to a parameter that contains at least one invalid value.

INVALID_PAGINATION_TOKEN: Get the value for the NextToken parameter from the response to a previous call of the operation.

INVALID_PARTY_TYPE_TARGET: You specified the wrong type of entity (account, organization, or email) as a party.

INVALID_PATTERN: You provided a value that doesn’t match the required pattern.

INVALID_PATTERN_TARGET_ID: You specified a policy target ID that doesn’t match the required pattern.

INVALID_ROLE_NAME: You provided a role name that isn’t valid. A role name can’t begin with the reserved prefix AWSServiceRoleFor .

INVALID_SYNTAX_ORGANIZATION_ARN: You specified an invalid Amazon Resource Name (ARN) for the organization.

INVALID_SYNTAX_POLICY_ID: You specified an invalid policy ID.

INVALID_SYSTEM_TAGS_PARAMETER: You specified a tag key that is a system tag. You can’t add, edit, or delete system tag keys because they’re reserved for AWS use. System tags don’t count against your tags per resource limit.

MAX_FILTER_LIMIT_EXCEEDED: You can specify only one filter parameter for the operation.

MAX_LENGTH_EXCEEDED: You provided a string parameter that is longer than allowed.

MAX_VALUE_EXCEEDED: You provided a numeric parameter that has a larger value than allowed.

MIN_LENGTH_EXCEEDED: You provided a string parameter that is shorter than allowed.

MIN_VALUE_EXCEEDED: You provided a numeric parameter that has a smaller value than allowed.

MOVING_ACCOUNT_BETWEEN_DIFFERENT_ROOTS: You can move an account only between entities in the same root.

TARGET_NOT_SUPPORTED: You can’t perform the specified operation on that target entity.

UNRECOGNIZED_SERVICE_PRINCIPAL: You specified a service principal that isn’t recognized.

HTTP Status Code: 400

MasterCannotLeaveOrganizationException

You can’t remove a management account from an organization. If you want the management account to become a member account in another organization, you must first delete the current organization of the management account.

HTTP Status Code: 400

ServiceException

AWS Organizations can’t complete your request because of an internal service error. Try again later.

HTTP Status Code: 400

TooManyRequestsException

You have sent too many requests in too short a period of time. The quota helps protect against denial-of-service attacks. Try again later.

For information about quotas that affect AWS Organizations, see Quotas for AWS Organizationsin the AWS Organizations User Guide.

HTTP Status Code: 400

Managing your ACH direct debit payment methods

If you meet the eligibility requirements, you can add a US bank account as an ACH direct debit payment method to your payment methods.

To be eligible, your account must meet the following requirements:

It is an Amazon Web Services customer.

Читать еще:  Как прищипывать базилик в открытом грунте: нужна ли растению пинцировка, когда это лучше делать, как правильно провести процедуру, надо ли срезать взрослые побеги?

It is at least 60 days old.

It has paid at least one invoice in full in the previous 12 months.

It has paid at least $100 cumulative over the previous 12 months.

It uses USD as the preferred currency.

If you pay by ACH direct debit, AWS provides you with your invoice and initiates the charge to your payment method within 10 days of the start of the month. It can take up to 20 days for the payment to complete successfully, even if the payment shows as Succeeded on the Billing and Cost Management console.

To add a direct debit account to your AWS payment methods

You can use the Billing and Cost Management console to add a direct debit account to your AWS payment methods. You can use any personal or business bank account, provided that the account is located at a branch in the US.

To add an ACH direct debit account, you must have the following information ready:

A US bank account number

A US bank account routing number

The address that the bank associates with the account

(For a personal bank account) A US driver’s license number or state-issued ID number

(For a business bank account) A Federal tax ID number

Sign in to the AWS Management Console and open the AWS Billing console at https://console.aws.amazon.com/billing/ .

In the navigation pane, choose Payment methods .

Choose Add a bank account.

For Account Holder Name, enter the name of the principal account holder.

For Bank Routing Number, enter the nine-digit routing number.

Routing numbers are always nine digits long. Some banks list the routing number first on a check, and other banks list the account number first.

For Bank Account Number, enter the account number. Account numbers might have up to 17 digits. The account must be an ACH-enabled checking account at a bank located in the US.

For Bank Account Type, choose Personal or Business.

(Personal) For Driver’s License Number, enter the primary account holder’s valid US driver’s license or state-issued ID number.

For State, enter the name of the state where the ID was issued.

(Business) For Federal tax ID, enter the Federal tax ID for the business.

For Make Default, select whether you want this direct debit account to be your default payment method.

For Billing Address Information, enter the valid US billing address of the primary account holder.

Choose Create to agree to the Terms and Conditions and add your direct debit account.

To update your direct debit account

You can update the name, address, or phone number associated with your direct debit account.

In the navigation pane, choose Payment methods.

Next to the direct debit account that you want to edit, choose Edit.

Update the information that you want to change.

At the bottom of the dialog box, choose Update.

Features of Billing

Manage your account settings using the AWS Management Console and Billing console. This includes designating your default currency, editing alternate contacts, adding or removing Regions, updating your tax information, and closing your AWS account. The close your account section calls out considerations such as terminating resources before you proceed with closing an account. This way, you aren’t charged for unused services.

View your bill

You can use the Billing console to view your past bill details or your estimated charges for your current month at any time. This section outlines how you can view your bills, download PDF copies of your charges, and set up monthly emails to receive your invoices. It also covers how you can use other resources such as AWS Cost and Usage Reports.

Managing your payments

You can view your estimated bills and pay your AWS invoices in your preferred currency by setting a payment currency. AWS converts your bill to your preferred currency after your bill is finalized. Until then, all of the preferred currency amounts shown in the console are estimated in USD. AWS guarantees your exchange rate. This is so that refunds use the same exchange rate as your original transaction.

AWS Marketplace invoices aren’t eligible for this service and are processed in US dollar.

This service is available only if your default payment method is Visa or MasterCard.

The rates change daily. The rate that’s applied to your invoice is the current rate at the time when your invoice was created. You can check the current rate on the Billing console.

Currency conversion is provided by Amazon Services LLC.

AWS Purchase Order Management

Manage your AWS purchase orders in a self-service fashion by taking care of multiple purchase orders all in one place. This can help to reduce your overhead costs and increase the accuracy and efficiency in your overall procure-to-pay process. Use the Billing console to manage your purchase orders and configure how they reflect on your invoices. In this chapter, learn how to add, edit, view details, and set up notifications regarding your purchase orders in the console.

AWS Cost Categories

Manage your AWS costs with AWS Cost Categories by mapping your cost and usage into meaningful categories. This section defines terms that are used in the console for supported dimensions, operations, rule types, and status. The section also provides more information on how you can create, edit, delete, and split the charges within cost categories.

Payment profile

You can use payment profiles to assign more than one payment method to your automatic payments. If you receive invoices from more than one AWS service provider («seller of record»), you can use payment profiles to assign a unique payment method for each one. After you create a payment profile for a service provider, your payment profile pays your AWS bills automatically. In this section, learn how to use the Billing console to set up custom payment profile.

Consolidate billing for AWS Organizations

Use the consolidated billing feature for AWS Organizations to combine your billing for multiple AWS accounts. This chapter outlines the consolidated billing process, differences for Amazon Internet Services Pvt. Ltd accounts, and details for discounts.

Managing your US tax exemptions

If your state is eligible, you can manage your US tax exemptions on the Tax Settings page. The documents you upload for the exemption are reviewed by AWS Support within 24 hours.

To upload or add your US tax exemption

(Prerequisite) Ensure you have the IAM permissions to view the Tax exemptions tab on the Tax Settings page in the Billing console.

Sign in to the AWS Management Console and open the AWS Billing console at https://console.aws.amazon.com/billing/ .

In the navigation pane, choose Tax Settings.

Choose Set up tax exemption.

(If you have existing tax exemptions uploaded) Choose Add tax exemption.

Specify your exemption type and jurisdiction.

Upload certificate documents.

Review your information, and choose Submit.

Within 24 hours, AWS Support will notify you through a support case if they need additional information, or if any of your documents weren’t valid.

Once the exemption is approved, you’ll see it under the Tax exemption tab with an Active validity period.

You’ll be notified through a support case contact if your exemption was rejected.

You can add funds to Advance Pay using electronic funds transfer, or a personal or business bank account.

To add funds to your Advance Pay using electronic funds transfer

In the navigation pane, choose Payments.

Choose the Advance Pay tab.

Choose Add funds.

Under Amount, enter the fund amount that you want to add.

The amount must be entered in US dollars.

Under Payment method, choose Choose payment method.

Choose Wire transfer.

Choose Use this payment method.

Review the payment details, and choose Verify.

Complete your electronic funds transfer by using the instructions in the Payment summary section.

To add funds to your Advance Pay using a bank account

In the navigation pane, choose Payments.

Choose the Advance Pay tab.

Choose Add funds.

Under Amount, enter the fund amount that you want to add.

The amount must be entered in US dollars.

Under Payment method, choose Choose payment method.

Choose Bank account.

Choose Use this payment method.

Review the payment details, and choose Add funds.

Your bank account will automatically be charged with the fund amount that you entered.

You can download the funding summary document from the Advance pay summary page.

Thanks for letting us know we’re doing a good job!

If you’ve got a moment, please tell us what we did right so we can do more of it.

Thanks for letting us know this page needs work. We’re sorry we let you down.

If you’ve got a moment, please tell us how we can make the documentation better.

Ссылка на основную публикацию
Статьи на тему:

Adblock
detector