Where do I begin?
What an experience! For folks who do not know what #CloudResumeChallenge is about, buckle up. The challenge was introduced to me and my classmates the start of the spring semester at Miami Dade College. The challenge has its ups and challenges. It is a great start to get yourself started with the different services AWS has to offer and get integrated. For quick background of myself, I am currently a supervisor at Teleperformance on the Hughes account. prior to this challenge I didn't have any experience working with cloud resources. However, if you're like me don't worry, AWS does an amazing job giving you all the resources you need to use their services, especially as a newbie like myself.
It may take some time and hands-on walkthroughs to completely understand the services and how they work, but no worries AWS has extensive documentation and their are numerous blog posts that give you what you need. This blog post contains a short walkthrough of the steps I took to complete the #CloudResumeChallenge and what I've learned from this experience.
Setting up the frontend
Setting up the backend
Connecting both front and backend together
The key takeaways for me this first half was the project:
- Securing and locking the root account is a MUST.
- Origin-Access Identity is a more secure way of hosting a website on S3.
- A standard DNS server cannot choose the best server to use per request based on specific rules, but other services, such as CloudFront can.
- A CloudFront distribution is a valid target for traffic from a DNS server, and it can take an S3 bucket as its origin.
- Requests from CloudFront to S3 are HTTP, not HTTPS. Amazon S3 does not expose an HTTPS endpoint.
- In some scenarios, Lambda functions may need CORS headers.
- A CloudFront distribution allows specifying domain name aliases to enable access to the cached content via custom domain names.