One provider, several workflows
AWS can cover multiple operational surfaces on Wodby instead of forcing teams to split cluster, storage, database, and mail concerns across several vendors.
Integration
Amazon Web Services integrations on Wodby
AWS is one of the broadest integration pages on Wodby: use EKS for clusters, S3 for backup targets, RDS for managed databases, SES for mail relay, and variable-style credentials where app code needs direct AWS access.
KubernetesStorageManaged DBSMTPVariables
Keep credentials reusable
A shared provider account or access model can support several Wodby workflows at once.
Match managed services to app stacks
Teams can combine provider-managed infrastructure with Wodby stack-based application delivery.
Supported workflows
How Amazon Web Services fits into Wodby
Each supported integration kind maps Amazon Web Services into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
Kubernetes
Elastic Kubernetes Service (EKS)
Use AWS as a managed Kubernetes target for Wodby stacks.
- Deploy the same versioned stack model onto a managed cluster target.
- Keep cluster operations with the provider while Wodby stays responsible for the app delivery workflow.
- Useful for teams that want managed infrastructure without rebuilding their stack definitions.
Storage
Simple Safe Storage (S3)
Send backup archives and storage-backed data from Wodby services to AWS.
- A practical fit for stateful services that should keep backup archives outside the running environment.
- Works with automatic backup workflows and restore paths.
- Lets teams standardize on an object storage target without changing the app stack itself.
Managed DB
Relational Database Service (RDS)
Use managed database services from AWS with Wodby cloud database stacks.
- Useful when the database should be managed externally instead of running inside the application stack.
- The provider-backed database stays inside the same stack-aware workflow on Wodby.
- Most relevant to Cloud PostgreSQL, Cloud MySQL, and Cloud MariaDB stacks.
SMTP
Simple Email Service (SES)
Relay outbound email through AWS from OpenSMTPD and app workloads.
- OpenSMTPD is the most direct stack-level consumer for SMTP integrations.
- Useful for transactional email flows that should route through a dedicated provider.
- Keeps provider credentials out of the application repository.
Variables
Variable
Inject AWS settings into services as environment variables instead of hardcoding them into app code.
- Keep provider keys, tokens, and DSNs outside repositories and local dotenv files.
- Attach the integration to reusable stacks, then connect it to the services that actually need it.
- Override values per environment without rebuilding the stack.
Configuration surfaced to workloads
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEY
Configuration surface
Values teams usually configure for Amazon Web Services
Wodby keeps these values at integration level and makes them available to the workflows or service containers that need them.
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEY
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Amazon Web Services.
Explore Kubernetes delivery
See how Wodby deploys versioned stacks onto managed Kubernetes targets.
See backups and imports
Use storage integrations as backup targets for stateful services and app data.
Explore managed databases
Connect cloud database stacks to managed providers while keeping the same app workflow.
See integration workflows
Keep SMTP providers reusable across stacks and environments.
Browse all integrations
Compare this provider with the rest of the integration catalog and other supported workflows.
Stack fit
Stacks that commonly pair with Amazon Web Services
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
Cloud PostgreSQL
Stack
Connection stack for apps that use managed PostgreSQL services such as Amazon RDS instead of self-hosting Postgres inside the stack.
Cloud PostgreSQL is the clearest path when you want Wodby to connect apps to Amazon RDS instead of running Postgres inside the app stack.
View stackCloud MySQL
Stack
Connection stack for apps that use managed MySQL services such as Amazon RDS instead of self-hosting MySQL inside the stack.
Cloud MySQL fits teams that want an RDS-backed MySQL service attached to the same Wodby workflow.
View stackOpenSMTPD
Stack
SMTP server stack that can relay mail directly or integrate with third-party delivery providers for reliable sending.
OpenSMTPD can relay outbound mail through Amazon SES for application stacks that need reliable delivery.
View stackNext.js
Stack
Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.
Application stacks such as Next.js can run on EKS while still keeping versioned stack definitions on Wodby.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.