# Resource / Hardware allocation

# General

For all new services, applications, etc. there MUST be a clear concept regarding deployment, observability, costs and reliability (e.g., impact of outage, backup strategy, Alerting, Data aging, etc.)

If you are planning to create or change* something which changes or needs new, or more resources in AWS you MUST involve Niclas Tocha into that concept and make an estimation about the needed resources before implementation.
If you are planning a new Service or want to use managed Services of AWS (RDS, SQS, SNS,...) you MUST inform Niclas before you use them. This is also true if you want to do a proof of concept.
You stay in charge of those resources, so if they are no longer needed you MUST inform Niclas Tocha that they will get removed.

If you are planning to create or change* something which changes or needs new, or more local resources you MUST involve Mario Gielsdorf into that concept and make an estimation about the needed resources before implementation.
You stay in charge of those resources, so if they are no longer needed you MUST inform Mario Gielsdorf that they will get removed.
Involve Niclas for architectural support

We will not keep Strato as additional data center, so no new resources or data MUST be implemented or shipped to Strato (March, 2021).

*Things like a significant change in the amount of data shipped or somehow stored to AWS (e.g., shop-updater, logs, S3) belongs to this.