System administration is a special are of IT. It also has a special place in my heart. It is an interesting mixture of all the other disciplines, both common across the whole industry, and at the same time unique for each person, company, and geographical location. When I have something to say or share about system administration, I use this category.
“How we designed our Kubernetes infrastructure on AWS” is a case study of how Atlassian (the kind people behind BitBucket, HipChat, Jira, and a few other popular tools) setup their infrastructure on Amazon AWS.
With all the popularity of the cloud in general and AWS in particular, there is still not enough articles like this one.
For those unaware, Oracle laid off ~ all Solaris tech staff yesterday in a classic silent EOL of the product. https://t.co/ibs2REGRmj
— Simon Phipps (@webmink) September 2, 2017
AWS Blog lets us know that Amazon has finally implemented one of the most useful features ever – descriptions on Security Groups rules. Â Previously, one could provide a description to the Security Group only, for example: “Proxy Server Access”. Â Which wasn’t very useful, as it was almost obvious. Â But now one can add a description to every rule inside the Security Group. Â So when you have a Security Group with a bunch of IP address ranges, you can now describe each one of them. Â For example: “HQ Office”, “UK Office”, “Boss At Home”, etc.
If you read Russian, have a look at this article as well, which is somewhat based on the above slides.
BitBucket blog announces the support for scheduled Bitbucket Pipelines. Â This is super cool and has been on the wishlist for a while now. Â Here are a few examples of how this feature is useful:
- Nightly builds that take longer to run
- Daily or weekly deployments to a test environment
- Data validation and backups
- Load tests and tracking performance over time
- Jobs and tasks that aren’t coupled to code changes