A key concept to understand when migrating to AWS is the physical distribution of cloud resources. AWS organizes its global infrastructure into Regions and Availability Zones (AZ). An AZ consists of one or more discrete data centers within a Region. When you deploy resources in AWS you must define the Region those resources are deployed to and one or more AZs. AWS best practices encourage deployments to be spread across multiple AZs (Multi-AZ) instead of isolating them to a single AZ. Why is this recommended? Read to find out more.
Read MoreAn Application Load Balancer (ALB) may seem unnecessary when thinking about architecting Cognos on AWS. ALBs are most often used in serverless patterns or containerized applications. Those architectures obviously don’t apply to Cognos. However, that doesn’t mean we can’t borrow design patterns from other architectures to benefit a Cognos deployment. Two reasons we recommend leveraging an ALB when deploying Cognos are simplified administration and improving your security posture.
Read MoreDeploying Cognos on AWS immediately raises questions around the Cognos databases. What database type should we use? What service should we use to host them? Let’s dive in and hopefully, I can help you get a much clearer sense of what is best for your organization.
Read MoreAt PMsquare, we see more and more companies moving Cognos workloads to Amazon Web Services (AWS). The reasons for this move vary from company to company. There may be a desire to reduce architecture and administration costs, improve the reliability of the Cognos infrastructure, dissatisfaction with IBM’s SaaS offering, or the move to the cloud is being mandated by a larger company initiative. Whatever the reason, if you need to migrate Cognos to a public cloud you will likely have many questions and this blog series will answer them!
Read MoreTransitioning your company from traditional, on-prem architecture to a cloud native architecture can be a technically consuming project. Along with the technical shift in the way you think about your architecture, you also have to reposition your thinking around pricing and provisioning. Leveraging infrastructure as a service (IaaS) means you no longer need to buy a physical box and wait for it to be installed. You are now able to provision a new instance (sever) as easily as renting a movie from Apple TV or signing up for a Spotify subscription.
Read MorePlanning a migration, upgrade or new implementation of Cognos Analytics? One common question is Cognos server sizing--in other words, how many servers will you need and how "large" should they be (CPU, RAM, etc.)? While this is a somewhat complex question, we provide you a chart with a high-level estimate to use in the early stages of your planning.
Read More