...

• Anyone can create a Draft ticket in the Jira project.
• A Dev Team Representative (up to the team – for example the Dev Lead, PO, Scrum Master or QA Lead) can change status from Draft to Submitted.
  • The Dev Team Representative should be the person who will be available to answer questions.
  • Should be submitted at least two weeks before it’s needed.  Ideally four.
  • See required information.
• AWS Cost Review Group can change status from Submitted to Approved or Denied
  • See approval process.
• Dev team can change status from Approved to Active
  • See activation process.

AWS Environment Request: Required Information in

...

the Jira ticket

As with the New Module Evaluation Process, the onus us on development teams to fill out a template with required information, hopefully fixing any issues & addressing concerns before the request is actually submitted.  The benefit then to a team is that then the actual approval should be as easy & quick as possible.   The required information should be sufficient, but no more than necessary, to make that (easy, quick) decision.

...

• AWS Cost Review Group should request the dev team submit an updated request within two weeks.
• In the unlikely event that the Dev Team is unresponsive after that time period, the AWS Cost Review Group should escalate the issue to Community Council.  If ultimately necessary, the AWS Cost Review Group can then request that Kitfox shut down the environment.

Environments that Predate this Process

When the ACRG first forms, it should ask the dev teams responsible for existing environments to submit an Environment Request for each environment by the next Flower Release.

Shutting Down an Environment

...