When a new customer organization is created in Metworx and the first Organization Admin user is added, the user will receive an e-mail including login instructions to the e-mail address configured. Further steps assume that you have OrgAdmin credentials to your Metworx Organization AND Admin-level Credentials to your AWS account.
Once you are configured as OrgAdmin in Metworx, you will receive initial credentials via the e-mail address on record. Please login, reset your password, as required, and complete the steps below.
When you first log in, your Metworx dashboard will resemble the following:
Steps to Complete
1. Select network topology and configure a vpc and a subnet for metworx workflows
Metworx workflows can be setup to run in either Public or Private Subnets, depending on customer requirements. If metworx workflows are going to be setup in a private subnet, it is the customer's responsibility to establish a way for end users to connect to those workflows, typically though a VPN tunnel.
Each Metworx user can have their own ssh key in AWS to connect to their workflow. However, if a user or users DO NOT have a key configured, an organization-level key will be used instead. Only cloud- or metworx- administrators should have access to the organization-level ssh key.
In the customer's AWS account, there has to be an IAM service user, that Metworx applications use to connect to the customer-owned AWS account, and an IAM service role, that all of the ec2 instances assume when they run.
AWS IAM Service user api access and secret keys must be configured in Metworx Organizations by the customer Organization Administrator. MetrumRG does not have permissions to configure or view these keys.