Day 30: Enable Internet Access for Private EC2 using NAT Instance
I followed the question and updated but still i am getting an error. Even though the job will run automatically to the S3 bucket, I got an error that the private route table is not associated with the NAT gateway even though I associated
As per the github repo you provided, i have followed the same for today but cron job is not happened. But yesterday everything works but failed I am not sure where exactly it denying the connection.
Today also I have followed the same to enable Internet access using the NAT instance, but still the job is not running to upload the file to the S3 bucket.
First created the Subnet with devops-pub-subnet with a private VPC and Enable auto-assign public IPv4 address, and also attached the IGW with the VPC.
created the public route table associated with public subnet
created security group while allowing all traffic with private subnet CIDR and SSH
Created the EC2 instance devops-nat-instance and disabled the source and destination
add the IP tables on the NAT instance following the doc
Attached the Nat Instance to private route table associate with private subnet
Not sure where exactly the internet access is blocking for S3 bucket to run cron job
Please, anyone, help me to finish this task; it will be very help to understand and learn if I am missed any part
I’ve just checked and it seems the solution is missing the update to the route table. Because of this, the private instance cannot access the NAT instance. The private route table should include a route to the internet through the NAT instance.
Thank you for sharing the solution. I have tried that; while generating through CLI, it works, but the manual way is failing with the NAT connectivity.
Thank you once again for completing the task. Day 30