Post by Rahul Kumar

AWS just killed one of the most annoying errors in cloud engineering. 𝗬𝗲𝘀… 𝘁𝗵𝗲 𝗶𝗻𝗳𝗮𝗺𝗼𝘂𝘀 “𝗕𝘂𝗰𝗸𝗲𝘁𝗔𝗹𝗿𝗲𝗮𝗱𝘆𝗘𝘅𝗶𝘀𝘁𝘀”. You choose a simple name like: 𝗰𝗼𝗺𝗽𝗮𝗻𝘆-𝗱𝗮𝘁𝗮-𝗽𝗿𝗼𝗱 …and AWS tells you it's already taken. Why? Because 𝗦𝟯 𝗯𝘂𝗰𝗸𝗲𝘁 𝗻𝗮𝗺𝗲𝘀 𝗵𝗮𝗱 𝘁𝗼 𝗯𝗲 𝗴𝗹𝗼𝗯𝗮𝗹𝗹𝘆 𝘂𝗻𝗶𝗾𝘂𝗲 𝗮𝗰𝗿𝗼𝘀𝘀 𝗔𝗟𝗟 𝗔𝗪𝗦 𝗮𝗰𝗰𝗼𝘂𝗻𝘁𝘀. Which forced teams to create bucket names like: 𝗰𝗼𝗺𝗽𝗮𝗻𝘆-𝗽𝗿𝗼𝗱-𝗱𝗮𝘁𝗮-𝟮𝟬𝟮𝟲-𝗳𝗶𝗻𝗮𝗹-𝘃𝟮 Not exactly elegant. But AWS just introduced 𝗔𝗰𝗰𝗼𝘂𝗻𝘁-𝗥𝗲𝗴𝗶𝗼𝗻𝗮𝗹 𝗡𝗮𝗺𝗲𝘀𝗽𝗮𝗰𝗲𝘀 𝗳𝗼𝗿 𝗦𝟯 𝗯𝘂𝗰𝗸𝗲𝘁𝘀. This means bucket names now live inside your AWS account namespace, not the entire internet. I wrote a 𝗾𝘂𝗶𝗰𝗸 𝗯𝗹𝗼𝗴 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗶𝗻𝗴 𝗵𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀, 𝗹𝗶𝗺𝗶𝘁𝗮𝘁𝗶𝗼𝗻𝘀, 𝗮𝗻𝗱 𝗵𝗼𝘄 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 𝗰𝗮𝗻 𝗲𝗻𝗳𝗼𝗿𝗰𝗲 𝗶𝘁 𝘂𝘀𝗶𝗻𝗴 𝗜𝗔𝗠 & 𝗦𝗖𝗣𝘀. Read the full blog here: https://lnkd.in/ghXjHnBb #AWS #AmazonS3 #CloudComputing #DevOps #AWSCommunityBuilders #PlatformEngineering Ajay Singh