Fifo queue without name in nested stack fails to create
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 74
Description
### Reproduction Steps
```
import cdk = require('@aws-cdk/core');
import { NestedStack } from '@aws-cdk/aws-cloudformation';
import { Queue } from '@aws-cdk/aws-sqs';
export class CdkFifoQueueStack extends cdk.Stack {
constructor(scope: cdk.Construct, id: string, props?: cdk.StackProps) {
super(scope, id, props);
new MyNestedStack(this, 'NestedStack');
}
}
export class MyNestedStack extends NestedStack {
constructor(scope: cdk.Construct, id: string) {
super(scope, id);
new Queue(this, 'MyQueue', {
fifo: true
});
}
}
```
[source](https://github.com/cmckni3/cdk-fifo-queue)
MUST USE `cdk deploy`. THE STACK SYNTHESIZES FINE.
### Error Log
CloudFormation error after running `cdk deploy`:
```
The name of a FIFO queue can only include alphanumeric characters, hyphens, or underscores, must end with .fifo suffix and be 1 to 80 in length. (Service: AmazonSQS; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 0079e079-6bf5-5eec-90d9-b6e4eebec170)
```
### Environment
- **CLI Version : 1.19.0**
- **Framework Version: 1.19.0**
- **OS : macOS**
- **Language : TypeScript**
---
This is :bug: Bug Report
Contributor guide
Research direction
Start with the Queue and NestedStack entry points shown in the reproduction, then run the provided cdk-fifo-queue example with cdk deploy rather than relying on synthesis alone. Compare the generated deployment behavior with the reported FIFO-name error; done means the nested FIFO queue deploys successfully without requiring an explicit name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100