Amazon Web Services Integration



Amazon Web Services supports the following integration kinds on Wodby.

  • Elastic Kubernetes Service (EKS)

    Create a ready-to-run kubernetes cluster on Amazon Web Services with pre-installed infrastructure

    Amazon Web Services can be used to create a Kubernetes cluster for your workloads.

    Wodby provisions the cluster as an integration target so stacks can be deployed onto it.

  • Simple Safe Storage (S3)

    Back up data for your applications with backups and upload to Amazon Web Services Simple Safe Storage (S3)

    Amazon Web Services can be used as a storage integration for backup archives.

    Backup data is uploaded to the connected storage provider instead of staying only inside the platform.

  • Relational Database Service (RDS)

    If you prefer to use a managed database solution for your app you can integrate special 'external' services from the databases page with Amazon Web Services Relational Database Service (RDS)

    Amazon Web Services can be used to connect third-party managed databases.

    This lets you deploy and use external database services instead of running the database inside the stack.

  • Simple Email Service (SES)

    Connect Amazon Web Services Simple Email Service (SES) for guaranteed email delivery with stack services such as OpenSMTPD

    Amazon Web Services connects to the OpenSMTPD service in your stack.

    OpenSMTPD relays outgoing mail through the provider to improve delivery reliability.

  • Variable

    Easily add Amazon Web Services secrets or environment variables to your app

    Amazon Web Services is configured as a variable integration for API keys, tokens, and other secret-based settings.

    The integration is attached at stack level and values can be overridden per environment when needed.

    How it works

    1. Create a Amazon Web Services integration and fill in the required secret or configuration values.
    2. Attach the integration to the stack so the values can be used by the services that need them.
    3. Connect the integration to an app service and Wodby will add the configured environment variables to that service container.
    4. Override values per environment when staging and production should use different credentials.

    Environment variables added to containers

    AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY

    When this integration is connected to an app service, Wodby adds these environment variables to the service container. Their values come from the integration configuration, with per-environment overrides when configured.

Related pages

Read more about integrations and browse other providers that can be configured the same way.

Integration feature overviewAll integrations