- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
You can use L1 constructs instead of L2 and sometimes it is an easier approach. There are resources that don't have a corresponding L2 construct and in such cases, it is easier to use L1 constructs. Reviewing the construct best practices, there is nothing specifically for L1 vs. L2. Often, L2 constructs make it easier to deploy multiple resources within a single construct.
Speaking of getting attributes, you can take a look at the package source code or run cdk synth
to generate a CloudFormation template to identify resources/parameters.
The higher Construct level you go, the more abstraction you will see ie. more parameters are pre-defined in the underlying Construct Resources so it is easier for you to create a resource.
No particular best practice that I know of, but you can see more L1 Construct options rather than L2.
Here you go for reference: https://docs.aws.amazon.com/cdk/v2/guide/cfn_layer.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren