Tweet
Tweet

Slide 1

Slide 1 text

Netlify from the Infrastructure Engineer perspective Netlify Meetup Tokyo #1 Shogo Muranushi

Slide 2

Slide 2 text

Who are you? Shogo Muranishi ABEJA, Inc SRE/Infra Engineer, Product Owner Speciality is AWS

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Receive requests I would like to web hosting static contents. 
 and I will use HTTPS. Okey

Slide 5

Slide 5 text

I think. 1st If you just want to hosting a static site simply, Amazon S3. Amazon S3 is… Object Storage. High scalability, High availability, High security, Low cost. Very simple web hosting service. S3

Slide 6

Slide 6 text

I think. 2nd If requires HTTPS to Amazon S3, you also need CloudFront. CloudFront is… CDN ( Contents Delivery Network ). That is not simple. It takes time for each change. S3 CF

Slide 7

Slide 7 text

I think. 3rd If requires SSL, you also need ACM. ACM is… Amazon Certificate Manager. Free SSL certificate, Automatic update. But… S3 CF ACM

Slide 8

Slide 8 text

I think. 4th If require ACM, email authentication is also need and SES is needed.
 (Recently, DNS authentication can also be selected.) SES is… Simple Email Service. You can send and receive mail. But… S3 CF ACM SES

Slide 9

Slide 9 text

I think. 5th If requires SES, you also need s3 bucket to receive mail. Create s3 bucket to receive mail… S3 CF ACM SES S3

Slide 10

Slide 10 text

Complete !! S3 CF ACM SES S3 This is Building Block !!

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

This is not simple You need to know a little about AWS. You need to maintenance and troubleshooting it. You will be asked to change config.

Slide 13

Slide 13 text

I do not want to do anything I do not want you to depend on me. My work increases as it depends. I searched for a simple way.

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

I tried Netlify I opened an account. I completed Web hosting work in 
 10 minutes. It was very simple compared to AWS

Slide 16

Slide 16 text

Netlify from the Infrastructure engineer perspective

Slide 17

Slide 17 text

Good point, 1st Static web hosting and CDN High Performance High Availability High Scalability In case of Web server?

Slide 18

Slide 18 text

CDN Contents Delivery Network https:/ /freefeast.info/general-it-articles/cdn-content-delivery-network/

Slide 19

Slide 19 text

Good point, 2nd Continuous Delivery Very simple Github integration Deliver with `git push` In case of S3?

Slide 20

Slide 20 text

Good point, 3rd Simple deploy free SSL certificate Deploy with few clicks In case of ACM?

Slide 21

Slide 21 text

Good point, 4th High Security Static contents is very high security. In case of WordPress?

Slide 22

Slide 22 text

Good point, 5th Other Form receive service Branch deploy A/B test

Slide 23

Slide 23 text

Good point, 6th Infrastructure engineer is unnecessary.

Slide 24

Slide 24 text

But, Monitoring is necessary. URL Monitoring Pingdom, StatusCake, Stackdriver, etc… Responce code, Latency, etc…

Slide 25

Slide 25 text

Troubleshooting You can't control CDN Troubleshoot. Let's have a cup of tea Or Multi CDN..?

Slide 26

Slide 26 text

Appendix Netlify IP Adress is Google Cloud?

Slide 27

Slide 27 text

Appendix Netlify IP Adress is Google Cloud?

Slide 28

Slide 28 text

I work has gone.