Saravanan666/pypi-org huggingface dataset:
Package: aws-cdk.aws-transfer
AWS Transfer for SFTP Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_transferastransferThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for Transfer construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::Transfer resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::Transfer.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-voiceid
AWS::VoiceID Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_voiceidasvoiceidThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for VoiceID construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::VoiceID resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::VoiceID.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-vpclattice
AWS::VpcLattice Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_vpclatticeasvpclatticeThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for VpcLattice construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::VpcLattice resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::VpcLattice.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-waf
AWS Web Application Firewall Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_wafaswafThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for WAF construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::WAF resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::WAF.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-wafregional
AWS WAF Regional Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_wafregionalaswafregionalThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for WAFRegional construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::WAFRegional resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::WAFRegional.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-wafv2
AWS::WAFv2 Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_wafv2aswafv2There are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for WAFv2 construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::WAFv2 resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::WAFv2.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-wisdom
AWS::Wisdom Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_wisdomaswisdomThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for Wisdom construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::Wisdom resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::Wisdom.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-workspaces
Amazon WorkSpaces Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_workspacesasworkspacesThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for WorkSpaces construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::WorkSpaces resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::WorkSpaces.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk.aws-xray
AWS::XRay Construct Library---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module is part of theAWS Cloud Development Kitproject.importaws_cdk.aws_xrayasxrayThere are no official hand-written (L2) constructs for this service yet. Here are some suggestions on how to proceed:SearchConstruct Hub for XRay construct librariesUse the automatically generatedL1constructs, in the same way you would usethe CloudFormation AWS::XRay resourcesdirectly.There are no hand-written (L2) constructs for this service yet.
However, you can still use the automatically generatedL1constructs, and use this service exactly as you would using CloudFormation directly.For more information on the resources and properties available for this service, see theCloudFormation documentation for AWS::XRay.(Read theCDK Contributing Guideand submit an RFC if you are interested in contributing to this construct library.)
Package: aws-cdk-billing-alarm
aws-cdk-billing-alarmA CDK construct that sets up email notification for when you exceed a given AWS estimated charges amount.Create this construct in any stack you find appropriatewith only a few lines. This construct is an implementation of the manual
setup described onAWS Estimated Charges Monitoring.Get StartedPre-RequisitesIMPORTANT!Only completeStep 1: Enable Billing Alertsof the following documentation link. This construct will take
care of creating the rest of the resources for you.You must first enable billing alerts from the AWS Console as perdocumentation.Billing alerts will allow your AWS account to start collecting billing metrics (EstimatedCharges) on a periodic 6-hour basis.InstallationNode documentationnpminstall--saveaws-cdk-billing-alarmPython documentationpipinstallaws-cdk-billing-alarmUsage# Example automatically generated from non-compiling source. May contain errors.import{Stack,StackProps}from'aws-cdk-lib';import{Construct}from'constructs';import{BillingAlarm}from'aws-cdk-billing-alarm';classCdkStackextendsStack{constructor(scope:Construct,id:string,props?:StackProps){super(scope,id,props);//Createanalarmthatemails`admin@example.com`//ifestimatedchargesexceed50USDnewBillingAlarm(this,'AWSAccountBillingAlarm',{monthlyThreshold:50,emails:['admin@example.com'],});}}Post-DeploymentConfirm the subscription to the newly created topic for the emails you specified as endpoints inBillingAlarmProps.
You can do so by clicking on theSubscribeURLof the JSON email you received.Note: If you did not receive the email, you can fire aRequest confirmationfor the subscription from the AWS SNS Console.LimitationsUSD currency
Package: aws-cdk-build-badge
tested cdk versionsaws-cdk-build-badgeThis an AWS CDK custom construct for get the status of a CodeBuild Project with has CodePipeline as source. That is currently not possible:https://github.com/aws/aws-cdk/issues/1749How the native badges are working you find in the AWS docs:https://docs.aws.amazon.com/codebuild/latest/userguide/sample-build-badges.htmlAfter you created the build badge construct you can use the api gateway url to get the badge picture. Additionally you can retrieve the url to to the CodeBuild build with adding ?url=true to the query parameter. See the example.URL to BuildIf you want your badge forwarding you to your build when you click on it use the url=true parameter:Build succeeded: [![CodeBuild test build](https://fktijpwdng.execute-api.eu-central-1.amazonaws.com/prod/?projectName=PipelineCustomStageprodTest-Fdei5bm2ulR6)](https://fktijpwdng.execute-api.eu-central-1.amazonaws.com/prod/?projectName=PipelineCustomStageprodTest-Fdei5bm2ulR6&url=true)Default project nameYou can use thedefaultProjectNamein the cdk construct to point the badge to a specific project. That way you don't need to write the projectName parameter in thr url.new BuildBadge(stack, 'BuildBadge2', { defaultProjectName: 'Build123' });ExampleBuild succeeded:Build failed:Build not found:Build in progress:Build stopped:There are more badges (see ./badges/) but I don't have build in that state atm.# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826app=cdk.App()stack=cdk.Stack(app,"my-build-badge-demo-stack")# without exposing the account id in the url when using ?url=trueBuildBadge(stack,"BuildBadge")# with exposing the account id in the url when using ?url=trueBuildBadge(stack,"BuildBadge2",hide_account_iD="no")# partly exposing the account id in the url when using ?url=trueBuildBadge(stack,"BuildBadge3",hide_account_iD="XX123356")Thanks ToThe CDK Community cdk-dev.slack.comProjenproject and the community around ithttps://github.com/btorun/aws-codebuild-badges...
Package: aws-cdk.cli-lib-alpha
AWS CDK CLI Library---The APIs of higher level constructs in this module are experimental and under active development.
They are subject to non-backward compatible changes or removal in any future version. These are
not subject to theSemantic Versioningmodel and breaking changes will be
announced in the release notes. This means that while you may use them, you may need to update
your source code when upgrading to a newer version of this package.⚠️ Experimental moduleThis package is highly experimental. Expect frequent API changes and incomplete features.
Known issues include:JavaScript/TypeScript onlyThe jsii packages are currently not in a working state.No useful return valuesAll output is currently printed to stdout/stderrMissing or Broken optionsSome CLI options might not be available in this package or brokenOverviewProvides a library to interact with the AWS CDK CLI programmatically from jsii supported languages.
Currently the package includes implementations for:cdk deploycdk synthcdk bootstrapcdk destroycdk listSetupAWS CDK app directoryObtain anAwsCdkCliclass from an AWS CDK app directory (containing acdk.jsonfile):cli=AwsCdkCli.from_cdk_app_directory("/path/to/cdk/app")Cloud Assembly Directory ProducerYou can also createAwsCdkClifrom a class implementingICloudAssemblyDirectoryProducer.
AWS CDK apps might need to be synthesized multiple times with additional context values before they are ready.Theproduce()method of theICloudAssemblyDirectoryProducerinterface provides this multi-pass ability.
It is invoked with the context values of the current iteration and should use these values to synthesize a Cloud Assembly.
The return value is the path to the assembly directory.A basic implementation would look like this:@jsii.implements(ICloudAssemblyDirectoryProducer)classMyProducer:defproduce(self,context):app=cdk.App(context=context)stack=cdk.Stack(app)returnapp.synth().directoryFor all features (e.g. lookups) to work correctly,cdk.App()must be instantiated with the receivedcontextvalues.
Since it is not possible to update the context of an app, it must be created as part of theproduce()method.The producer can than be used like this:cli=AwsCdkCli.from_cloud_assembly_directory_producer(MyProducer())Commandslist# await this asynchronous method call using a language featurecli.list()synth# await this asynchronous method call using a language featurecli.synth(stacks=["MyTestStack"])bootstrap# await this asynchronous method call using a language featurecli.bootstrap()deploy# await this asynchronous method call using a language featurecli.deploy(stacks=["MyTestStack"])destroy# await this asynchronous method call using a language featurecli.destroy(stacks=["MyTestStack"])
Package: aws-cdk.cloud-assembly-schema
Cloud Assembly SchemaThis module is part of theAWS Cloud Development Kitproject.Cloud AssemblyTheCloud Assemblyis the output of the synthesis operation. It is produced as part of thecdk synthcommand, or theapp.synth()method invocation.Its essentially a set of files and directories, one of which is themanifest.jsonfile. It defines the set of instructions that are
needed in order to deploy the assembly directory.For example, whencdk deployis executed, the CLI reads this file and performs its instructions:Build container images.Upload assets.Deploy CloudFormation templates.Therefore, the assembly is how the CDK class library and CDK CLI (or any other consumer) communicate. To ensure compatibility
between the assembly and its consumers, we treat the manifest file as a well defined, versioned schema.SchemaThis module contains the typescript structs that comprise themanifest.jsonfile, as well as the
generatedjson-schema.VersioningThe schema version is specified in thecloud-assembly.version.jsonfile, under theversionproperty.
It follows semantic versioning, but with a small twist.When we add instructions to the assembly, they are reflected in the manifest file and thejson-schemaaccordingly.
Every such instruction, is crucial for ensuring the correct deployment behavior. This means that to properly deploy a cloud assembly,
consumers must be aware of every such instruction modification.For this reason, every change to the schema, even though it might not strictly break validation of thejson-schemaformat,
is consideredmajorversion bump.How to consumeIf you'd like to consume theschema filein order to do validations onmanifest.jsonfiles,
simply download it from this repo and run it against standardjson-schemavalidators, such asjsonschema.Consumers must take into account themajorversion of the schema they are consuming. They should reject cloud assemblies
with amajorversion that is higher than what they expect. While schema validation might pass on such assemblies, the deployment integrity
cannot be guaranteed because some instructions will be ignored.For example, if your consumer was built when the schema version was 2.0.0, you should reject deploying cloud assemblies with a
manifest version of 3.0.0.ContributingSeeContribution Guide
Package: aws-cdk-code-builder
AWS CDK Code BuilderThis library work very similarly to how AWSsam buildworks. It will find the requirements.txt file and install all libraries and package them together with your code to then ship to a lambda function.📝 CONTRIBUTIONSBefore doing any contribution readCONTRIBUTING.📧 CONTACTEmail:amng835@gmail.comGeneral Discord:https://discord.gg/dFD5HHaDeveloper Discord:https://discord.gg/rxNNHYN9EQ📥 INSTALLINGLatest PyPI stable releasepipinstallaws-cdk-code-builder⚙ HOW TO USEFolder tree (Simplified)cdk_project
     | -- lambda_function
     |          | -- main.py
     | -- cdk_project
     |         | -- __init__.py
     |         | -- cdk_project_stack.py
     | -- app.py
     | -- ...File:cdk_project_stack.pyimportosimportaws_cdkfromaws_cdkimportaws_lambdaaslambda_fromaws_cdk_code_builderimportBuildCURRENT_DIR=os.path.dirname(os.path.abspath(__file__))PARENT_PATH=os.path.dirname(CURRENT_DIR)LAMBDA_CODE=os.path.join(PARENT_PATH,'lambda_function')classCdkProjectStack(aws_cdk.Stack):def__init__(self,scope:aws_cdk.Construct,construct_id:str,**kwargs)->None:super().__init__(scope,construct_id,**kwargs)# This is a simplified representation of Function, more params are needed for it to compilelambda_.Function(code=Build(project_path=LAMBDA_CODE,work_dir=PARENT_PATH).build(),)🤝 PARAMETERSproject_path : str, requiredPath to the lambda function codework_dir : str, requiredPath to the working directory.Note: Build folder will be created in this path (build/)
Package: aws-cdk-dynamodb-seeder
aws-cdk-dynamodb-seederA simple CDK JSON seeder for DynamoDBWhy this packageGlad you asked!UsingAWS CDKfor automating infrastructure deployments is an amazing way of integrating the development and operations into one process and one codebase.However, building dev or test environments that come pre-populated with data can be tricky, especially when usingAmazon DynamoDB.How do I use itInstall using your favourite package manager:yarnaddaws-cdk-dynamodb-seederExample TypeScript usage# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826fromaws_cdk_dynamodb_seederimportSeedermy_table=Table(stack,"MyTable",table_name="MyTable",partition_key={"name":"Id","type":AttributeType.STRING})Seeder(stack,"MySeeder",table=my_table,setup=require("./items-to-put.json"),teardown=require("./keys-to-delete.json"),refresh_on_update=True)For a more in-depth example, see:elegantdevelopment/aws-cdk-dynamodb-seeder-examples.Importing seed dataData passed intosetup("Items" to put) orteardown("Keys" to delete) should be anarrayof objects (that are, in turn, representations ofstringtoAttributeValuemaps).setupelements should use the format ofparams.ItemfromAWS.DynamoDB.DocumentClient.put()teardownelements should use the format ofparams.KeyfromAWS.DynamoDB.DocumentClient.delete()VersioningWe willattemptto align the major and minor version of this package withAWS CDK, but always check our release descriptions for compatibility.We currently supportInternalsBehind the scenes we use anAwsCustomResourceas a representation of the related table's seed state. The custom resource's event handlers invoke aFunctionto perform setup and/or teardown actions.Deploying a stackOn deployment, we write copies of your seed data locally and use aBucketDeploymentto write it to an S3Bucket.We then create the handler function and custom resource to field seed requests (theonCreateevent will immediate fire as the stack deploys, reading the data from the bucket and seeding the table usingAWS.DynamoDB.DocumentClient).Updating a stackOn a stack update, theonUpdatehandler is triggered whenrefreshOnUpdateistrue.This will runAWS.DynamoDB.DocumentClient.delete()on every teardown "Key" followed byAWS.DynamoDB.DocumentClient.put()on every setup "Item".Destroying a stackWhen the stack is destroyed, the event handler'sonDeletefunction will be invoked, providingteardownis set.This simply runsAWS.DynamoDB.DocumentClient.delete()on every teardown "Key" before destroying theSeeder's resources.
Package: aws-cdk-featureflags
aws-cdk-featureflagsAnAWS CDKfeature flag implementation:exclamation: WIP :exclamation:This package is aWORK IN PROGRESS, please make sure you're not using this until we've reached at least v1.0.0.Why this packageFor when you want feature flags.How do I use itInstall using your favourite package manager:yarnaddaws-cdk-featureflagsExample TypeScript usage# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826fromaws_cdk_featureflagsimportFeatureFlagsfeature_flags=FeatureFlags(self,"featureflags")Function(self,"my-function",code=Code.from_asset("./my-function"),handler="index.handler",environment={"FEATURE_FLAGS_URL":feature_flags.url})VersioningCurrently pre-release. Check back when we've reached at least 1.0.0!
Package: aws-cdk.lambda-layer-awscli
AWS Lambda Layer with AWS CLI---AWS CDK v1 has reached End-of-Support on 2023-06-01.
This package is no longer being updated, and users should migrate to AWS CDK v2.For more information on how to migrate, see theMigrating to AWS CDK v2guide.This module exports a single class calledAwsCliLayerwhich is alambda.Layerthat bundles the AWS CLI.Any Lambda Function that uses this layer must use a Python 3.x runtime.Usage:# AwsCliLayer bundles the AWS CLI in a lambda layerfromaws_cdk.lambda_layer_awscliimportAwsCliLayer# fn: lambda.Functionfn.add_layers(AwsCliLayer(self,"AwsCliLayer"))The CLI will be installed under/opt/awscli/aws.