pawaitemadisoncollege
commented
6 months ago Hi @potatoesnmolasses! Great job getting your indie project deployed up to AWS! There are a lot of fiddly parts to this work and you met the challenge! Be sure to add your deployed app url to the list of indie projects in the student repo (makes it easy for future reviews).
Darin also ran into an issue with incurring a fee, but I think he resolved it, though I am not sure of the solution - I'd recommend a post out in Slack to check in on this. I have seen charges incurred when somebody has more than one beanstalk instance deployed; not sure if that is the case for you? I had thought IPV4 were free for the first year too; I wonder if their billing is messed up or?? https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/. Might be worth trying ipv6??
@pawaitemadisoncollege Week 6 is ready for review!
Deployed app link here What were your key learning points/takeaways? I learned how to set up environments in AWS and deploy applications to them! What challenged you? I struggled to set up my project at first - the environment wouldn't finish creating because apparently I needed a service role, key-pair, and instance profile. I also didn't pull my AWS database password into the repository the way it needed to at first. What problems did you solve and what resources did you use to solve them? I was able to resolve the issue with the service role/key-pair using the AWS documentation and advice from the Slack chat. The password issue was eventually resolved after I watched the setup video again!
I am concerned, however, that my environment already appears to be incurring charges? I'm not sure what I've done wrong, since I thought the first 750 hours of public IPv4 were supposed to be free? I'll include a screenshot.
