City of Gold Coast, Australia’s second largest local government, is becoming an active digital city.[Read more…]
Idea 11 is honoured and humbled to again achieve industry recognition through placing in Australia-wide growth awards in 2018.
Today we’ll look at handling application settings in build and deployment pipelines.
An application normally has several settings that are stored outside of main application codebase. Database Connection strings, external SaaS API Keys, credentials are examples of settings and other environment specific settings will be stored in appsettings.json for a DotNetCore app, web.xml for a Java app, or settings.yml for Ruby.
If you have hardcoded connection strings or parameters inside your application, it is highly recommended to extract these out to a file so that you can easily update these without having to store sensitive information inside the source code and stored as part of your version control repository.
AWS SSM Parameter Store (AWS Systems Manager Parameter Store) is a service and it’s importance should not be underestimated. It provides secure, hierarchical storage for configuration data management and secrets management. You can store data such as passwords, database strings, and license codes as parameter values.
Amazon CloudFront is a Global Content Distribution Network. Essentially, this is a global caching system that delivers your website and app content really fast and low latency to your end users.
This is one of my favourite AWS services because you can increase the responsiveness, resiliency and scalability with minimal effort or cost – without even re-configuring your web servers!
Today, I’ll show you how to leverage some of the advanced protection functionality that is available within CloudFront.
Apache and Nginx are two of the most popular web servers in the open source community. between them, they are responsible for serving over half of the traffic on the internet. Both services have Pros and Cons that need to be taken into account when working out which solution to implement. This article explains how you can use apache2buddy to help tune your Apache2 installation when your dealing with large web applications or large volumes of traffic.
I’m pleased to announce that Idea 11 is one of the first Public Cloud Specialised partners for Palo Alto Networks in Australia, and the first in Queensland.
Meeting the requirements of this designation demonstrates our commitment to delivering Palo Alto Networks solutions on the AWS platform, and we’re excited to share this designation of our capability and experience.
Here at Idea 11 we work with our customers to deploy Amazon WorkSpaces. A lot of WorkSpaces.
In an enterprise, one annoying aspect of the client is the Registration Code. This code is used to tell the WorkSpace client where to connect.
Now obviously just telling the end users to enter this code isn’t the most seamless user experience we could want and usually results in a few helpdesk calls.
So this is how you can configure this code automatically for your end users.
What a year 2017 was. In addition to our AWS Rising Star Partner of the Year award, we were honoured to receive additional awards placings – the Australian Financial Review Fast 100, CRN Fast 50 and Deloitte APAC Fast 500.
Each of these awards is measured differently, but all are based on business growth. The AFR Fast 100 (formerly known as the BRW Fast 100) is measured on three year average growth rate, the CRN Fast 50 is measured on single year growth rate, and the Deloitte APAC Fast 500 is three year cumulative growth rate.
We’re ecstatic to be recognised publicly for what we’re doing. Ultimately, this is a byproduct of what we aim to do – excellent work for our customers, every day.
What is Amazon AppStream 2.0?
Appstream 2.0 is Amazon Web Services’ latest fully managed service that allows anyone to securely stream windows applications directly to a compatible HTML5 web browser. Previously only available in limited regions world-wide, it’s now available for deployment in Sydney.
What problems does AppStream solve?
You’re a software vendor:
- You’re a software vendor wanting to break into the Software-as-a-Service landscape, but have a heavy GUI client based application. SaaS apps where primary delivery is by Windows Forms or some other technology that is not able to be delivered via web browser. Reduce time to market rather than re-writing your software to be web browser friendly.
- Simplify environment management to just your application rather than the complete operating environment.
- Looking for an additional revenue stream hosting your application, instead of having customers install in their own environments.
AWS Cognito is a fantastic product that handles everything to do with your app’s users, so you don’t have to. You don’t have to think about authentication, user profiles, user management, or ensuring that passwords are handled properly. AWS Cognito also handles federation with other systems.
I was asked a question recently;
I’ve used the Serverless framework to create a small app to support internal business functions. It’s a private application and we’re using AWS Cognito to secure it, but we need to use our Office365 logins. Is it possible to set this up?
In this post, we look at implementing AWS Cognito with federation against Office365. I’m assuming that you are already using API Gateway, AWS Lambda and AWS Cognito to provide login functionality. It’s not immediately obvious to federate Cognito with Office365, so I thought it would be good to put together a short tutorial.
Let’s get started!