aws部署apache/elb/s3等

一：部署AWS EC2, IGW, RT, NAT, SG

BRIEF

Imagine that you meet with a small startup company in the early stages of their

operations. Currently their architecture uses a LAMP stack with MySQL, Apache and PHP

all running on one desktop PC within their small office. Like many small start-ups they

are confident that they will be the next big thing and expect significant, rapid, yet

unquantified growth in the next few months. With this in mind, they are concerned

about:

scaling to meet the demand, but with uncertainty around when and how much this

demand will be they are very concerned about buying too much infrastructure too

soon or not enough too late!

their lack of provision for Disaster Recovery their ability to configure their

database and data access layer for high performance and throughput

making the user experience in the browser very low latency even though a large

portion of their user base will be from far away

effective distribution of load a self-healing infrastructure that recovers

from failed service instances security of data at rest and in transit securing

access to the environment as the delivery team expands an archival strategy

for inactive objects greater than 6 months ability to easily manage and

replicate multiple environments based on their blueprint architecture.

解答：

注解：

1、网络层：

Route53: Implemented the DNS domain name resolution service, connecting to the CloudFront endpoint via CNAME.

cloudFront: Implementing a global content delivery network, user requests will be directed to the lowest latency node, providing the best performance for the delivered content. You need to set the cloudFront to set the access source to the application’s ELB node.

AWS Regoin is the area where the application is deployed. A Region can have an A-Z Availability Zone.

IGW/NAT:

参考：https://zhuanlan.zhihu.com/p/363550751?utm_id=0

2、

参考：

https://blog.csdn.net/csy_csy1/article/details/90290364?ops_request_misc=&request_id=&biz_id=102&utm_term=aws%20%E6%96%B9%E6%A1%88%E6%9E%B6%E6%9E%84%E9%9D%A2%E8%AF%95&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduweb~default-4-90290364.142^v88^control_2,239^v2^insert_chatgpt&spm=1018.2226.3001.4187

3、auto scaling

二：

aws创建html网页,AWS: 在AWS上创建一个网站，综合运用（Lambda + Api Gateway + Dynamodb + S3)

https://blog.csdn.net/weixin_42367233/article/details/118045893

三：

At the end of this assignment you will have created a web site using the following

Amazon Web Services: EC2, EBS, ELB, EIP and S3.

1、在S3中部署静态网页。

https://blog.csdn.net/breaksoftware/article/details/106722804

2、ALB配置

配置成功。

3、EC2 web server

https://www.e-learn.cn/topic/3831057

4、cloudfront

https://blog.csdn.net/u011886447/article/details/79070197?ops_request_misc=%257B%2522request%255Fid%2522%253A%2522168612767116800184138690%2522%252C%2522scm%2522%253A%252220140713.130102334..%2522%257D&request_id=168612767116800184138690&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-2-79070197-null-null.142^v88^control_2,239^v2^insert_chatgpt&utm_term=cloudfront&spm=1018.2226.3001.4187

问题1：

配置ELB后，在浏览器中无法访问。

1 目前只能访问HTTP服务，无法访问HTTPS服务。

2 在ELB上新配置了安全组，安全组包括HTTP 80的规则。 2 EC2的安全组。

问题2：用ec2-user账号创建apache服务后，发现会报错资源不可达。

Forbidden

You don't have permission to access this resource.

解决方案：卸载apache后，用root账号完成apache服务的安装，和index.html文件的配置。

问题3：访问S3服务ok。访问web失败。

502 ERROR

The request could not be satisfied.

CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.

If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.