サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
衆院選
cloudonaut.io
AWS announced Kubernetes-as-a-Service at re:Invent in November 2017: Elastic Container Service for Kubernetes (EKS). Since yesterday, EKS is generally available. I discussed ECS vs. Kubernetes before EKS was a thing. Therefore, I’d like to take a second attempt and compare EKS with ECS. Before comparing the differences, let us start with what EKS and ECS have in common. Both solutions are managing
Stay up-to-date! We launched the cloudonaut blog in 2015. Since then, we have published 389 articles, 91 podcast episodes, and 99 videos. Our weekly newsletter keeps you up-to-date. Subscribe now!. Subscribe Our weekly newsletter keeps you up-to-date. Subscribe now! It's all free. I want to subscribe to the newsletter with new content as well as announcements regarding products and services. The n
The most reliable way to automate creating, updating, and deleting your cloud resources is to describe the target state of your infrastructure and use a tool to apply it to the current state of your infrastructure (see Understanding Infrastructure as Code). AWS CloudFormation and Terraform are the most valuable tools to implement Infrastructure as Code on AWS. I have worked with CloudFormation and
I was preparing some AWS Security related training. Soon, I realized that this topic is too huge to fit into my brain. So I structured my thoughts in a mind map1. Within a couple of minutes2 I came up with this: What is your first reaction? Mine was pretty much surprised: Let me summarize how AWS Security works to make sure you are not surprised one day. This post received over 200 points on Hacke
Stay up-to-date! We launched the cloudonaut blog in 2015. Since then, we have published 388 articles, 89 podcast episodes, and 97 videos. Our weekly newsletter keeps you up-to-date. Subscribe now!. Subscribe Our weekly newsletter keeps you up-to-date. Subscribe now! It's all free. I want to subscribe to the newsletter with new content as well as announcements regarding products and services. The n
The Gold Standard for modern cloud-native applications is a serverless architecture. AWS Lambda allows you to implement scalable and fault tolerant applications without the need of a single virtual machine. A serverless infrastructure based on AWS Lambda has two key benefits: You don’t need to manage a fleet of virtual machines anymore. Deploying new versions of your code can be entirely controlle
Since this year I’m working as an AWS Cloud Consultant where I see a lot of small to medium sized AWS deployments. Most of them are typical web applications. I want to share with you the 5 most common mistakes that you better avoid: managing infrastructure manually not using Auto Scaling Groups not analyzing metrics in CloudWatch ignoring Trusted Advisor underutilizing virtual machines If you are
Your AWS account is one of the most valuable things you own if you run a business on AWS. If you only own a single AWS account, you’re facing a serious security risk! The post will show you why this a problem and how you can solve it. This post received over 300 points and 100 comments on Hacker News. The risky default: a single AWS accountA single AWS account contains IAM users together with EC2
このページを最初にブックマークしてみませんか？
『cloudonaut.io』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
