Blend creativity with cloud computing prowess to transform a mundane CV into a dynamic, cloud-hosted website. By conquering this challenge, you're not just flaunting your tech skills; you're unlocking doors to potential job opportunities. It's the ultimate flex for tech enthusiasts—showcasing your abilities in AWS, web development, and more. Through AWS hand-on you get to know how a serveless architecture deployment looks.
S3 bucket is used for storing the files like html, css and images (all static files) basically to host static website. To keep the bucket private and accessible we use the next AWS service, Cloudfront!
By setting OAI (Origin Access Control) it allows access to S3 bucket indix.html file (set root deffault object in cloudfront). It adds extra layer of security by authorizing access to private index.html in S3. It enhances performance by caching at the edge giving low latency while accessing the site which also saves network cost.
Buy domain name from route53(or namecheap), request a SSL certificate from ACM (if you used route53 to buy domain). As I had got my domain from namecheap I had to manage nameservers in domain lists and configure Route53 records. Custom domain name can be set in route53 and we make the record in route53 point towards cloudfront distribution. Deployment of website using custom DNS over HTTPS is done.
Create DynamoDB table with the attributes mentioned in the table(set value 1 for both). We don't want to fetch data directly from DynamoDB
| Primary key | Attributes |
|---|---|
| Partition key: CounterName | string |
| visitors | number |
Write a lambda function to access table in dynamoDB and then to print the value of hit counter and addinng-storing the value of views in DynamoDB on a hit to website.
Create a javascript file which will fetch request from lambda function and store in a variable we have created which is used to display hit counter on your website.
Create .github\workflows file in which you create a yaml file to write github actions which will be responsible to push new content to S3 when we push from local to github.
DON'T PUT YOUR AWS ACCESS KEY AND SECRET KEY OR S3 BUCKET IN THE WORKFLOWS FILE we create env variables for all the secrets.
Go to Github repo >> settings >> in Security sections go to 'Secrets and Variables' >> Actions >> Set Respository Secrets
After understanding all the above services, its underline working and the usage of policies, you can use Terraform to create this whole architecture using just the code hence implementing IaC (Infrastructure as Code). Your knowledge on policies for all the AWS services used will be tested while implementic IaC. There will be very minimal use of AWS UI and Click Ops.
1 ) AWS SNS, AWS SQS, AWS SES
2 ) AWS CloudWatch
3 ) API Gateway
-
AWS Cognito
-
AWS CodePipeline
-
AWS CloudFormation
Using these services you will still keep the architecture serverless. Using Aws services like SNS , SQS AND SES with CloudWatch helps monitor any metric you want, it will help fan out alerts , and it can also help trigger lambda function.
AWS Cognito will add an extra layer of security by authenticating the user.
AWS CodePieline can be an alternative to GitHub actions for CI/CD integration.
AWS CloudFormation can be used as an IaC instead of terraform.
serverless architecture