AsyncAws Symfony Bundle

A small SymfonyBundle that helps with configuration and autowiring.

Install¶

composer require async-aws/async-aws-bundle

Configure¶

The bundle will autowire all AsyncAws clients that you have installed. You can provide default configuration to all clients and specific configuration of each service you define.

This example assume you have installed core, ses, sqs and s3:

# config/packages/async_aws.yaml

async_aws:
    config: # Will be merged with other configuration
        region: eu-central-1

    clients:
        ses: ~ # This will complain if we don't have that package installed
        sqs:
            config:
                region: us-west-1
        delayed:
            type: sqs

The config above will create the following services:

For a complete reference of the configuration please run:

php bin/console config:dump-reference async_aws

Note: Multiple clients with different configuration for the same service can be created by providing a unique name and defining the service in the type sub-property. See client delayed in above example.

Using SSM to store secrets¶

Since version 4.4, Symfony provides secrets management. AsyncAws leverage this feature and by storing secrets in AWS SSM Parameter Store:

# config/packages/async_aws.yaml

async_aws:
    secrets: ~
#        path: /parameters/my-project
#        recursive: true
#        max_results: 20
#        client: app-secret
#        cache:
#            pool: cache.app
#            ttl: 3600
#    clients:
#        app-secret:
#            type: ssm

Parameters stored in SSM will be available as env variable:

Warning: Fetching parameters from SSM is billed by AWS. AsyncAws provide an optional cache layer that can be enabled with the cache configuration.

# config/packages/doctrine.yaml

doctrine:
    dbal:
        password: '%env(DATABASE_PASSWORD)%'

When recursive option is true, AsyncAws Bundle will retrieve all parameters within a hierarchy, then will trim the path prefix option, replace / by _ and uppercase the parameter name. ie. in the above configuration, a parameter stored in /parameters/my-project/database/password will be referenced by DATABASE_PASSWORD.