You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the collector for monitoring our RDS instances via a Docker image on ECS, which uses the quay.io registry.
It would be great if you could additionally publish the image to the ECR public registry, so we could avoid a point of failure and get a slight speedup.
Thanks!
The text was updated successfully, but these errors were encountered:
This matter is slightly complicated because we'd have to teach our publishing process about pushing to ECR (and having enough permissions to do so), but it may fit into some other work we're doing for automating more of the package publishing, which also ends up in an S3 bucket.
I'll leave this open for now (no guaranteed ETA), and I'll see what we can do when we do the other automation work.
We use the collector for monitoring our RDS instances via a Docker image on ECS, which uses the quay.io registry.
It would be great if you could additionally publish the image to the ECR public registry, so we could avoid a point of failure and get a slight speedup.
Thanks!
The text was updated successfully, but these errors were encountered: