This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Issue creating s3 bucket on Mac #715
Comments
It seems that the bootstrap part now with CDK v2 needs to happen for any CDK usage (previously it was only needed for the second stack, which has a larger template). Can you run it in this order?
|
Thanks for the quick response! If I do that, I get this after the first command.
|
Alright, checking it now myself with a blank region. This works:
Unfortunately this was not catched in the tests, because bootstrap is a per-account-and-region operation therefore the account we use for CI stays bootstrapped between CI runs. Right now it's not even possible to destroy the bootstrap resources. |
Repository owner
moved this from In Progress
to Done
in nRF Asset Tracker Development
Jan 21, 2022
coderbyheart
added a commit
that referenced
this issue
Jan 21, 2022
Resources created during bootstrap are now referenced by all CDK deploy operations. See #715
@rohandkn kindly confirm fix. |
Yes, that fixed it. Thank you! |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm attempting to install the nRF Asset Tracker into my AWS account. Upon reaching this command, I reach the following error.
npx cdk -a 'node dist/cdk/cloudformation-sourcecode.js' deploy
❌ nrf-asset-tracker-sourcecode failed: Error: nrf-asset-tracker-sourcecode: SSM parameter /cdk-bootstrap/hnb659fds/version not found. Has the environment been bootstrapped? Please run 'cdk bootstrap' (see https://docs.aws.amazon.com/cdk/latest/guide/bootstrapping.html)
I am running on a Mac. I also see the following warning beforehand.
current credentials could not be used to assume 'arn:aws:iam::...:role/...-us-east-2', but are for the right account. Proceeding anyway.
Direnv appears to properly exporting the AWS access tokens and I don't see any clear errors there. Has anyone seen a similar issue? Thank you!
The text was updated successfully, but these errors were encountered: