Bonus / Optional Add-ons

EC2 Bonus Checklist

These are best practices and field-tested settings you can easily add to your bot by chatting with it. Copy and paste each prompt when you are ready to add another layer of protection or automation.

Production rules

Tell the bot how to treat production, branches, and archives

This gives the bot a simple working pattern before it starts creating real websites and products.

Please add these website/project safety rules to your workspace markdown files:

      1. Do not edit production directly unless I explicitly approve it.
      2. Create a branch, draft, or version folder for meaningful website/app changes.
      3. Preserve useful previous versions in an archive folder before replacing live work.
      4. For S3 websites, publish review versions first and give me the review URL.
      5. Only promote a branch or version to production after I clearly approve it.
      6. If an existing AWS account has production data, ask me which buckets, databases, and projects are protected before editing.
      7. If we create a backup, add a deny policy or other protection so the bot cannot casually overwrite or delete the backup.
      8. When you change a rule file, show me exactly what file you updated.
Cost watchdog

Ask the bot for a biweekly AWS cost analysis

Cost is the most practical ongoing guardrail. Paste this prompt to your bot and ask it to create a cron job (a regular request that will automatically be sent to your Telegram) to check your setup for any AWS costs so you can easily monitor it.

Please set up a biweekly cron job to review AWS costs.

      Goal:
      - Every two weeks, check current AWS month-to-date spend.
      - Compare it to the previous period if available.
      - Identify services causing charges.
      - Look for resources that may be forgotten, idle, oversized, public, or unexpectedly expensive.
      - Recommend cleanup actions before doing anything destructive.
      - Send me a short summary with:
        1. current month-to-date spend
        2. top paid services
        3. unusual changes
        4. cleanup recommendations
        5. anything that needs my approval

      Safety:
      - Do not delete, stop, resize, or modify resources without asking me first.
      - If you need AWS permissions to inspect costs, tell me exactly which permissions are needed.
      - Save the schedule/check instructions in the appropriate local markdown file so this survives future sessions.
Optional add-on

Protect production or backup buckets

For a brand-new AWS account, you can usually skip this. For an existing AWS account, or for a backup bucket you never want the bot to overwrite, create a second deny policy and replace the placeholder with your real bucket name.

{
        "Version": "2012-10-17",
        "Statement": [
          {
            "Sid": "DenyProtectedS3BucketChanges",
            "Effect": "Deny",
            "Action": "s3:*",
            "Resource": [
              "arn:aws:s3:::REPLACE_WITH_PROTECTED_BUCKET_NAME",
              "arn:aws:s3:::REPLACE_WITH_PROTECTED_BUCKET_NAME/*"
            ]
          }
        ]
      }
Finished

Congratulations. Your bot is done and ready to build things.

Recommended next lesson: learn how to use specs, design notes, tasks, README files, and S3 bucket principles so your bot can build websites and apps in a more organized, reliable way.