aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

AWS::DeploymentBucket - New Pseudo Parameter

Open
#1,690 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

Other

### Resource name

AWS::DeploymentBucket

### Description

Many AWS QuickStarts (and other solutions) rely on their own bucket name being passed into them as a parameter.

https://aws-quickstart.github.io/design-parms.html#qsconfig

This allows them to reference S3build artifacts as part of the deployment. E.g. Content for static websites.

However, it's a bit redundant. All CloudFormation stacks get deployed from S3. The simple addition of a new pseudo param which pointed to that deployment would allow developers to reference S3 resources without the need for a user-supplied parameter.

**Stretch goal**
Update `aws cloudformation package` to use this new parameter in place of hard-coded URIs. This would allow CloudFormation packages to be moved between buckets or even **in and out of an artifact repo** without breaking hard-coded references.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the AWS Quick Starts parameter guidance linked in the issue and the behavior of AWS CloudFormation pseudo parameters. Then investigate how `aws cloudformation package` currently emits hard-coded S3 URIs; done means defining and implementing the new `AWS::DeploymentBucket` parameter, with the packaging update treated as a stretch goal.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.