The latest News and Information on Cloud monitoring, security and related technologies.
Mikk and the rest of the dev team at Dashbird have been working overtime this past month, in an effort to rehaul the user experience in the app based on the feedback we are constantly getting. We believe in having an honest and open, two-way street when it comes to communication so I advise each and every one of you to either write us an email via support@dashbird.io or to join our slack channel.
Lambda@Edge is a compute service that allows you to write JavaScript code that executes in any of the 150+ AWS edge locations making up the Amazon CloudFront content delivery network (CDN) service. In this post, I’ll provide some background on CDN technologies. I will also build out an application stack that serves country-specific content depending on where the user request originates from.
There’s no denying it — Kubernetes has become the de-facto industry standard for container orchestration. In 2018, AWS, Oracle, Microsoft, VMware and Pivotal all joined the CNCF as part of jumping on the Kubernetes bandwagon. This adoption by enterprise giants is coupled by a meteoric rise in usage and popularity. Yet despite all of this, the simple truth is that Kubernetes is hard.
The phrase “better safe than sorry” gets thrown around whenever people talk about monitoring or getting observability into your AWS resources but the truth is that you can’t sit around and wait until a problem arises, you need to proactively look for opportunities to improve your application in order to stay one step ahead of the competition.
FaaS services such as AWS Lambda take care of many security aspects - networking, firewall, OS updates, etc. Make no mistake, though: application-level security is still fully on our hands! Do we have all the information needed to secure our serverless apps? Enters critical logging!
When creating EBS snapshots, it’s important that the snapshots be “consistent”. This means that the data on the snapshot is whole and complete. An EBS snapshot can be considered “inconsistent” if not all data was flushed to the filesystem, and/or if an application running on the EC2 instance was mid-write when the EBS snapshot was initiated.
