Skip to content

Maintenance: refactor SSM SecureString to AwsCustomResource #1316

Closed
@dreamorosi

Description

@dreamorosi

Summary

Currently as part of the integration tests of the Parameters utility we are creating a number of resources. For SSMProvider specifically we are creating some SSM SecureString resources.

CDK doesn't have any dedicated L2 construct for this type of resource and so, the current implementation of the tests relies on a custom resource backed by AWS Lambda to create the secure strings.

Why is this needed?

The current implementation requires us to maintain a dedicated Lambda function, which has the single purpose of creating and deleting a given SecureString resource.

Which area does this relate to?

Tests, Parameters

Solution

Refactor this custom resource to use AwsCustomResource instead. This will allow us to not have to manage a custom resource and provider, and thus delegate the responsibility to CDK.

Acknowledgment

Metadata

Metadata

Assignees

Labels

completedThis item is complete and has been merged/shippedparametersThis item relates to the Parameters UtilitytestsPRs that add or change tests

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions