Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infrastructure as code #3

Open
1 of 7 tasks
j6k4m8 opened this issue Nov 15, 2020 · 1 comment
Open
1 of 7 tasks

Infrastructure as code #3

j6k4m8 opened this issue Nov 15, 2020 · 1 comment

Comments

@j6k4m8
Copy link
Collaborator

j6k4m8 commented Nov 15, 2020

Right now, the configuration steps (setting up the SES email address, validating, and attaching the S3 hook to the SES incoming message action) are all manual. They're pretty well-documented (ha! not by me; check out the AWS docs in the README) but I'd love for this all to happen during deploy.

Most likely this looks like a provisioning step (some python script) which you run beforehand (which also creates a config.py for you), followed by a regular zappa deploy.

  • init
  • create-bucket
  • verify-domain
  • verify-sender
  • validate-ses-account
  • create-s3-event
  • connect-s3-event
@j6k4m8
Copy link
Collaborator Author

j6k4m8 commented Feb 14, 2021

There are two options:

  • cloudformation (big json file)
  • boto python for everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant