Please enable JavaScript.
Coggle requires JavaScript to display documents.
Status (Migration (Website (Deployment Pipeline, Dockerize, Fargate),…
Status
Migration
-
-
-
Old accounts should not be touching the new, so new status needs to read S3 from the old accounts
-
-
-
Kibana / ElasticSearch
-
-
-
-
-
-
Answers
We don't want a Cognito Identity pool. That's for AWS resource permissions and our users have no need for an IAM temporary token. It can also be federated with Google Auth.
-
When you choose to send CloudWatch Logs direct to ElasticSearch it actually creates a Lambda in the background via a wizard. So regardless of the option chosen you are paying for a Lambda execution. We may as well do a custom one and then we can add in our own enrichment.
We possibly want to investigate a Rolling Index for ElasticSearch. Something like 24 hours per index, retained for up to X weeks.
Need to calculate how big a log entry can be and how large our index would need to be to handle it. We also need to calculate the Lambda execution costs.
-
-
-
-
Log database in DC2 has average rowsize of 700 bytes. Or 35k to 1 standard deviation. Maximum size is over 5MB.
108m requests per month a 1s lambda is $2,250 a month
Upgrades
-
-
-
Move PUEncryption into Conductor so we can use permissions to choose who has access to it. A CLI tool is not acceptable, support need to use it as well
-
-