top of page
The Big Data Blog
๐๐๐ฌ๐ฅ๐โ๐ฌ ๐๐ฎ๐๐๐ซ๐ง๐๐ญ๐๐ฌ ๐๐ข๐ฌ๐๐จ๐ง๐๐ข๐ ๐ฎ๐ซ๐๐ญ๐ข๐จ๐ง ๐๐๐ ๐ญ๐จ ๐๐ซ๐ฒ๐ฉ๐ญ๐จ๐ฃ๐๐๐ค๐ข๐ง๐ (2018) ๐จ
๐ ๏ธ ๐๐ก๐๐ญ ๐๐๐ฉ๐ฉ๐๐ง๐๐: In 2018, Tesla fell victim to a cryptojacking attack when hackers discovered an exposed Kubernetes dashboard within Tesla's AWS cloud infrastructure. The attackers gained unauthorized access and deployed cryptominers, secretly using Teslaโs cloud resources to mine cryptocurrency. โ ๏ธ ๐๐จ๐ฐ ๐๐ข๐ ๐๐ญ ๐๐๐ฉ๐ฉ๐๐ง? ๐ ๐๐ฎ๐๐ฅ๐ข๐๐ฅ๐ฒ ๐๐๐๐๐ฌ๐ฌ๐ข๐๐ฅ๐ ๐๐ฎ๐๐๐ซ๐ง๐๐ญ๐๐ฌ ๐๐๐ฌ๐ก๐๐จ๐๐ซ๐ โ The dashboard was left open to the internet with
Anna Kokhan
๐ฐ ๐๐๐๐ฎ๐๐๐ ๐๐๐ ๐3 ๐๐จ๐ฌ๐ญ๐ฌ ๐๐จ๐ซ ๐ ๐๐ก๐๐ญ ๐๐ฉ๐ฉ ๐๐ฒ $6,975 ๐ฉ๐๐ซ ๐๐๐๐ซ
We recently worked with a customer who was developing a chat application where users could share files stored in Amazon S3. During a cost review, we noticed that most files were rarely accessed after 30 days, but everything was still stored in S3 Standard, which costs $0.023 per GB. After discussing the usage patterns with the team, we implemented a lifecycle policy to automatically move files older than 30 days to S3 Glacier Instant Retrieval, priced at $0.004 per GB. ๐ Res
Jan 171 min read
ย
ย
ย
๐ ๐๐ง๐๐ซ๐๐ฌ๐ญ๐ซ๐ฎ๐๐ญ๐ฎ๐ซ๐ ๐๐จ๐๐๐ซ๐ง๐ข๐ณ๐๐ญ๐ข๐จ๐ง ๐๐ก๐๐ญ ๐๐๐ฅ๐ข๐ฏ๐๐ซ๐๐ $70,584 ๐ข๐ง ๐๐ง๐ง๐ฎ๐๐ฅ ๐๐๐ฏ๐ข๐ง๐ ๐ฌ
Today I want to share a real DevOps case where a planned migration turned into a serious cost optimization win. The initial request was straightforward: * Migrate applications from Docker Swarm to AWS EKS * Rearchitect the infrastructure for scalability and reliability * Move workloads to a new AWS region But instead of doing a โlift and shiftโ, we went deeper. What we actually delivered: * Clean and stable migration to AWS EKS * A redesigned architecture aligned with AWS and
Jan 171 min read
ย
ย
ย
Recent posts
bottom of page