No, it will not route anything through GitHub Actions when a user visits your site. After a successful deploy to your S3 bucket, the GitHub action terminates and will only be triggered when you make a new push to the master branch.
Thank you for your question 🙂. For Amazon S3, it is inherently scalable and scales seamlessly to serve thousands of HTTP or HTTPS requests per second without any changes to the architecture. But we can improve our current architecture by configuring the site to be served from the S3 bucket through AWS Cloudfront, which will give some benefits and more like:
Low latency across different locations with the use of edge locations.
Better page speed across different locations
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
No, it will not route anything through GitHub Actions when a user visits your site. After a successful deploy to your
S3bucket, the GitHub action terminates and will only be triggered when you make a new push to themasterbranch.Great, Thanks for clarifying! How will the website performance be if there are 100 users on the website at a time vs. 10,000 users at a time?
Thank you for your question 🙂. For Amazon S3, it is inherently scalable and scales seamlessly to serve thousands of HTTP or HTTPS requests per second without any changes to the architecture. But we can improve our current architecture by configuring the site to be served from the
S3bucket throughAWS Cloudfront, which will give some benefits and more like: