@robhan-cdk-lib/aws_aps
AWS Cloud Development Kit (CDK) constructs for Amazon Managed Service for Prometheus.
In aws-cdk-lib.aws_aps, there currently only exist L1 constructs for Amazon Managed Service for Prometheus.
While helpful, they miss convenience like:
- advanced parameter checking (min/max number values, string lengths, array lengths...) before CloudFormation deployment
- proper parameter typing, e.g. enum values instead of strings
- simply referencing other constructs instead of e.g. ARN strings
Those features are implemented here.
The CDK maintainers explain that publishing your own package is "by far the strongest signal you can give to the CDK team that a feature should be included within the core aws-cdk packages".
This project aims to develop aws_aps constructs to a maturity that can potentially be accepted to the CDK core.
It is not supported by AWS and is not endorsed by them. Please file issues in the GitHub repository if you find any.
Example use
import * as cdk from 'aws-cdk-lib';
import { Subnet } from 'aws-cdk-lib/aws-ec2';
import { Cluster } from 'aws-cdk-lib/aws-eks';
import { Construct } from 'constructs';
import { Workspace, RuleGroupsNamespace, Scraper } from '@robhan-cdk-lib/aws_aps';
export class AwsApsCdkStack extends cdk.Stack {
constructor(scope: Construct, id: string, props?: cdk.StackProps) {
super(scope, id, props);
const workspace = new Workspace(this, 'MyWorkspace', {});
new RuleGroupsNamespace(this, 'MyRuleGroupsNamespace', { workspace, data: '<myRulesFileData>', name: 'myRuleGroupsNamespace' });
new Scraper(this, 'MyScraper', {
destination: {
ampConfiguration: {
workspace,
},
},
source: {
eksConfiguration: {
cluster: Cluster.fromClusterAttributes(this, 'MyCluster', {
clusterName: 'clusterName',
}),
subnets: [
Subnet.fromSubnetAttributes(this, 'MySubnet', {
subnetId: 'subnetId',
}),
],
},
},
scrapeConfiguration: {
configurationBlob: '<myScrapeConfiguration>',
},
});
}
}
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for robhan-cdk-lib.aws-aps 0.0.351
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| robhan_cdk_lib_aws_aps-0.0.351.tar.gz | 117.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| robhan_cdk_lib_aws_aps-0.0.351-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 234.3 kB
Release files / robhan_cdk_lib_aws_aps-0.0.351.tar.gz
| Download URL | robhan_cdk_lib_aws_aps-0.0.351.tar.gz |
|---|---|
| Size | 117.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55d08b00dce69c932b80abed6ebe49ef41e6c9030b360e2dee37c81109a390dc
|
|
BLAKE2b-256 checksum How to use checksums |
04122d70aa542f6decc32239e4ef1ed384cf71472276a207b20a2c3e562fbb65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.14.7
|
Release files / robhan_cdk_lib_aws_aps-0.0.351-py3-none-any.whl
| Download URL | robhan_cdk_lib_aws_aps-0.0.351-py3-none-any.whl |
|---|---|
| Size | 116.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11d83b60fa55c596b6ae8ed5fdab15113c59e676b962e2a1a48aff65006f7ddf
|
|
BLAKE2b-256 checksum How to use checksums |
af32aee26cdcff5a7c93c2c0b273f2c0afc9b291e141c90db2fb02ae6577d9e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.14.7
|
Security for robhan-cdk-lib.aws-aps 0.0.351
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
