AWS EC2 P4d / P4de (NVIDIA A100 SXM4 40GB and 80GB)

per A100 GPU-hour. p4de.24xlarge = 8x A100 80GB, on-demand $27.44705/instance-hr / 8 = $3.4309 (us-east-1 and us-west-2 identical). p4d.24xlarge = 8x A100 40GB, on-demand $21.95764/8 = $2.7447, Capacity Block $11.8/8 = $1.475; p4de Capacity Block $17.712/8 = $2.214. Fetched 2026-10-03. PRICE CLASS: this is a PUBLISHED LIST PRICE - an asking rate a new customer is quoted, not a realised, discounted or negotiated transaction rate. A real bill is at or below this and typically well below it once commitments, credits and committed-use discounts are applied PERISHABLE-FIGURE STAMP (added 2026-10-04, uniform across data/supply/ so it is greppable). PRICE CLASS: PUBLISHED LIST PRICE - an asking rate a new customer is quoted, NOT a realised, discounted or negotiated transaction rate. A real bill is at or below this and typically well below it once commitments, credits and committed-use discounts apply. OBSERVED: 2026-10-03 RE-VERIFY BY: 2027-01-04 - the repo's quarterly re-verification bar. After that date this figure is presumed drifted and must be re-checked against its source before it is quoted again. A price without its observation date is noise; this stamp exists so a reader can tell a fresh figure from a stale one without reading prose. UNIT: per A100 GPU-hour READING RULE: No further perishable flag is published for this figure.

lead_time_weeks is null because the quantity is structurally not applicable: on-demand cloud capacity starts on request, so there is no order-to-delivery lead time. The constraint is the price per GPU-hour and the availability snapshot, not an interval. The one caveat worth keeping: scarce tiers gate capacity behind a reservation or Capacity Block commitment (AWS caps the booking horizon at 8 weeks, source spl-aws-capacity-block-booking-horizon), and that is a commitment window, not a lead time.

EAR 742.6(a)(6)(iii)(A) + EAR 744.23/744.6 (Entity, Unverified, MEU list screening of the end user) + the advanced-computing IaaS obligations of 91 FR 1684 (consignee KYC, and management/limitation of IaaS access to the hardware)

LAYER 1, EXPORT LICENCE: under the Jan 2026 BIS rule 91 FR 1684 (effective 2026-01-15) the license review policy for advanced-computing commodities with TPP < 21,000 AND total DRAM bandwidth < 6,500 GB/s - the NVIDIA H200 and AMD MI325X are the rule's named examples - moved from PRESUMPTION OF DENIAL to CASE-BY-CASE REVIEW, but only for exports FROM THE UNITED STATES to end users located in China or Macau, and only against six exporter certifications filed via SNAP-R before shipment: (1) items below the thresholds with the count of units shipped in the US; (2) sufficient US supply, judged 'taking into account normal lead times'; (3) no diversion of global foundry capacity away from US end users; (4) aggregate China+Macau shipments <= 50% of total US end-use shipments of that product; (5) no end-user or use prohibition; (6) the consignee runs rigorous KYC. Every shipment must then pass a qualified third-party testing lab - US-headquartered, not controlled by a D:5/Macau entity, no ownership stake in any party, qualification revocable by BIS at any time - verifying TPP, total DRAM bandwidth, interconnect bandwidth and copackaged DRAM capacity. Reexports and in-country transfers of the same chips to China/Macau REMAIN PRESUMPTION OF DENIAL. LAYER 2, END-USER AND PARENT SCREENING: per BIS guidance of 2026-05-31 a licence is required where the consignee is HEADQUARTERED in Country Group D:5 (15 CFR part 740 supplement no. 1) or Macau OR whose ULTIMATE PARENT COMPANY is so headquartered - even when the consignee itself sits outside D:5/Macau. The requirement sits at EAR 742.6(a)(6)(iii)(A) for destinations outside the US, with an exception available only under the license exception at 740.2(a)(9)(ii). The destination country alone therefore never answers the question; screen the parent. LAYER 3, REMAINING LIMITS: exports to D:5/Macau-headquartered OR -parented entities stay PRESUMPTION OF DENIAL wherever the buyer sits, and the AI Diffusion Rule that would have set a country-tier structure on who could lawfully buy what was RESCINDED on 2025-05-13 and is not being enforced, so any recorded status rests on the instruments named here rather than on tiering.

A100 remains the value entry point into AWS for anyone who does not need Hopper. p4d carries the $0.00 sentinel too, so treat on-demand p4d as allocation-only and buy the Capacity Block. The 2026-10-07 forward schedule LOWERS P4d Capacity Blocks to $1.696 per A100-hour and P4de to $2.546 - the one AWS accelerated SKU in this slice that is scheduled to get cheaper. P4 Capacity Blocks are offered in only three regions (n. Virginia, Ohio, Oregon), less regional choice than P5. Prices exclude the OS fee ($0 on Linux, $1.0368/instance-hr for RHEL on a 24xlarge) and all data egress. Note p4de is the 80GB part and p4d the 40GB part - different accelerators, not two sizes of one instance, so do not average them. EXPORT CONTROL (2026-10-04, mechanism-level; sources spl-bis-2026-05-d5-guidance, spl-bis-2026-01-advanced-computing-case-by-case): renting capacity does NOT remove the export-control question, it relocates it. Providing remote access to controlled computing capability can constitute a transfer under the EAR, so the provider must screen the end user; and separately, under the 91 FR 1684 licence regime the consignee must run KYC procedures to prevent unauthorized remote access and must manage and limit IaaS access to the hardware - obligations pushed onto the customer, who must be told to implement them. For a customer headquartered or parented in Country Group D:5 or Macau the 742.6(a)(6)(iii)(A) end-user/parent test can bite even when the capacity is consumed in a permitted region. Recorded true because the underlying hardware is controlled and the provider carries the screening duty, not because access to a US region is itself restricted. LEAD TIME: null, correctly so, and this instance family is the clearest case in the slice. p4d/p4de are the older A100-generation shapes and are listed on-demand, so capacity is allocated per request and there is no wait to quote - the binding constraint for these shapes is instance AVAILABILITY in the region, not a build or ship interval. Recorded on this record rather than invented. The one AWS family that does publish a commitment horizon is Capacity Blocks, whose 8-week MAXIMUM booking horizon is documented (source spl-aws-capacity-block-booking-horizon) and is recorded on rent-aws-ec2-gpu-hourly-2026-10-04, where the Capacity Block prices already live; that 8 weeks is a ceiling on how far ahead you may commit scarce capacity, not a delivery time, and it does not apply to the on-demand rates on this record. Probe log in source spl-negative-no-oem-publishes-lead-time.