AWS CloudFormation:

A stack in the sky

⛅

☁️

🌧️

🌬️

🛩️

🥞

@YvesGurcan

https://slides.com/yvesgurcan/cloudformation/live

Follow along

Who this?

My name is not as complicated as you think 🤓

Not a pickle 🥒

Senior software engineer 👴🏻

French 🇫🇷

JavaScript All The Things! ⚡

AWS Cloud Practitioner 📜

@YvesGurcan

https://connect.yvesgurcan.com

✋✋✋✋✋
On a scale from 🌈 to 💩
how do you feel about CloudFormation?

third option: ⛏️

CloudFormation

Infrastructure as Code (template) 🛣️

YAML / JSON ✍️

Deploy and connect resources 🏗️

Organized as stacks 📚

Continuous integration/development ♻️

IAM roles & policies 👮‍♀️

Check errors / Automatic rollback 💥

No additional cost 👍

What CF does not do

Coffee ☕

Access your machine locally (SAM) 🖥️

Check that your stack works the way you expect it to work (tests) 🔧

Monitor cost of deployed resources 💰

CloudFormation is not a super admin 🗿

Anatomy of a template

AWSTemplateFormatVersion: "2010-09-09"
Description: Static website using S3

Resources:
  S3Bucket:
    Type: AWS::S3::Bucket
    Properties:
      AccessControl: PublicRead
      BucketName: amazing-website-about-gherkins
      WebsiteConfiguration:
        IndexDocument: index.html
        ErrorDocument: error.html
    DeletionPolicy: Delete

Outputs:
  WebsiteURL:
    Value: !GetAtt [S3Bucket, WebsiteURL]
    Description: URL for website hosted on S3
  S3BucketSecureURL:
    Value: !Join ["", ["https://", !GetAtt [S3Bucket, DomainName]]]
    Description: Name of S3 bucket to hold website content