Hey, we are running our full production setup on A...
# guide
p
Hey, we are running our full production setup on AWS-CDK without SST currently. We’re very interested into using SST for development, but would not want to touch our production setup. Is there a guide how to / is anyone using SST for development only, but using “pure” aws-cdk for production?
k
@p0wl While not mentioned in the CDK migration, I think you could do something similar to a partial serverless migration by importing just the resources you need for development / testing and then use SST for function debugging ect. https://docs.serverless-stack.com/migrating/serverless-framework#migrate-only-the-functions
Normally, SST also creates stage prefixed resources, but using
...from[something]
references removes that isolation. This might not be a god choice though for critical infrastructure and probably means you have to recreate at least some of it or proper isolation when testing out new stuff.
f
Thanks @Klaus!
Hey @p0wl, as @Klaus suggested, while it is possible to defined some infrastructure in SST only for dev environments, it is not ideal. You want to ensure dev mirrors prod as closely as possible.
k
@p0wl I just remembered 1 other potential caveat that comes with debugging - in order to allow you the local live reload experience, the
real lambda functions are replaced by a generic stub that forwards the request via web socket
. While this is wonderful for development, it also means you
must recreate any production functions you are debugging
(create a duplicate) before using this approach. Otherwise, the dev machine debugging the code could become a bottle-neck if you are testing during times when the production workflows should be running.