Currently I package my Serverless stack in an environment without any AWS credentials. And then feed the .serverless folder to a separate CD job which deploys the package.
However, I found that serverless-vpc-plugin doesn't work without AWS access: it uses a few AWS API calls to collect essentially static metadata, such as the IP prefixes for firewall config and the list of available endpoints.
Is it possible to add an option to provide that metadata statically, so serverless package runs without any AWS access?
Currently I package my Serverless stack in an environment without any AWS credentials. And then feed the
.serverless
folder to a separate CD job which deploys the package.However, I found that
serverless-vpc-plugin
doesn't work without AWS access: it uses a few AWS API calls to collect essentially static metadata, such as the IP prefixes for firewall config and the list of available endpoints.Is it possible to add an option to provide that metadata statically, so
serverless package
runs without any AWS access?