This week's roundup of all the cloud news.
Auto-scaling is the capability built into AWS that allows you to ensure you have the right number of EC2 instances provisioned to handle the load of your application. Using Auto-scaling, you can remove the guess work in selecting how many EC2 instances are required to provide an acceptable level of performance for your application without over-provisioning resources and incurring unnecessary costs.
If you are using AWS to build solutions that consist of more than a handful of resources you will appreciate the need for accurate AWS VPC Diagrams. The best form of documentation to be able to easily communicate how your AWS network is constructed is a network topology diagram.
If you are using AWS to build solutions that consist of more than a handful of resources you will appreciate the need for accurate network documentation. By far, the best form of documentation to be able to easily communicate how your AWS network is constructed is a network topology diagram.
When you are working with Azure cloud computing infrastructure, there are many benefits to creating and maintaining accurate Microsoft Azure diagrams.
You can effectively communicate your Azure network design to both technical engineering staff and also management where necessary. If you are onboarding new engineers, or engaging external consultants, you can bring them up to speed very quickly with a well laid out infrastructure diagram.
If you are taking on a new client or project, having access to infrastructure documentation is a massive advantage when trying to understand exactly what is running where. Back in our cloud consulting days, diagramming a new client's infrastructure was always the first job in the induction process. It was often time consuming, laborious but necessary in establishing exactly what was going on prior to starting work on improving or redesigning infrastructure.
There are numerous reasons why you would want to accurately diagram and document your AWS environments. Knowing exactly what is running based on the actual resources configured in your cloud environments is probably the number one reason to use an automated Cloud Architecture Diagram Tool over manually drawing your network topology diagrams.
If you are developing on AWS or any other platform for that matter, you will understand the need for good version control. Git repositories have for a long time been an effective method of controlling software versions, enabling multiple developers to work on the same code base without overwriting each other’s code and providing the opportunity to roll back code in the event of a release introducing unforeseen behaviours, or bugs as they are more commonly referred to.
AWS Fargate is a service that provisions serverless compute resources to run AWS ECS and EKS containers. AWS states that Fargate allows you to focus on building your applications when you let Fargate provision and manage the infrastructure required. Think of it as containers on-demand with no underlying manually created infrastructure that are quick to launch and scale, where you manage everything at the container level.
When you are working with AWS cloud infrastructure, accurate network topology diagrams play a major part in monitoring and internally communicating the design of your AWS infrastructure.
Being able to visualise all of your AWS components and resources in diagram form assists in understanding what is running where and also helps experienced engineers spot vulnerabilities and redundancy issues in network design.
AWS Lambda is a service that allows you to run code and containers without the need to set up, manage or provision servers. Lambda runs your code on highly available compute cloud infrastructure via Functions. Lambda takes care of server and OS maintenance, scaling, code monitoring and activity/error logging.
This month AWS announced the release of App Runner which is a fully managed container-native service designed to make it easier for developers to quickly deploy APIs, micro-services, and web applications using source code repositories and container images.
When you are working with any cloud computing virtual infrastructure, there are many benefits to creating and maintaining accurate Azure Architecture diagram sets.
You can immediately communicate the network design to both technical engineering staff and also management where necessary. If you are onboarding new engineers, or engaging external consultants, you can bring them up to speed very quickly with a well laid out infrastructure diagram.
When you are monitoring your AWS infrastructure for security alerts, not all security signals can be remediated automatically. Large or complex environments can generate multiple security flags (repeatedly) that need to be manually investigated in detail. This requires access to sometimes complex metadata to thoroughly investigate which may place a strain on your in-house security skills or may even require you to find the budget for a dedicated security expert.
In this Post we will look at a high level overview of all the different AWS container services you can use on AWS. If you want to run a containerized application on AWS you have multiple options to choose from depending on your application requirements, AWS Security and orchestration software preferences.
If you have worked with Microsoft Azure for any length of time, you no doubt appreciate the value and necessity of great network topology diagrams. Diagrams provide a visual cue for better communication and understanding of your cloud infrastructure at all levels of your organisation, from management down to freshly onboarded engineers and consultants.
Along side the hundreds of AWS resources we recently detailed in this AWS Services List, Amazon also provides a stack of developer and DevOps tools to help you build, deploy, manage and monitor applications on the AWS cloud.
This is a list of a few of our favourite AWS Developer Tools.
There are many reasons why you would want to accurately diagram and document your AWS environments. Knowing exactly what is running based on the actual resources configured in your AWS environments is probably the number one reason to use automated AWS Infrastructure Diagram software over manually drawn diagrams.
AWS is one of three major cloud platforms that Hava generates automated cloud diagrams for. AWS offers a host of services that fall under several major service categories. In this post we'll take a look at the services available for you to build, manage and monitor applications on the AWS cloud platform.
There are so many reasons why you should accurately document your AWS cloud environments with Network Topology Diagrams. They visually portray how your network is constructed, what is running where and how resources are grouped and connected.
This is a major time saver when explaining your network to new engineers, consultants or other internal stakeholders.
Google Cloud recommend your network resources should be organized hierarchically to enable you to manage access control and permissions across your organization. Grouping together all the network resources that each team or project requires makes it easier to permit or deny access according to which business unit each team member belongs.
Continuing on a stellar trajectory and partly enhanced by the pandemic, the adoption of cloud infrastructure and services is expected to top $120Bn in 2021 increasing by well over 35% according to Forrester Research. Welcome to the new normal.
When you are responsible for the delivery and maintenance of critical or complex applications built on cloud infrastructure, the chances are you are relying on multiple in house engineers or teams of engineers, devops and external consultants to keep your network and applications operating at peak performance for your end users.
When you are working with Microsoft Azure, there is no doubt you appreciate the value and necessity of great network topology diagrams. Diagrams provide a visual cue for better communication and understanding of your cloud infrastructure at all levels of your organisation, from management down to freshly onboarded engineers and consultants.
When moving your data and applications to AWS or developing a solution from scratch, you are most likely going to be faced with the challenge of selecting the most appropriate of the multitude of database options offered by AWS.
If you used Arcentry in the past to document your cloud infrastructure, the closure of the service earlier this year probably came as a bit of a shock.
While quite a newcomer having only been established in 2018, the decision to shut the doors at short notice potentially left a lot of people high and dry that were using the service to diagram their cloud infrastructure.
Tags are an incredibly useful yet often overlooked feature of most cloud computing platforms. Once created they let you manage your infrastructure more effectively by providing the ability to filter resources and perform tasks and actions based on nominated tag values.
The best and most perfect cloud architecture is next to useless if no one in your organisation understands it. What maybe even worse is if everyone misunderstands it, which is why we believe accurate documentation is an essential step in network architecture design and implementation.
With the availability of multiple cloud platforms each with their own strengths and cost advantages, it is not uncommon for DevOps engineers and cloud architects to take advantage of resources from multiple cloud vendors when designing a cloud based application.
We're happy to announce general availability of the new hava.io user interface. The result of many many hours of performance tweaks and design improvements this implementation of the cleaner UI has delivered improved navigation, more screen area for your diagrams so you can focus on the things that matter to you.
We are pleased to announce the general availability of Compliance Reporting as an addition to our AWS diagram tools. Hava's new reporting module centred around the AWS trusted advisor / well architected methodology is available on selected subscription plans and self hosted enterprise solutions.
There are countless reasons why you would want to accurately document your AWS environments. Knowing exactly what is running based on the actual resources configured in your AWS environments is probably the number one reason to use automated AWS Diagram Software over manually drawn diagrams.
If your systems or applications process electronic payments or store client payment and transaction data, then PCI compliance should be a high priority for your business.
There's no question that having industry certifications under your belt is one of the best ways to advance your cloud computing career. It's also a great way to help you break into the industry if you are contemplating a career change or looking to show value to a potential employer.
If you are looking for something interesting to fill your earbuds in 2020, here's a list of 50 podcasts worth a listen.
Mostly focused on Cloud Platforms, DevOps and Security there is sure to be something in there that resonates with you.
We’ve all heard the cliche “A picture paints a thousand words”, but there is real value in using images to explain complex technical information.
Amazon Web Services (AWS) have launched a re-designed set of diagram icons, the first version release was for AWS re:invent 2018, with the official public release on the 2nd of February 2019. Hava now supports diagrams using the new icon set, so you can discover, diagram, diagnose, and document your environments straight from the source of truth with a familiar style.
Cloudcraft is known for their isometric AWS diagrams and often one of the tools used to depict the layout of your cloud environments, along with Lucidchart and Draw.io. We all need to start somewhere with our network diagrams, whether it's on a whiteboard, in a drawing tool or in a drag and drop builder.
Canalys estimates cloud infrastructure services spend reached US$20 billion in Q2 2018. The top three cloud providers account for 57% market share.
AWS security groups act as a virtual firewall for your EC2 instances to control inbound and outbound traffic.
"Security groups act at the instance level, not the subnet level. Therefore, each instance in a subnet in your VPC could be assigned to a different set of security groups." - AWS Documentation
Trawling through your VPC flow logs helps provide visibility into your network traffic to detect anomalous traffic and provides insights, however, it still comes with its own risk of error.
Generating a visual diagram from the source of truth with automated layouts to display your network infrastructure as it is right now can eliminate the potential risk of human error.
Hava offers several ways to assist with diagnosing security within your network.
There is no doubt that as we continue to move further into cloud networking and infrastructure our environments are evolving daily. This rapid pace of change is failing to keep up with the expectation that your team knows "how it works" and "what it looks like". Keeping network diagrams up to date is often the last thing on most engineers mind, until the time you need them which in some cases is too late.
Manual creation and updating of diagrams are tedious and time-consuming and not that effective with continuous change. These days we have the ability to automate the process of generating and drawing a diagram, getting the information straight from the source of truth.
So you’ve got approval to hire a consultant on a six-month contract to fast track your project. You’ve found the perfect consultancy with proven success in everything you need to implement. Your Scope of Work (SOW) has been signed off on and your consultant starts in a week. Hoorah!
You want the project to be a resounding success, right?
Onboarding your cloud consultant properly is the most critical thing to you can do to maximize your ROI. They have limited time to deliver you results, not being prepared means your consultant sits idle, and that costs you money which can significant with the increased level of cloud spend in the IT landscape.
Sydney’s wild weather brought down an availability zone in AWS’s AP-SOUTHEAST-2 Region on Sunday night.
Websites went down, customer service calls went up, twitter went nuts, engineers scrambled to find work arounds and management started asking “Why?”.
If your website crashed, you know by now that it’s probably because your application wasn’t designed for region failure.
One outage should not be reason for you to start thinking that the cloud isn’t right for you, or that you should move service providers. But it should make you revisit your architecture.
Failure in cloud services is inevitable regardless of your provider. Outages happen so you must design for failure. Your actual infrastructure availability is irrelevant to your application availability. 100% uptime should be achievable even when your cloud provider has an outage regardless of its size.
AWS has invited Hava to be part of the AWS Startup Pavilion on Day 1 of the AWS Sydney Summit. Having attended AWS Summits and conferences for years, it’s exciting to be on the other side demoing Hava.
If you're registered for Summit, we'll be at the Startup Pavilion on Wednesday so come over and say hello. We’d love to step you through Hava and show you how we can save you time and headaches visualizing your AWS cloud infrastructure clearly.
How are you currently creating your cloud diagrams? Are you spending quality time with your whiteboard hand drawing them? Or are you trolling through your AWS console, then clicking and dragging in a drawing tool?
Imagine being able to extract real-time diagrams of your actual AWS environments. That would be pretty cool, right?
Well that’s exactly what Hava does!
With DevOps now firmly placed in the enterprise sights, we are seeing that automation visibility is becoming critical. Having the view of the state of the delivery pipeline ensures there is an increased awareness of the system as a whole. The question that often arises is “Yes, we need monitoring, but what do we monitor?” There are numbers components of your environments that you should be monitoring, and this blog explores what they are, how to track changes in your cloud environment and why it’s important to monitor them.