1 Answer
- Newest
- Most votes
- Most comments
0
Check you code that defines the stack and env. I am betting that you have defined the Dev account as the env to deploy the stack to but are running cdk deploy
in your staging account.
For example
import 'source-map-support/register';
import { App } from 'aws-cdk-lib';
import { WorkspacesStack } from '../lib/workspaces-stack';
const app = new App();
const sharedStack = new WorkspacesStack(app, 'WorkspacesStack', {
env: {
account: '123456789012' <<< I am betting that you have your DEV Account ID there but trying to deploy to your staging account.
region: 'us-east-1',
},
});
If your intent to just be able to take your cdk and run those commands in any account. Then you will want to use new process.env.CDK_DEFAULT_ACCOUNT as detailed in the CDK Environment docs
MyDevStack(app, 'dev', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION
}});
Otherwise if you are looking to build a pipeline you will want to look at bootstrapping with using the --trust parameter and CDK Pipelines
answered 2 years ago
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago