Оффлайн
- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
Started a Bluesky on my personal AWS to learn more about AT and decentralised protocols but also to experiment in managing AWS workloads using multiple services.
So far using Route 53, Certification Manager, EC2 (Graviton t4g.micro instance family and size), simples IPv4 and IPv6 VPC (Bluesky do not support IPv6 at this time), EBS and Snapshot (manual for now), CloudWatch Log and metrics from CloudWatch Agent.
Next short term ideas are are a simple AWS Backup lifecycle job, test moving /pds folder to an EFS share, enable CMS KMS for the service, check if project tags are consistent for proper workload spense tracking and connect PDS to SES for email verification and password resets.
Medium term ideas are writing IaC to build the whole infra by automation, perhaps move into a CodePipeline pipeline with 2 or 3 environments.
Long term idea is to think of how to transform this EC2 container workload into a stateless that could run over ECS.
So far using Route 53, Certification Manager, EC2 (Graviton t4g.micro instance family and size), simples IPv4 and IPv6 VPC (Bluesky do not support IPv6 at this time), EBS and Snapshot (manual for now), CloudWatch Log and metrics from CloudWatch Agent.
Next short term ideas are are a simple AWS Backup lifecycle job, test moving /pds folder to an EFS share, enable CMS KMS for the service, check if project tags are consistent for proper workload spense tracking and connect PDS to SES for email verification and password resets.
Medium term ideas are writing IaC to build the whole infra by automation, perhaps move into a CodePipeline pipeline with 2 or 3 environments.
Long term idea is to think of how to transform this EC2 container workload into a stateless that could run over ECS.