Skip to content

Adding support for new AWS accounts regions

Jump to bottom
Satish Malireddi edited this page Jun 13, 2019 · 1 revision

Overview

Jazz admins can now add support for new AWS accounts/regions to an existing Jazz stack. Developers can choose a specific account/region from a list of supported values to deploy their service. This will help developers to design & deploy multi-region highly available serverless applications through Jazz. Developers can reduce latency by deploying their serverless applications closer to other dependent services in a specific region or account.

Setup: Adding new Accounts & Regions

Follow the instructions here to install the multi account/region extension to an existing Jazz stack to complete the required setup. You will be using an automated installer that will provision various AWS resources in the new account/region & update few resources in the primary account where Jazz is installed.

Developer experience

Jazz is built on the fundamentals of abstracting complexity from the developers. When Jazz admins add support for new accounts/regions into the environment, developers would just choose them as their deployment target accounts/regions without worrying about any of the underlying complexity. All the Jazz features - CI/CD, logs, metrics, environments, security - all work automagically out of box!

Deep Dive

The automated installer creates required AWS resources like basic IAM roles, API Gateways, CloudFront resources, S3 buckets etc. in the new account/region. Secrets are stored in the credential store and configurations are updated in config store (database).

  • Service Deployment: Let's take a service that got created using one of the newly added account/region as its deployment account/region. During its deployment, Jazz CI/CD component retrieves credentials & the platform configurations for this target account/region and completes the deployment process.

    deployment

  • Metrics: Jazz metrics API uses a platform role to retrieve metrics from the account/region where a service is deployed. During the account/region setup, this platform role will get all the required permissions to retrieve metrics from the target account/region.

    metrics

  • Logs: Service (function) logs are streamed from every account/region using AWS Log Destinations. Complete documentation on this setup is described here. Jazz leverages a centralized Kinesis stream to collect logs for further processing.

    logs

Create! Manage! Self-service!

Clone this wiki locally