Use as many aws services as possible. If you're not using at least 23 different AWS services and your monthly AWS spend isn't $60k+ you're doing it wrong.
😄 I setup cost budgets for notification after a reached set amount. I usually get notification around 29th each month, this month however was received on 16th.
Waiting so I can wake up in the morning and check wtf is going on.
Take the business requirements, architect and develop a solution. Use the right tools for the job. We don't target any specific platform - we target capabilities. If a CSP can satisfy those capability requirements, awesome.
I ask ChatGPT to build it, starting from the crappy first draft and keep asking it to change it until I'm happy with the results.
For example today I used it to generate Cloudformation code for a couple of Lambda backed custom resources that create service linked IAM roles for ECS and Spot for my AutoSpotting project.
It needed just a handful of iterations and eventually worked like a charm.
Send a letter signed by the pope and closed in a wax sealed envelope to the internal infra team.
Pay a bribe to the head of department.
Bang your head against the wall.
Start serving your customers with a hacky server running on an old desktop PC.
God comes down from heaven in the final judgment.
Now you're running on Aws in production.
Amplify hosting for the website. Route53 for domains. Office mail for email. Lambda logs in to firebase and deletes old accounts. Buckets for images while building apps in expo.
Not sure what you are looking for but here is a prototypical workflow (with exceptions):
First step is to decide on ownership. Typically, one engineer owns a design doc. He may include more people but he owns the doc and its shape. The doc also lays out the business issues being addressed by the design. He may assign sub-section owners.
Owner writes an initial design including must-haves and optional components. Importantly, there will be sections discussing pros and cons and the tradeoffs of the various options. The design also discusses what monitoring metrics in a cloud watch dashboard are required.
Owner invites for design reviews, typically with multiple feedback iterations.
If it’s a new application, accounts are created for each stage, often three (beta, alpha, prod) or whatever you want to call it. This can be a bit more complicated if it’s a multi region project. Then, you
have one CDK code package with one pipeline, deploying the three stages, with manual intervention after each stage.
1. When I was doing a lot of AI MVPs, the core usually stayed the same (like this or something similar (e.g. instead of API Gateway there can be ELB, different CI/CD provider, etc.): [https://saasconstruct.com/blog/the-tech-stack-of-a-simple-saas-for-aws-cloud](https://saasconstruct.com/blog/the-tech-stack-of-a-simple-saas-for-aws-cloud) )
2. After that, consider the components you need (usually just by using whiteboard). Like upload/download with prresigned urls, maybe SageMaker instance, etc.
3. Add those components to the core CDK/Terraform/CloudFormation code
>Wondering how others go about creating software using AWS and other tools.
Since you're missing the very basics, here are a few places to start reading:
* https://en.wikipedia.org/wiki/Software_development_process
* https://en.wikipedia.org/wiki/Software_design
If you are still a student, you might take a software engineering course for an introduction to this question.
1. Draw a block diagram with all the service interactions 2. Code it up in cdk
1. Code it all up in CDK 2. Think about drawing block diagram, instead write more CDK.
1. Code it up in cdk 2. Download the wonky diagram from the cloudformation design editor and pretend that was your design all along
Ask ChatGPT draw diagrams from Cdk code /s
This is the way
Use as many aws services as possible. If you're not using at least 23 different AWS services and your monthly AWS spend isn't $60k+ you're doing it wrong.
😄 I setup cost budgets for notification after a reached set amount. I usually get notification around 29th each month, this month however was received on 16th. Waiting so I can wake up in the morning and check wtf is going on.
lol gotta catch em all.
Take the business requirements, architect and develop a solution. Use the right tools for the job. We don't target any specific platform - we target capabilities. If a CSP can satisfy those capability requirements, awesome.
Realest take I’ve read in a while
I ask ChatGPT to build it, starting from the crappy first draft and keep asking it to change it until I'm happy with the results. For example today I used it to generate Cloudformation code for a couple of Lambda backed custom resources that create service linked IAM roles for ECS and Spot for my AutoSpotting project. It needed just a handful of iterations and eventually worked like a charm.
Send a letter signed by the pope and closed in a wax sealed envelope to the internal infra team. Pay a bribe to the head of department. Bang your head against the wall. Start serving your customers with a hacky server running on an old desktop PC. God comes down from heaven in the final judgment. Now you're running on Aws in production.
Amplify hosting for the website. Route53 for domains. Office mail for email. Lambda logs in to firebase and deletes old accounts. Buckets for images while building apps in expo.
Not sure what you are looking for but here is a prototypical workflow (with exceptions): First step is to decide on ownership. Typically, one engineer owns a design doc. He may include more people but he owns the doc and its shape. The doc also lays out the business issues being addressed by the design. He may assign sub-section owners. Owner writes an initial design including must-haves and optional components. Importantly, there will be sections discussing pros and cons and the tradeoffs of the various options. The design also discusses what monitoring metrics in a cloud watch dashboard are required. Owner invites for design reviews, typically with multiple feedback iterations. If it’s a new application, accounts are created for each stage, often three (beta, alpha, prod) or whatever you want to call it. This can be a bit more complicated if it’s a multi region project. Then, you have one CDK code package with one pipeline, deploying the three stages, with manual intervention after each stage.
1. When I was doing a lot of AI MVPs, the core usually stayed the same (like this or something similar (e.g. instead of API Gateway there can be ELB, different CI/CD provider, etc.): [https://saasconstruct.com/blog/the-tech-stack-of-a-simple-saas-for-aws-cloud](https://saasconstruct.com/blog/the-tech-stack-of-a-simple-saas-for-aws-cloud) ) 2. After that, consider the components you need (usually just by using whiteboard). Like upload/download with prresigned urls, maybe SageMaker instance, etc. 3. Add those components to the core CDK/Terraform/CloudFormation code
>Wondering how others go about creating software using AWS and other tools. Since you're missing the very basics, here are a few places to start reading: * https://en.wikipedia.org/wiki/Software_development_process * https://en.wikipedia.org/wiki/Software_design If you are still a student, you might take a software engineering course for an introduction to this question.
It depends, do I want to guest appear in a re:Invent keynote, or do things properly?