Boto3 tutorial examples SEO Brief & AI Prompts

You are building a publish-ready, SEO-optimised outline for an informational, 2200-word article titled 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks' in the 'Automation & Scripting with Python' topical map. Produce a ready-to-write outline that is developer-focused, practical, and authoritative. Include: H1, all H2 headings, H3 sub-headings, suggested word counts per section that sum to ~2200 words, and 1-2 notes under each heading about what must be covered (must include code patterns, security, testing, and production pitfalls). The outline must balance explanation + copy-pastable examples and include a short resources/tools list at the end. Priorities: S3 (pagination, multipart, object lifecycle), EC2 (provisioning, tags, cost control, waiters), IAM (least privilege, role assumptions), common tasks (logging, retries, error handling), and CI/CD/testing. Use section word targets (numbers). Do not write the article — only create the structured blueprint. Output format: return a numbered outline with H1, H2, H3, per-section word counts, and 1-2 bullet 'must cover' notes for each section. Ensure total words ~2200.

You are creating a research brief for the article 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. List 8-12 entities, tools, studies, statistics, expert names, and trending angles the writer MUST weave into the article. For each item include a one-line note explaining why it is essential and how to cite or integrate it (e.g., link, command, or paraphrase). Include: AWS SDK (boto3) docs, AWS Well-Architected Framework, cost statistics for EC2/Storage, Moto testing library, IAM least-privilege guidance, AWS CLI comparisons, boto3 paginators/waiters docs, and relevant AWS blog posts or recent conference talks. Make items practical (what paragraph to use them in). Output format: return an ordered list of 8-12 items, each with a 1-line rationale and an 'integration note' telling the writer where to place or cite it in the article.

Write a 300-500 word introduction for the article 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Start with a compelling hook that addresses reader pain (repetitive cloud tasks, fragile scripts, unexpected costs). Give concise context about boto3 as the Python AWS SDK and why automation matters for DevOps and developers. State a clear thesis sentence: what the reader will achieve by following this article (production-ready patterns for S3/EC2/IAM plus testing and CI/CD integration). Then list 3 specific outcomes the reader will get (e.g., safe IAM automation pattern, reliable S3 transfers with pagination and multipart, idempotent EC2 provisioning and teardown). Keep tone authoritative and practical, promise examples and caveats, and include a short transition sentence to the next section. Output format: return a single continuous intro section, ready to paste into the article, with no subsections and targeting low bounce engagement.

You will write the complete body of the article 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks' targeting ~2200 words. First, paste the outline produced in Step 1 exactly as the input before running this prompt. Then write each H2 section fully, in the order of the outline; finish each entire H2 block (with its H3 subheads) before moving to the next. Include concise, copy-pastable Python code snippets using boto3 for each practical task (S3 uploads with paginator/multipart, EC2 create+tag+wait+terminate, IAM policy example and assume-role snippet, using sessions and profiles, retry/backoff, logging). For each code example include a short explanation, security notes (credential sources, least privilege), and a 'Production tip' bullet. Cover: S3 operations (pagination, multipart, lifecycle), EC2 automation (AMI launch, tags, waiters, cost controls), IAM automation (policy templates, assume-role patterns), common tasks (retries, exponential backoff, IDE/test tips, Moto for unit tests), and CI/CD integration snippet (GitHub Actions example). Include transitions between sections. Use headings, brief paragraphs, and keep code blocks concise (prefer 8-20 lines). Target total ~2200 words. Output format: deliver the full article body as plain text with H2 and H3 headings matching the pasted outline. Paste your Step 1 outline here:

Create strong E-E-A-T signals for 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Provide: (A) five specific, high-quality expert quote suggestions — each quote line followed by the suggested speaker name and concise credentials (e.g., 'Jane Doe, Senior AWS Solutions Architect at XYZ — quote text'). The quotes should support claims about best practices, security, and automation reliability. (B) three real studies/reports or official docs to cite (include title, publisher, year, URL, and one-line why to cite). (C) four short, experience-based sentences the author can personalise that show real-world experience (e.g., 'In a production fintech deployment I encountered X and solved it by Y — include brief metrics'). Make items copy-ready for in-article use and label them. Output format: deliver three labeled sections 'Expert quotes', 'Studies & docs', and 'Personal experience lines' with bullet lists for each.

Write a FAQ block of 10 concise Q&A pairs for the article 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Target People Also Ask, voice-search, and featured snippet formats. Each answer must be 2-4 sentences, conversational, and specific (include commands, parameter names, or short code references where appropriate). Prioritize likely reader queries such as: how to authenticate boto3 safely, how to upload large files to S3, how to wait for EC2 instance readiness, creating least-privilege IAM policies for automation, error handling and retries, costs and cleanup, testing boto3 code, and using roles in CI. Output format: return an ordered list numbered 1-10, each with the question in bold style and the short answer below (plain text).

Write a 200-300 word conclusion for 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Recap the key practical takeaways (one sentence each for S3, EC2, IAM, testing/CI). Include a strong single-call-to-action instructing the reader exactly what to do next (e.g., 'Clone the sample repo, run tests, apply least-privilege policy example to a test account, and open a PR'). Add one sentence linking to the pillar article 'Python Automation: Best Practices, Tooling, and Patterns for Reliable Scripts' that explains why they should read it next. Keep tone prescriptive and motivating. Output format: return the conclusion as a single ready-to-publish paragraph block followed by the CTA as a short numbered checklist.

Generate the SEO title tag, meta description, OG title, OG description, and a complete JSON-LD block that contains both Article and FAQPage schema for 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Constraints: (a) title tag 55-60 characters, (b) meta description 148-155 characters, (c) OG title and OG description should be compelling and include the primary keyword, (d) JSON-LD must include article headline, author placeholder, datePublished/dateModified placeholders, wordCount ~2200, and the 10 FAQ Q&A content produced in Step 6. Use concise, publication-ready language. Output format: first list the title tag, meta description, OG title, OG description as separate lines, then provide the full JSON-LD block only (no surrounding text) formatted as valid JSON.

You will create an internal linking plan for 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. First, paste the full draft of your article produced earlier (paste the entire article text below before running this prompt). Then produce 6-8 link suggestions: for each, give the target article title within the topic map, the exact sentence from the pasted draft where the link should be inserted (quote the sentence), and the recommended anchor text to use. Prefer links to: pillar article on Python automation, S3 deep-dive, EC2 cost optimization guide, IAM policy examples, testing Python AWS code, CI/CD pipelines for infra. Make sure anchor text is 2-6 words and natural. Output format: return a numbered list where each item contains 'Target article', 'Quoted sentence from draft', and 'Anchor text'.

Create a visual and image-SEO plan for 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. Recommend 6 images. For each image include: (1) short filename suggestion, (2) what the image shows in one sentence, (3) exact location in the article (e.g., 'above S3 pagination section'), (4) the SEO-optimised alt text (must include the primary keyword 'AWS automation with boto3' and be 6-14 words), (5) recommended type (photo, infographic, screenshot, diagram, code-screenshot), and (6) a 1-sentence photographer/creator note (e.g., 'use AWS console screenshot with blurred sensitive info'). Also give a brief note on image size/aspect and whether to lazy-load. Output format: return an ordered list 1-6 with the six image specification objects in plain text.

Write three ready-to-publish social posts promoting 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. (A) X/Twitter: create a thread opener tweet (max 280 chars) plus 3 follow-up tweets that expand with a short code snippet or tip, each tweet concise and numbered. (B) LinkedIn: write a 150-200 word professional post with a hook, 2-3 insights from the article, and a CTA linking to the article. Tone: developer->developer, credible. (C) Pinterest: craft an 80-100 word SEO-rich Pin description that includes the primary keyword and tells what the pin links to (tutorial, code snippets, testing tips). Include suggested hashtags for X and LinkedIn (3-5 each). Output format: return three labeled sections 'X Thread', 'LinkedIn Post', and 'Pinterest Description' with the content for each.

You will perform a detailed SEO and quality audit of the article draft 'AWS Automation with boto3: S3, EC2, IAM and Common Tasks'. First, paste the full article draft (paste below) before running this prompt. The audit must check: primary keyword placement (title, first 100 words, H2s, meta), secondary/LSI usage, heading hierarchy, readability (estimate Flesch score or grade), E-E-A-T gaps and recommended author credentials, duplicate-angle risk against top-10 results, content freshness signals (dates, versions of boto3/AWS SDK), and internal anchor/link coverage. Then provide 5 concrete improvement suggestions prioritized by SEO impact, and 5 suggested exact edits (word-level: e.g., 'replace sentence X with Y' or 'add a line after paragraph 3'). Output format: return a named JSON object with keys: 'keyword_checks', 'readability_estimate', 'E-E-A-T_issues', 'duplication_risk', 'freshness_notes', 'internal_links_coverage', 'top_5_improvements', and '5_exact_edits'.