Improvements #3
Improvements #3
Conversation
… the repo and improve some descriptions
… the Launch Configuration
|
|
||
| In [the first section](/workshop/s3-web-ec2-api-rds/05-finishing-up.md), the `API_URL` parameter was set to the DNS name of our only instance. Now, we need to tell the web that the request must be done through the load balancer, so we need to modify `API_URL`. | ||
| We also need to modify the CodeDeploy project so the tool knows that now we have an Auto Scaling Group and that it needs to run the deploy on each of the instances in the group. | ||
| We also need to modify the CodeDeploy project so the tool knows that now we have an Auto Scaling Group and that it needs to run the deploy each time a new instance is launched. |
There was a problem hiding this comment.
Y además en las instancias existentes, no? Cómo funciona con las que ya están levantadas?
There was a problem hiding this comment.
La que ya está corriendo no se entera de nada. Todos los deploys futuros se van a hacer atravez del ASG.
| **Extra mile:** | ||
|
|
||
| - Can you `ping` the Postrges instance? | ||
| - Try to connect to the DB through your running EC2 instance. |
| 3. SSH into the instances (from the bastion) with `ssh <private-ip-of-webserver-instance> -i <pem-file-name>`. | ||
|
|
||
| --- | ||
| **Extra mile:** `ssh` to one of the instances in the private subnets and `tracepath` to an external host. Do the same for a instance in the public subnets. What's the difference? |
| 5. Delete existing Launch Configuration group. | ||
| 6. Repeat the same steps from this [section](/workshop/elb-auto-scaling-group/02-auto-scaling-group.md), but select the default security group of your VPC. | ||
|
|
||
| Now you need to create a new Launch Configuration almost identical to the one that you just delete except for one things: instead of create a Security Group you need to choose the default one for your VPC. |
There was a problem hiding this comment.
No entendí muy bien por qué hay que hacer esto vs crear el security group normalmente!
There was a problem hiding this comment.
Hay dos temas: ya existe un security group para esto que fué creado cuando se configuro el ASG por primera vez. El otro tema es que las instancias nuevas que levante el ASG tiene que estár dentro de la VPC, por eso es toda la tranza de identificar el security group por defecto de la VPC nueva.
| 6. Repeat the same steps from this [section](/workshop/elb-auto-scaling-group/02-auto-scaling-group.md), but select the default security group of your VPC. | ||
| 5. Delete existing Launch Configuration. | ||
|
|
||
| Now, you need to create a new Launch Configuration that is almost identical to the one that you just deleted except for one thing: instead of creating a Security Group you need to choose the default one for your VPC. |
There was a problem hiding this comment.
No entendí muy bien por qué hacer esto vs crear el SG normalmente
There was a problem hiding this comment.
Fijate en la respuesta anterior, si no se entiende te lo explico denuevo en esta :P
2 participants
Address some (all ?) of the comments that appear here
Close #2