2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
2
If this was the control plane security group, I don't believe you can modify this and you won't be able to re-create the security group ID. Your best option at this point is to rebuild the cluster. Please also see: https://github.com/aws/containers-roadmap/issues/738
0
Yes, I saw that issue long time ago. However, my cluster here is production one and it will take more effort to rebuild and migrate all the things there. I'm also wondering why the force update does not happen. At least, I can try to schedule downtime for this
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 3 Monaten