Manish Batheja’s Post

Couple of weeks ago there was a huge storm on how AWS charged a user for unauthorized requests to his S3 bucket. 👉🏻The article : https://lnkd.in/dmw5MsxC 🌟Thanks to Jeff Barr and the team for addressing the issue and taking a quick action on the same : 🌟Amazon S3 will no longer charge for several HTTP error codes. https://lnkd.in/dGzSrHNd #AWS #cloudcomputing #S3

✈️ AWS Eliminates Charges for Unauthorized S3 Bucket Access Attempts AWS has addressed the long-pending issue of charging customers for unauthorized requests that result in HTTP 403 (Access Denied) errors in Amazon S3. Specifically, starting May 13, 2024, AWS will no longer charge for unauthorized requests that aren't initiated by the bucket owner, including those that return HTTP 403 errors when initiated from outside the bucket owner's individual AWS account or organisations. https://lnkd.in/dz-2mSvw #aws #longpending #s3 #403 #cost

🚀 𝗔𝗺𝗮𝘇𝗼𝗻 #S3 𝘄𝗶𝗹𝗹 𝗻𝗼𝘄 𝗺𝗮𝗸𝗲 𝘂𝗻𝗮𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗲𝗱 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 𝘄𝗶𝘁𝗵 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗲𝗿𝗿𝗼𝗿 𝗰𝗼𝗱𝗲𝘀 𝗳𝗿𝗲𝗲 𝗼𝗳 𝗰𝗵𝗮𝗿𝗴𝗲, covering a range of HTTP 3xx/4xx status codes. This change is rolling out across all AWS Regions over the next few weeks. Thanks to our customers for pointing this out and to our service teams for the swift implementation! Learn more here: https://lnkd.in/eRfKbfBd. 🔒 #AWS #CustomerObsessed #ZoKnowsSecurity

AWS listened! Amazon S3 will make a change so unauthorized requests that customers did not initiate are free of charge. With this change, bucket owners will never incur request or bandwidth charges for requests that return an HTTP 403 (Access Denied) error response if initiated from outside their individual AWS account or AWS Organization. To see the full list of error codes that are free of charge, visit Billing for Amazon S3 error responses. This billing change requires no changes to customer applications and applies to all S3 buckets. These billing changes will apply in all AWS Regions, including the AWS GovCloud Regions and the AWS China Regions. This deployment is starting today and we will post another update in a few weeks when it is completed. To learn more, visit Billing for Amazon S3 error responses and Error Responses in the S3 User Guide. #CustomerObsession https://lnkd.in/gBMZwb_9

"𝐀𝐦𝐚𝐳𝐨𝐧 𝐒3 𝐰𝐢𝐥𝐥 𝐧𝐨 𝐥𝐨𝐧𝐠𝐞𝐫 𝐜𝐡𝐚𝐫𝐠𝐞 𝐟𝐨𝐫 𝐔𝐧𝐚𝐮𝐭𝐡𝐨𝐫𝐢𝐳𝐞𝐝 (𝐇𝐓𝐓𝐏 403 𝐅𝐨𝐫𝐛𝐢𝐝𝐝𝐞𝐧) 𝐫𝐞𝐪𝐮𝐞𝐬𝐭𝐬" AWS has announced that they won't be charging for several HTTP error codes including 403 error code. Read more here 👉 https://lnkd.in/dBqwDbBZ To know the background and cause of this change and how this can be a big relief for customers using AWS S3 buckets, read the article by Maciej Poćwierz : https://lnkd.in/dbJRjczW #amazonwebservices #aws #s3 #security #devops #sre #errorcodes #reliability #ddos #billing

💥💥Important update from Amazon Web Services (AWS) Billing for Amazon S3 error responses On May 13, 2024, AWS started deploying a change to eliminate charges for unauthorized requests that aren't initiated by the bucket owner. After the deployment of this change is completed, bucket owners will never incur request or bandwidth charges for requests that return AccessDenied (HTTP 403 Forbidden) errors when these requests are initiated from outside of their individual AWS account or AWS organization. The current page shows a full list of HTTP 3XX and 4XX status codes that won't be billed. This billing change requires no updates to your applications and applies to all S3 buckets. When deployment of this change is completed in all AWS Regions, we’ll update our documentation.

When we say that AWS is customer obsessed. April 29th: a customer report a bad experience being charged for S3 API that e did not initiated and returned an access denied error. https://lnkd.in/dmYS7K4W The developer experience was really bad. The story has been picked by the press and relayed on multiple social networks. May 13th: Amazon S3 does not charge for HTTP 403 and some other errors anymore https://lnkd.in/dMexqmGm #aws #s3

🚀 Amazon S3 Billing Update 🚀 Great news for all Amazon S3 users! Unauthorized requests resulting in HTTP 403 (Access Denied) errors from outside your AWS account or organization will now be FREE. Previously, these unauthorized requests could lead to unexpected charges, causing unnecessary costs and billing headaches. This update ensures more predictable and fair billing, helping you save money and simplify your AWS experience. https://lnkd.in/dY4FkdSe #AWS #AmazonS3 #CloudStorage #TechUpdate

🚀 Exciting update for Amazon S3 users! Amazon S3 is now more cost-effective with changes to billing for certain HTTP error codes: - ✅ Billing still applies to successful requests (HTTP 200). - ❌ No charges for server error responses (HTTP 5XX). - 🚫 Specific HTTP 3XX and 4XX errors, especially those involving redirects or invalid requests, are no longer billed. - 🔒 AccessDenied errors (HTTP 403) are not charged if the request comes from outside your AWS account or organization. Check out more details here: https://lnkd.in/gZs3tCzh #AWS #AmazonS3 #CloudComputing #CostOptimization #AWSCommunity

Finally its here: