AWS Amplify: AWS Amplify's Pay as you go overage rate keys were renamed (for example, standard_instance_build to build_standard_inst…

{"data_storage":"$0.023/GB/month","ssr_requests":"$0.30 per 1 million requests","data_transfer_out":"$0.15/GB served","large_instance_build":"$0.025/minute (16 GB Memory; 8 vCPUs)","ssr_request_duration":"$0.20 per GB-hour","xlarge_instance_build":"$0.10/minute (72 GB Memory; 36 vCPUs)","standard_instance_build":"$0.01/minute (8 GB Memory; 4 vCPUs)","web_application_firewall":"$15/month per Amplify app + WAF costs"} → {"data_storage":"$0.023/GB/month","ssr_requests":"$0.30 per 1M requests","data_transfer_out":"$0.15/GB","build_large_instance":"$0.025/minute (16 GB Memory; 8 vCPUs)","ssr_request_duration":"$0.20 per GB-hour","build_xlarge_instance":"$0.10/minute (72 GB Memory; 36 vCPUs)","build_standard_instance":"$0.01/minute (8 GB Memory; 4 vCPUs)","web_application_firewall":"$15/month per Amplify app + WAF costs"}

AWS Amplify's Pay as you go overage rate keys were renamed (for example, standard_instance_build to build_standard_instance) and data transfer out changed in wording from $0.15/GB served to $0.15/GB. All rates were unchanged, including $0.01/minute standard, $0.025/minute large, and $0.10/minute XLarge builds.