Download the PHP package cinghie/yii2-aws without Composer

Yii2 AWS

Yii2 AWS integrates AWS SDK for PHP v3 into Yii2 applications and provides wrappers for:

• Amazon S3 (upload, multipart, get/delete, presigned URLs)
• Amazon SES (classic) and SESv2 (draft helper for new sending)
• Amazon SNS
• Yii2 admin dashboards for the included services

Current package version: 0.3.0 (requires aws/aws-sdk-php ^3.0; tested with 3.389.0, the latest Packagist release at time of writing).

Installation

Or add the package to composer.json:

Basic Configuration

Configure the aws component and, if you need the included dashboards, the aws module.

With this configuration credentials are not stored in code: AWS SDK uses its native credential provider chain, including environment variables, IAM roles, container credentials, local profiles, and other supported providers.

Credentials

Recommended Option: IAM, Env Or Provider Chain

Environment variables supported by AWS SDK:

Local AWS Profile

Static Credentials

Use static credentials only when an IAM, env, or profile based setup is not available.

If only one of accessKey or secretKey is configured, the component throws InvalidConfigException.

AWS SDK Options

The component exposes the main Aws\Sdk options:

sdkOptions is passed directly to the Aws\Sdk constructor, so it can be used for advanced options that are not exposed as dedicated component properties.

Security note: debug => true is refused when YII_DEBUG is false, because the SDK may log signing/credential material.

Service clients (getS3Client(), getSesClient(), getSesV2Client(), getSnsClient()) are lazy-cached on the component. Models reuse those shared clients unless you inject a mock via setters.

Error Handling

The services do not write flash messages and do not convert AWS errors into empty arrays.

The contract is:

• success: returns Aws\Result
• AWS error: throws Aws\Exception\AwsException
• invalid local input: throws InvalidArgumentException

Example:

The included dashboards already catch AwsException in their controllers, log the detailed error, and display a generic message in the UI.

Input Validation

The wrappers validate common input mistakes before calling AWS. This keeps application errors deterministic and avoids sending obviously invalid requests to AWS.

Validated inputs include:

• S3 bucket names and object keys
• S3 local SourceFile paths (realpath, readable file; optional allowedUploadBasePaths)
• SNS topic names and topic ARNs
• SNS subscription protocols and endpoints
• SES email addresses
• SES domain names
• SES template names and template data (JSON)
• SES recipient lists
• SES receipt filter policies, limited to Allow or Block
• SES policy JSON strings

These checks are intentionally strict for common application use. AWS remains the final authority for service-specific edge cases.

Client Injection And Tests

Models can receive specific AWS clients through Yii configuration. This simplifies testing, mocking, and application-level overrides.

Available setters:

• S3::setS3Client(S3Client $client)
• SES::setSesClient(SesClient $client)
• SESV2::setSesV2Client(SesV2Client $client)
• SNS::setSnsClient(SnsClient $client)

If no client is injected, the model reuses the lazy client from Yii::$app->aws.

Amazon S3

Basic Usage

Create A Bucket

Upload A File

Large File (Multipart) And Presigned GET

Also available: getObject(), deleteObject(), doesObjectExist().

MinIO Or S3-Compatible Configuration

Amazon SES

Verify Identities

List Email Identities

Create A Template

Send A Templated Email

SESv2 (Draft) Simple Send

Prefer SESv2 for new sending code:

Create A Receipt Filter

Create A Receipt Rule With Recipients

Amazon SNS

SNS methods no longer have fake default values: protocol, endpoint, and topic must always be passed explicitly.

Create A Topic

Subscribe An Email Endpoint

Subscribe An HTTPS Endpoint

Yii2 Dashboards

The module exposes basic dashboards for the services:

• /aws/s3/index
• /aws/ses/index
• /aws/sns/index

Access is controlled by awsRoles:

Overrides

Controllers

Models

The bootstrap process registers model overrides in Yii's DI container. Query aliases such as S3Query, SESQuery, and SNSQuery are registered only when the mapped class extends yii\db\ActiveRecord; plain service models are not treated as ActiveRecord classes.

Views

Frontend Filter

In a Yii2 Advanced App, frontend module actions can be hidden with the included filter.

Operational Suggestions

• Prefer IAM roles, environment variables, or AWS profiles over static credentials.
• Do not store access keys or secret keys in the repository.
• Handle AwsException, InvalidArgumentException, and InvalidConfigException at the application layer.
• Never enable component debug when YII_DEBUG is false (blocked by the component).
• Prefer pinning service API versions via sdkOptions instead of relying on version => latest in production.
• Restrict S3 uploads with allowedUploadBasePaths when accepting user-supplied SourceFile paths.
• Prefer SESv2 (SESV2 model) for new sending code; classic SES remains supported.
• Inject specific clients in tests instead of calling real AWS services.
• Use endpoint and usePathStyleEndpoint for MinIO, LocalStack, and S3-compatible services.
• Avoid demo values or placeholders in production code: always pass explicit parameters.

AWS Documentation

• S3: https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/s3-examples.html
• SES: https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/ses-examples.html
• SESv2: https://docs.aws.amazon.com/ses/latest/APIReference-V2/
• SNS: https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/sns-examples.html