Tagging of Aurora Auto Scaling Replicas

We are using AWS Aurora with automatic scaling of read replicas, which are launched with a generated name-tag with the prefix "application-autoscaling-" but no other tags. Is there a way we could overwrite the prefix and define additional tags (like the environment or application-id for which the cluster is used), as we can do for instances launched into EC2 auto-scaling groups?

I can imagine doing this with some lambda function, but is there maybe an easier way? And if not, how are the costs for the autoscaled readers reported in the cost-replorer for example? Are they counted towards the readers I've created manually in the cluster?