By using AWS re:Post, you agree to the Terms of Use
/AWS Billing/

Questions tagged with AWS Billing

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Root account no permissions

Hi All, I have not used my Amazon account for a while. I think it was free-tier to begin with. I wanted to start re-using it. I logged on and find I have no access to Billing. I also have no access to Organizations. I can assign privileges to IAM users. I had an existing user under IAM and I gave it Administrator and BillingAccess privileges. I logged on with that user, but when it browses to Organizations or Billing, it also gets permission denied issues. Example with root account accessing "Account": You Need Permissions You don't have permission to access billing information for this account. Contact your AWS administrator if you need help. If you are an AWS administrator, you can provide permissions for your users or groups by making sure that (1) this account allows IAM and federated users to access billing information and (2) you have the required IAM permissions. I get the same error when IAM user with billing permissions accesses "Billing". I cannot even create a support case using root account. It says I have no access and I was placed in support plan Basic, but then there is no way to create a case. When I click "Create case": An error occurred when we tried to process your request User: arn:aws:iam::ID:root is not authorized to perform: support:DescribeServices with an explicit deny in a service control policy User: arn:aws:iam::ID:root is not authorized to perform: support:DescribeSeverityLevels with an explicit deny in a service control policy You don't have the necessary IAM permissions to view that support case. Learn more Then under "Create case" the various case options are grayed out. Thanks!
1
answers
0
votes
8
views
AWS-User-3997924
asked 2 months ago

Data Transfer OUT Charges Through TGW in Another Account

Who is responsible for data transfer OUT charges when the transfer is originated by a VPC in one account, and that data passes through a Transit Gateway in another account on its way out through a Direct Connect (DX and TGW owned by the same account)? ***Details*** With the recent announcement on Direct Connect granular cost allocation (https://aws.amazon.com/about-aws/whats-new/2019/10/aws-direct-connect-aws-direct-connect-announces-the-support-for-granular-cost-allocation-and-removal-of-payer-id-restriction-for-direct-connect-gateway-association/), it is stated that we now "allocate Data Transfer Out charges to the AWS account responsible for the Data Transfer." I have a customer who acts as a transport service provider, and they own multiple DX connections that they plan to connect to Transit Gateways via a Transit VIF and DX-GW. The customers of my customer have VPCs in separate accounts that will be connected to my customer's TGW. With my customer owning the TGW, I am unclear on whether the cost allocation per the above announcement will consider the owner of the TGW responsible for the data transfer OUT, or whether that responsibility will be attributed to the owner of the VPC that originated the transfer. Also, if traffic routes through a firewall or IPS in Transit VPC owned by the DX an TGW owner on the way out of AWS, will that change the consideration of cost allocation?
1
answers
0
votes
5
views
AWS-User-5964206
asked 3 years ago
  • 1
  • 90 / page