Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect to deployed environment without redeploying #965

Closed
patchwork01 opened this issue Jul 6, 2023 · 0 comments · Fixed by #973
Closed

Connect to deployed environment without redeploying #965

patchwork01 opened this issue Jul 6, 2023 · 0 comments · Fixed by #973
Assignees
Milestone

Comments

@patchwork01
Copy link
Collaborator

patchwork01 commented Jul 6, 2023

Currently the documentation says to run sleeper environment deploy to add a second user to a deployed environment. This will run cdk deploy.

The Amazon Machine Image (AMI) for the EC2 is looked up with a wildcard under Ubuntu images of a certain distribution. If a new image has been published since the last time the EC2 was deployed, the CDK will detect that the image isn't the same as what's in the EC2, and will delete and recreate the EC2.

We'd like a way to add a second user to a deployed environment without risking recreating the EC2.

One way to do that would be to get the outputs for each stack from CloudFormation rather than from the CDK. In an issue asking for a way to do this in the CDK, there's a suggestion for how to look that up in CloudFormation: aws/aws-cdk#1773 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant