- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
It finally worked. I was going through the workshop instructions again to check if I have missed anything. So, They have specifically mentioned in the instructions to use default VPC for the workshop.
This is the note they have mentioned:
**All the resources were deployed to the Default VPC for this lab. In real life scenario, you can deploy to your own VPC and subnets using x-aws-vpc extension (commented in docker-compose.prod.migrate.yaml).
I had used my custom VPC using "x-aws-vpc" parameter in docker-compose.prod.migrate.yaml file and due to that, it was creating an issue when creating AWS resources.
In the cloud9 terminal logs, I'm able to see that all services has been successfully created and also verified in cloudformation "Resources" section.
Thank you Madhav_P for your input. Appreciate it.
Though I haven't tried this, what I would do is to set the rollback option for cloudformation script to 'no' so that it remains in the same state when a failure occurs rather than rolling back and deleting the cloud components it created so far. That way one would be able to debug better.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
As I mentioned, docker compose up command automatically behind the scenes created cloudformation to deploy the resources. I don't have any control to make any configuration change.