Setting up infra for a stack in the service pipeline

To set up infrastructure in your preInteg account before adding it to your service pipeline, you'll need to bootstrap the account and configure cross-account deployment capabilities in your CDK application. Here's how to approach this:

1. First, bootstrap your preInteg account to prepare it for CDK deployments, establishing a trust relationship with your pipeline account:

cdk bootstrap aws://<PREINTEG-ACCOUNT-NUMBER>/<REGION> --profile <PREINTEG-PROFILE> --trust <PIPELINE-ACCOUNT-NUMBER>

2. Update your CDK context configuration (cdk.context.json) to include the preInteg environment:

{
"preInteg": {
"account": "<PREINTEG-ACCOUNT-ID>",
"region": "<REGION>"
},
"other-environments": {
// Your existing environments
}
}

3. In your CDK application, modify your stack definition to support deployment to the preInteg account. You'll need to specify the account and region when defining your stack:

new YourStack(app, 'PreIntegStack', {
env: {
account: app.node.tryGetContext('preInteg').account,
region: app.node.tryGetContext('preInteg').region
},
// Other stack properties for your load testing infrastructure
});

4. If you're using a CI/CD pipeline construct (like SparkEmrCICDPipeline or similar), you'll need to add the preInteg stage to your pipeline definition.

For load testing specifically, ensure your stack includes the necessary resources such as compute capacity, networking, and any other components needed for your testing scenario.

Once you've successfully deployed and tested the infrastructure in the preInteg account, you can then integrate it into your service pipeline as a formal stage.
Sources
Streamline Spark application development on Amazon EMR with the Data Solutions Framework on AWS | AWS Big Data Blog
Streamlining AWS Glue Studio visual jobs: Building an integrated CI/CD pipeline for seamless environment synchronization | AWS Big Data Blog