Ricky Chew

hi @antonbabenko, currently there were 3 deployment options based on [RDS docs here](https://aws.amazon.com/rds/features/multi-az/) (see comparison table in the link). Also can be seen in AWS console while provisioning in UI....

I am deploying to PostgreSQL @agomezvidalee

@agomezvidalee thanks for the respond. That seems to be just creating replica from source DB. Read [docs here](https://aws.amazon.com/rds/features/multi-az/) (see comparison table) as my first comment above there are 3 kinds...

Like for example, `copilot job init` command [here](https://aws.github.io/copilot-cli/docs/commands/job-init/) can it have additional flag so it tells copilot which .yml files to pick up instead of just looking for default `manifest.yml`...

Yes that is default in AWS however it seems copilot has defaulted it to be 30 days, those cloudwatch log group that created without using `logging.retention` in `manifest.yml` has only...

yes, i am not sure if this is the best practice to do, but basically is to allowing frontend ECS connectiion to backend ECS, both are within same VPC.

Yes, understand that using service connect (Cloud Map) that comes with Copilot deployment. However, we still need to configure the backend ECS security group to allow access from frontend ECS...

Thanks @rubiconjosh for the info. Saw the pr but the link about the announcement was 404 https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-copilot-cli-effective-february-3-2025/ sad news