Our Physical Asset Manager, PAM, was created to simplify and streamline the management of digital and physical wayfinding signage systems. Asset implementation programs typically use a variety of channels to communicate information.
To be effective, each of these must be cross-referenced to ensure validity. PAM streamlines this into a simple, consolidated view for organisations with multiple sites and large visitor numbers, complex signage types and multiple wayfinding needs.
Mediabank PAM enables consistent and easy management through the entire lifecycle of the sign, including warranty end-of-life management. Facilities Managers get a highly user friendly administration experience, with less frustration and a huge increase in productivity.
To scale and grow the business into new markets overseas.
New cloud formation templates deployed into VPC that could be replicated across multiple Availability Zones
Clustered systems running across multiple availability zones. Scalability and availability that was just not previously possible to reach new markets.
Post Implementation review with Simon Morgan – Head of Development at Mediabank PAM
What were some pain points being experienced that prompted a search for a cloud services provider?
We needed to move from our current local Sydney provider to AWS for better monitoring, scaling and entering the US market.
Our reliance on their service was a limitation to allow us to grow the business into new markets overseas where we needed to have a local data presence.
What was the engagement process like? How was PolarSeven found?
I had been to some of the AWS Meetups in Sydney and met Darrell (PolarSeven CEO) there. We had several conversations and moved from there to a formal engagement.
What due diligence process was undertaken to minimise risk and ensure the best provider was successfully engaged?
PolarSeven have hosted the Meetup for a long time which showed me that they were a serious face in the Cloud Service Consultancy and Darrell was a good public face of the organisation.
Technical qualification was established through our early discussions with an initial workshop with some of the team members which showed that they could understand our requirements and gave confidence to us in their ability to deliver.
What solution was implemented within the business?
We collaboratively developed Cloud Formation templates that could be supported in the long term by PolarSeven.
By using some of PolarSevens existing templates and some of Mediabanks previous work we created a custom template for Mediabank.
This was part of the reason why we liked PolarSeven because of their readiness to work in a collaborative fashion.
The following diagram outlines the environment to be deployed on AWS for MediabankPAM production environment.
The deployment architecture will leverage several AWS services for building the virtual private cloud (VPC) across multiple availability zones (AZ) for availability and redundancy. The AWS services and their relevance to the current scope are listed in this section.
The following AWS services were utilised while implementing this solution.
- VPC – Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define.
- AZ – Regions are separate geographic areas within them are AZ’s which are isolated locations. We deploy infrastructure across multiple AZ’s to ensure high availability (HA) for high value stacks and redundancy for others.
- Route53 – Mediabank.com.au domain hosted on route53 for ease of management.
- Auto Scaling – Auto Scaling helps you maintain application availability and allows you to scale your Amazon EC2 capacity up or down automatically according to conditions you define.
- SNS – Amazon Simple Notification Service (Amazon SNS) is a fast, flexible, fully managed push messaging service
- S3 – Amazon Simple Storage Service (Amazon S3), provides developers and IT teams with secure, durable, highly-scalable object storage.
- EC2 – Amazon Elastic Computer (Amazon EC2), provides computing resources that user need to run applications.
- RDS – Amazon Relational Database Service (Amazon RDS), is the SQL database service supporting SQL Server, Oracle, PostgreSQL, MySQL and MariaDB
- CloudWatch – Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications you run on AWS.
- CloudTrail – Enabling CloudTrail will provide audit capability and accountability for all actions on the environment.
- NAT – Network Address Translation instance is required within a VPC to enable instance on a private subnet to access the internet. The NAT is deployed in an autoscaling group of one to provide redundancy and availability.
- VPN – Virtual Private Network device will enable secure and controlled access to the environment for development and admin purposes.
The design of the scripts and template has allowed the VPC to be created in different regions. Multiple VPCs can be created within the same region, with the option of prod or non-prod.
Prod/non-prod configuration varies in instance type, RDS Multi-AZ support, NAT gateway, and the number of AZs. Basically non-prod VPCs are provisioned with reduced resources and availabilities.
What specifications needed to be adhered to?
We had some Business and some Technical Requirements that needed to be adhered to.
For the business we required reliable and secure cloud services with high availability and auto scaling. This is essential to the company’s future growth along with the ability to deploy into other regions so we can deal with clients requiring their data stored in their local country, i.e. if we were to get an airport in the U.S for example we need to be able to manage their data in country.
We also needed visibility and transparency to ensure that the environment is understood by all parties and well documented.
Backup and Disaster Recovery are of course a must for any business and flexibility and agility to give us the ability to release new feature requests quickly and reliably
On the Technical Requirements we had to deploy a secure Virtual Private Cloud (VPC) environment and have a repeatable and extensible process for building an application stack.
We needed to follow AWS Architecture best practices to make it highly secure and make sure that everything was well documented.
We used a Devops approach where all infrastructure is managed as code in a source code management repository with end to end scripting.
What were some of the alternative options proposed, that were not undertaken and why?
We knew that AWS was the clear choice for us. As the market leader and especially with the size and scale available globally it was a clear choice for us.
There was simply no way that we could scale the business using our local provider and other cloud services did not offer the same scale and service as AWS.
How would you describe the project in terms of success? Was business value realised?
Yes. Our reasons for moving into the AWS environment were very clear to us as a business that we needed to be able to scale and open to other markets, such as the US.
This simply wasn’t possible with our previous private cloud provider and hampered business growth.
What were some KPIs used to measure the success of the project?
Our operating cost is similar to our previous private cloud provider but we now have clustered systems running across multiple data centres with High Availability that was not possible with the old configuration.
We also have not experienced any outages or downtime since transition.
We have removed dependencies from the previous data centre with use of cloud formation which allows a high degree of transparency of configuration and change management.
The ability to re-launch into new zones with purpose built stacks quickly and effectively has made our development easier and faster to deploy.
Were there any unexpected benefits that arose once the project had been completed?
No real unexpected benefits as we knew what we were looking for but it has made it possible for us to scale and have access to advanced AWS capabilities that weren’t possible through the old DC centre.
Do you see yourselves expanding to utilise more AWS services into the future?
Yes, definitely. We will be looking at moving to a serverless architecture using Lambda in the future.
How did you rate your experience with PolarSeven?
Excellent, good collaboration and very flexible to work with. A good team effort and backup for the person on site from the broader PolarSeven team when required.
This showed through with great technical depth across the team.
Would you use PolarSeven again?
Would you recommend PolarSeven to others?
Yes, I certainly will..