1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
I can't start a new one, but I don't think it affects resources that are already active.
https://repost.aws/knowledge-center/delete-shared-vpc
Un-sharing subnets doesn't have a direct impact on the active resources. However, you must terminate all active resources within the shared or un-shared VPC to delete the parent VPC. To verify active resources, do the following:
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa