Jazz Installer Versions Save

Support for new AWS Lambda runtimes & ECS Fargate hosted components now use EFS for shared storage =>

-- Support latest runtimes: for Node12, Python3.8, Java11 & Go1.1 -- Using persistent, shared storage for core components deployed in ECS Fargate like Gitlab, Jenkins, Sonarqube -- Upgraded Jenkins to v2.164.1

• Secret Management using T-Vault => Developers can now use T-Vault, a simplified secrets management solution using Hashicorp Vault, to store/consume/manage secrets required for their applications. Each environment within a service gets its own secret store & functions deployed within the environment are configured to have required permissions to the access the secrets. No more storing secrets in the code, Happy Safe Coding!

• Node10 runtime support & other bug fixes => -- Added support for node10 -- Bug fix related to log destination policy updates -- Upgrade Jazz core services to use node10 -- Use new naming convention for functions -- Handle ENI issue during cleanup which was documented here

• Elastic search upgrade & containerized setup with the initial stack install => Jazz provisions managed Elastic search (ES) service for log storage by default. Since it needs dedicated EC2 instances provisioned & up all the time, it contributes to majority of the stack cost for simple trial environments. With this release, ES is upgraded to version 6.5 & provisioned as a container in AWS Fargate service along with other always-on services like Gitlab and Jenkins. This should bring down the total cost of the trial Jazz environment by a significant chunk. Post setup, Admins are free to replace it with enterprise grade ES service of their choice by simply updating the centralized Jazz configurations.

• Azure Support => Developers can now select Azure as the deployment target for their services! Developers can make this selection during service creation. Jazz creates required code templates and makes them available for developers to add their business logic & deploy their serverless services to Azure cloud platform in minutes! This feature will be supported as an extension. Jazz admins can apply the extension to an existing Jazz environment and can configure the details like Subscription Id, credentials etc. If required, they can also enable/disable the option for users. AWS will continue to be the primary/default deployment target.

• Additional Bug fixes

• Native support for serverless application templates => With this feature, Jazz supports cloud-native applications created using serverless framework! Existing Jazz templates (api, function & website) will continue to work. Developers can define their applications using serverless framework using deployment descriptors - serverless.yml in their code or Jazz UI during creation or after the service is created. Developers can view assets/metrics/logs/deployments related to the service all at one place! This will allow developers to create serverless applications that contain any of the serverless offerings from AWS that serverless framework supports!

• Extensions are updated to use python3

• Multi account/region support => Current Jazz gets installed in the default AWS account and region. This feature enables Jazz to connect to AWS resources in other accounts/regions. Jazz admin can configure new additional accounts/regions in an existing Jazz environment through an automated extension installer. Users of Jazz will be able to select specific account/region where they would like to deploy their services. You can read this to learn how to enable this feature!

• More bug fixes

• Moving to Python3 => Rewrote installer wizard and shell scripts in python3 & implemented CLI installer using Click.

• Hosting Jazz components (ECS) within a VPC & avoid the default public access => Jazz components including Gitlab, Jenkins, SonarQube & Elasticsearch are provisioned within a VPC for added security. With this change, Jazz admins can restrict the access to these components to a specific IP range.

• Manage ACL for Jazz services => Current version of Jazz works in a single developer mode where the service creator/owner has full access to their service with no provision to share access within the team. This feature will expand the scope of using Jazz in a collaborative team/application/product setup. Read wiki for more details!

• Apigee Support => Support Apigee as one of the deployment targets for APIs. Developers can now choose Apigee as their API deployment target for serverless functions (AWS Lambda)
• Bug fixes