For support requests please search or create posts on Serverless Forum: https://forum.serverless.com
The error is:
An error occurred: HttpApiStage - Cannot enable logging. Policy document length breaking Cloudwatch Logs Constraints, either < 1 or > 5120 (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: b47af8e7-47d7-4921-baf8-87de0f8ba253; Proxy: null).
serverless <something> command, it always seems to want to resolve secrets before executing the task I tell serverless to run, even if it's just using a local plugin that has no reason to use the environment variables I have stored with my cloud provider.What exactly happens when you use a
serverless <something> command, anyway? I'd like to disable resolving every bit of the config if I'm just trying to do something simple & local. Then I can save config validation for a separate command I can wrap up into other scripts/pipeline steps.
post is not workingserverless has any issue
user-xxx:
events:
- http:
path: xxx
method: post
cors: true
private: true
- http:
path: xxx/{sub_id}
method: get
cors: true
private: true
- http:
path: xxx/{sub_id}
method: post
cors: true
private: true
Je travail actuellement sur un projet lamda avec serverless, qui possède pas mal de event scheduled (cron) et il semble que serverless créer/rajoute une ligne de policy pour chaque event.
Malheuresement, on tombe maintenant sur cette erreur: "The final policy size is bigger than the limit"
N'étant pas très calé en serverless, je voudrai savoir si il y a un moyen de gérer manuellement ou de pouvoir dire a serverless de faire des règle de policy plus global avec des * plutot qu'il me génère une nouvelle règle de policy pour chaque event ?
Hey guys!
I'm having a problem when I try to run the start step function in another lambda function.
my code:
await stepfunctions.startExecution(params).promise();
But, he response nothing.
I've already increased the lambda execution time, but it's still not running.
@/all
Hi all,
We're doing a free Webinar on October 5th on Enabling Serverless Teams (AKA how to standardize serverless development amidst a growing group of developers).
You can register here: https://app.livestorm.co/serverless/enabling-serverless-teams
Has anyone had this error when trying to run a state machine?
{
errno: 'ETIMEDOUT',
code: 'TimeoutError',
syscall: 'connect',
port: 443,
time: 2021-09-28T20:22:32.335Z,
region: 'us-east-2',
hostname: 'states.us-east-2.amazonaws.com',
retryable: true
}
Hi everyone - How can I try out the new AWS Graviton2 Processor?
npm audit fix i wonder if anyone else is facing this issue and if there's a work around for this! Thanks https://snyk.io/test/github/serverless/serverless
@/all
We just released Serverless Cloud into Public Preview, and it's now available to everyone!
- 500ms deployments,
- Instantly forkable apps (into isolated AWS accounts)
- Rapidly create Preview and Test instances of your apps.
- And much more make it a game-changer for serverless application development.
https://www.serverless.com/blog/introducing-serverless-cloud-public-preview
Let us know what you think!
BlobsResource:
Type: AWS::ApiGateway::Resource
Properties:
RestApiId:
Ref: ApiGatewayRestApi
ParentId:
Fn::GetAtt:
- ApiGatewayRestApi
- RootResourceId
PathPart: '{blob_id}'when I change this Ref: ApiGatewayRestApi to Ref: blobs it says undefined blobs resource
aws command line, but sls deploy complains that the profile isn't configured. Are such role-based profiles supported by serverless at all?
Hi am running into an issue where my env vars aren't being expanded when my cloud formation json is being created:
service: ${env:FOO, "foo-default"}${env:BAR, ""}
...
apiGateway:
name: ${env:FOO, "foo-default"}${env:BAR, ""}
...
provider:
stackName: ${self:service}When I generate the cloud formation json it's creating these values:
"Export": {
"Name": "sls-${env:FOO, \"foo-default\"}${env:BAR, \"\"}-dev"
},Basically It's treating the env vars as plain text. Should I report this as a bug or am I doing something wrong?
