dseichter / vatservice Goto Github PK

Is your feature request related to a problem? Please describe.
If the service is deployed, we should have the possibility to monitor and alerted in any case, if something is going wrong.

Describe the solution you'd like

• Create Cloudwatch alarms based on specific numbers of errors
• Create Cloudwatch alarms based on step function execution results

Describe alternatives you've considered
Optional we can also provide a complete dashboard with all main metrics in Cloudwatch.

Additional context
This is a common issue, which should be probably specified more clearer based on all options we have.

Is your feature request related to a problem? Please describe.
If a request to one of our implemented services is not possible (e.g. maintenance of the systems), we should check, if there is an archived entry of the foreign vat. If there is an existing entry, we should respond this one.

Describe the solution you'd like
If response code of bzst, vies or hrmc is not 200, then do:

• if there is an entry in our table which is not too old (probably a configurable environment variable or within payload), we should load that value
• in the response, we should be able to identify, that we are currently provide an archived entry

Additional context
It depends on the company itself, if they can use an archived entry or if they need to check in real time.

In order to fullfil all necessary documents for my projects, there should be also a SECURITY.md document.

Is your feature request related to a problem? Please describe.
To improve the security of the API Gateway, we should have WAF enabled on the API Gateway.

Describe the solution you'd like
Every request should only by allowed, if the necessary payload is included. Additional (optional) rule should be added, if someone want to deploy it into a network, which makes IP whitelisting necessary.

Additional context
Enabling WAF should be an optional part, because of keep an eye on the costs, especially for test environments.

The first version of the readme contains some typos and some links are missing. We should refactor it.