AWS Certified Cloud Practitioner (CLF-C02) | Domain 4 Consolidated Billing, Data Transfer, and S3 Pricing Questions 05

As of August 22, 2026, an organization's management account is responsible for a member account's charges from the date that the account joins the organization. Responsibility does not apply retroactively, so the payer changes on August 15 in this scenario. Consolidated billing neither erases pre-join charges nor moves them to the next month.

As of August 22, 2026, consolidated billing can combine usage for eligible services such as S3 and apply the volume pricing tier reached by the organization as a whole. The benefit is allocated among accounts according to their usage. Because not every service or charge uses the same aggregation rule, the applicable service pricing terms must still be checked.

As of August 22, 2026, a Savings Plan under consolidated billing first applies to eligible usage in the account that owns the plan. If discount sharing is enabled, the remaining benefit can apply to eligible usage in other accounts in the organization. The order is not reversed merely because another account has more usage, and the benefit is not always divided equally.

As of August 22, 2026, Data Transfer In from the internet to AWS is generally free, while Data Transfer Out from AWS to the internet can be a major cost after the aggregated free allowance. The continuous delivery of processed images therefore deserves close attention in this estimate. Current terms for the specific service, Region, and path must also be checked.

As of August 22, 2026, EC2 data transfer over private IP addresses within the same Availability Zone is free, while transfer across Availability Zones in one Region can be charged. However, consolidating everything into one AZ reduces resilience to an AZ failure. The appropriate response is to reduce unnecessary chatty traffic while preserving the multi-AZ architecture required for availability.

As of August 22, 2026, direct data transfer between EC2 and S3 in the same Region can be free, but a path through a NAT Gateway can add separate processing charges. An S3 gateway endpoint removes the need for the NAT device and has no additional usage charge. S3 request and storage charges still apply separately.

As of August 22, 2026, S3 Standard-IA bills objects smaller than 128 KB as 128 KB. Deleting, overwriting, or transitioning an object before 30 days also incurs the remaining minimum storage duration charge, and data retrieval has a charge. Small, short-lived, frequently retrieved data might therefore deliver less savings than the storage rate per GB alone suggests.

As of August 22, 2026, S3 One Zone-IA stores data in one Availability Zone and costs less than Standard-IA, which stores data across multiple AZs. One Zone-IA is unsuitable for an irreplaceable sole copy because it is not resilient to the physical loss of an AZ. It fits this infrequently accessed secondary copy because the data can be recreated from another original.

As of August 22, 2026, S3 Intelligent-Tiering automatically optimizes data with unknown or changing access patterns and has no retrieval charge. Objects of 128 KB or more have a monitoring and automation charge, while smaller objects are not monitored or automatically tiered and remain in the Frequent Access tier. It does not immediately archive every object.

As of August 22, 2026, Bulk retrieval from S3 Glacier Flexible Retrieval usually takes 5–12 hours and has no data retrieval charge, matching both the 12-hour window and the cost priority. Other costs can still apply, including requests and temporary S3 Standard storage for the restored copy.