Browse categories
Explore
Fiverr Pro
English
$
USD
I will build secure AWS infrastructure with terraform
Senior Backend and Cloud Engineer
I am a Senior Software Engineer at Credera with production experience in Go, Python, AWS, Kubernetes, Terraform, APIs, cloud infrastructure, and CI/CD. I previously worked as an Amazon SDE intern and ...
About this Gig
I write Terraform configuration for AWS, with variables, outputs, validation, and documented plan and apply steps.
Starter covers up to 3 AWS resource types in one environment. Standard covers up to 10 in one environment. Premium covers up to 20 across development, staging, and production patterns.
Depending on the package, I include reusable modules, networking, compute, IAM, encryption settings, remote state, logging, and CI plan workflows. Premium also includes an approved apply workflow and an operating runbook. The default deliverable is infrastructure code and a documented handoff, not production deployment execution.
Before starting, I confirm the workload, account structure, regions, traffic path, data classification, availability and recovery requirements, and deployment ownership.
Message me before ordering for existing-state imports, multi-account landing zones, regulated workloads, production migrations, or strict zero-downtime changes. AWS charges, paid tools, and ongoing operations are not included.
Tools:
Other
Framework:
Terraform
Cloud Provider:
Amazon Web Services
Programming language:
Other
Expertise:
Development
•
Configuration
FAQ
Will you need access to my AWS account?
Not always. I can build and validate much of the configuration from requirements and existing architecture. If account access is required, use a least-privilege temporary role and never send long-lived credentials through Fiverr chat.
Do you apply the Terraform in production?
Only when explicitly included, access is safely provided, and the plan and rollback approach are approved. The default deliverable is reviewed infrastructure code and a documented handoff.
Can you import infrastructure that already exists?
Yes, after discovery. Imports can reveal drift, manual dependencies, and unsafe assumptions, so they require a custom scope rather than the fixed packages.
Does this include AWS charges?
No. AWS usage, domains, certificates from paid providers, licenses, and third-party services are paid directly by the buyer and are never purchased through this gig.
What counts as a revision?
A revision corrects delivered Terraform that does not match the agreed resource list and acceptance criteria. New regions, accounts, services, environments, or architecture changes require a scope update.
