Skip to main content

Integration of CDK apps with local assets

Project description

AWS CDK Assets

Assets are local files or directories which are needed by a CDK app. A common example is a directory which contains the handler code for a Lambda function, but assets can represent any artifact that is needed for the app's operation.

When deploying a CDK app that includes constructs with assets, the CDK toolkit will first upload all the assets to S3, and only then deploy the stacks. The S3 locations of the uploaded assets will be passed in as CloudFormation Parameters to the relevant stacks.

The following JavaScript example defines an directory asset which is archived as a .zip file and uploaded to S3 during deployment.

const asset = new assets.ZipDirectoryAsset(this, 'SampleAsset', {
  path: path.join(__dirname, 'sample-asset-directory')
});

The following JavaScript example defines a file asset, which is uploaded as-is to an S3 bucket during deployment.

const asset = new assets.FileAsset(this, 'SampleAsset', {
  path: path.join(__dirname, 'file-asset.txt')
});

Attributes

Asset constructs expose the following deploy-time attributes:

In the following example, the various asset attributes are exported as stack outputs:

    const asset = new assets.ZipDirectoryAsset(this, 'SampleAsset', {
      path: path.join(__dirname, 'sample-asset-directory')
    });

    new cdk.CfnOutput(this, 'S3BucketName', { value: asset.s3BucketName });
    new cdk.CfnOutput(this, 'S3ObjectKey', { value: asset.s3ObjectKey });
    new cdk.CfnOutput(this, 'S3URL', { value: asset.s3Url });

Permissions

IAM roles, users or groups which need to be able to read assets in runtime will should be granted IAM permissions. To do that use the asset.grantRead(principal) method:

The following examples grants an IAM group read permissions on an asset:

const group = new iam.Group(this, 'MyUserGroup');
asset.grantRead(group);

How does it work?

When an asset is defined in a construct, a construct metadata entry aws:cdk:asset is emitted with instructions on where to find the asset and what type of packaging to perform (zip or file). Furthermore, the synthesized CloudFormation template will also include two CloudFormation parameters: one for the asset's bucket and one for the asset S3 key. Those parameters are used to reference the deploy-time values of the asset (using { Ref: "Param" }).

Then, when the stack is deployed, the toolkit will package the asset (i.e. zip the directory), calculate an MD5 hash of the contents and will render an S3 key for this asset within the toolkit's asset store. If the file doesn't exist in the asset store, it is uploaded during deployment.

The toolkit's asset store is an S3 bucket created by the toolkit for each environment the toolkit operates in (environment = account + region).

Now, when the toolkit deploys the stack, it will set the relevant CloudFormation Parameters to point to the actual bucket and key for each asset.

CloudFormation Resource Metadata

NOTE: This section is relevant for authors of AWS Resource Constructs.

In certain situations, it is desirable for tools to be able to know that a certain CloudFormation resource is using a local asset. For example, SAM CLI can be used to invoke AWS Lambda functions locally for debugging purposes.

To enable such use cases, external tools will consult a set of metadata entries on AWS CloudFormation resources:

  • aws:asset:path points to the local path of the asset.
  • aws:asset:property is the name of the resource property where the asset is used

Using these two metadata entries, tools will be able to identify that assets are used by a certain resource, and enable advanced local experiences.

To add these metadata entries to a resource, use the asset.addResourceMetadata(resource, property) method.

See https://github.com/awslabs/aws-cdk/issues/1432 for more details

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

aws-cdk.assets-0.27.0.tar.gz (37.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

aws_cdk.assets-0.27.0-py3-none-any.whl (34.9 kB view details)

Uploaded Python 3

File details

Details for the file aws-cdk.assets-0.27.0.tar.gz.

File metadata

  • Download URL: aws-cdk.assets-0.27.0.tar.gz
  • Upload date:
  • Size: 37.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5

File hashes

Hashes for aws-cdk.assets-0.27.0.tar.gz
Algorithm Hash digest
SHA256 0dc2f630f45235fed0005425463e4703ed60ab18be40364a11f3fdd5009c44f8
MD5 f3868ccbcd2afa366a9920de198c5ea9
BLAKE2b-256 7e4ac3ce4e9442c3b80efeb039f094f71ac881f55cce022516d6c3d3a669b795

See more details on using hashes here.

File details

Details for the file aws_cdk.assets-0.27.0-py3-none-any.whl.

File metadata

  • Download URL: aws_cdk.assets-0.27.0-py3-none-any.whl
  • Upload date:
  • Size: 34.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5

File hashes

Hashes for aws_cdk.assets-0.27.0-py3-none-any.whl
Algorithm Hash digest
SHA256 5eefc9b11a64ef19c83809a9459ae64a5d1df6faef58b6cf0ee68b6d637ac610
MD5 ae92aa830c96eaca337a209cd78deda0
BLAKE2b-256 651df3ae433f0ad434d046270a3f9f6d147f2130c4b7dbb0bad7d4d94bd7b64e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page