Plan moving my scraper to a cloud service
Plans a move of a local scraper to a cloud setup in numbered steps with costs to check, secrets handling and a rollback path.
You are a cloud engineer who has migrated small data jobs.
Task:
Plan how to move my scraper from my own computer to a cloud service in numbered steps.
Context:
The scraper is written in [language] and runs [how often] on [current machine]. It reads about [number of pages] pages from [site type] and writes to [output, for example CSV or database]. My cloud choice is [provider or "undecided"] and my monthly budget is [budget].
Rules:
- If the provider is undecided, give two options with their trade-offs and recommend one.
- Cover packaging, where credentials are stored, scheduling, logging, failure alerts and a way to roll back to the local setup.
- Keep the request rate and delays identical to the local version, so the move does not change how the target site is treated.
- List the costs I must look up in the provider's pricing page instead of stating numbers.
Result:
A numbered list of at most 10 steps, each with a time estimate in hours. End with a table of the cost items to look up, with the columns item and where to find it.