The AWS CloudFormation Public Coverage Roadmap

Home Page: https://aws.amazon.com/cloudformation/

License: Creative Commons Attribution Share Alike 4.0 International

roadmap cloudformation aws-cloudformation cfn aws

cloudformation-coverage-roadmap's Introduction

CloudFormation Public Coverage Roadmap

The AWS CloudFormation Public Coverage Roadmap

Introduction

This is a public roadmap focused on upcoming coverage support for CloudFormation. It is focused on coverage additions to existing AWS services to be addressed by upcoming CloudFormation releases. It represents a preview of the information we provide in our existing release history documentation. Knowing about our upcoming coverage additions and priorities helps our customers plan, and we want to provide a way for our customers to help us ensure we are working on the most important requests.

See the roadmap »

Security disclosures

If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.

FAQs

Q: Why did you build this?

A: We know that our customers are making decisions and plans based on what we are developing, and we want to provide our customers the insights they need to plan. If our customers know that a coverage item is being worked on and will be released soon, we can help them avoid additional work if they are considering workarounds or custom resources to address their needs. Further, we want you to help us ensure we are working on the most important and impactful issues.

Q: Why are there no dates on your roadmap?

A: Because our main priority is security and operational stability, we cannot provide specific target dates for releases.

Q: What do the roadmap categories mean?

Shipped - currently usable in CloudFormation templates
Coming soon - nearing completion, likely being planned for an upcoming coverage update release. Think a couple of weeks out, give or take.
We're working on it - in progress, but further out. We might still be working through the implementation details, or scoping stuff out.
Researching - We're thinking about it. This might mean we're still evaluating designs and options, or thinking through how this should work. This is a great phase to give us feedback as to how you want to see something implemented! We’ll benefit from your specific use cases here.

Q: Is everything on the roadmap?

A: We are focusing on coverage updates for existing CloudFormation resource types, as well as new and previously available AWS services where there’s no native CloudFormation support yet. There is other coverage-related work that we won’t be able to preview. For example, services that are not publicly released yet will not appear on this roadmap. Finally, there are other non-coverage-related feature work that we won’t cover in this roadmap at this time.

Q: How can I provide feedback or ask for more information?

A: When in doubt, please create an issue! Although we’ll focus on coverage issues, all submitted issues will get reviewed and/or forwarded appropriately.

Q: How can I request a feature be added to the roadmap?

A: We encourage you to open an issue, even if you’ve requested it before via other channels. All community-submitted issues will be reviewed by the roadmap maintainers. We’ve created a template to make it easy to open new issues.

Q: Can I "+1" existing issues?

A: We strongly encourage you to vote on issues, as it helps us understand which issues will have the widest impact, but please don't leave comments saying "+1". Such comments generate noise for people receiving notifications, and issues can't be sorted by number of "+1" comments. Instead, leave a 👍 reaction, which is less noisy and can be used to sort issues for prioritization. To leave a reaction, navigate to the issue details page and add a reaction with the 😀 button on the post. There are six types of reactions supported (thumbs down "-1", confused, heart, watching, laugh, hooray, and thumbs up +1). We can typically do 8-10 items per month with all necessary regression testing, and we want you to help us decide which items will benefit you the most.

Community

Join us on Discord! Connect & interact with CloudFormation developers & experts, find channels to discuss and get help for cfn-lint, CloudFormation registry, StackSets, Guard and more:

License Summary

This project is made available under the CC-BY-SA-4.0 license. See the LICENSE file.

To learn more about the service, go here: http://aws.amazon.com/cloudformation

cloudformation-coverage-roadmap's People

Contributors

Stargazers

Watchers

cloudformation-coverage-roadmap's Issues

AWS::ACM::PCA - New Resource

Title -> AWS::ACM::PCA
Scope of request -> Manages an ACM Private CA Resource
Expected behavior -> Create, Update and Delete a Private CA
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/acm-pca/latest/APIReference/API_CreateCertificateAuthority.html
Category tag (optional) -> ACM

AWS::KinesisFirehose::DeliveryStream-ExtendedS3DestinationConfiguration & KinesisStreamSourceConfiguration (new property) Error Output Prefix

Title -> AWS::KinesisFirehose::DeliveryStream-ExtendedS3DestinationConfiguration & KinesisStreamSourceConfiguration
Scope of request -> AWS::KinesisFirehose::DeliveryStream-ExtendedS3DestinationConfiguration & KinesisStreamSourceConfiguration does not support Error Output Prefixes.
Expected behavior -> CloudFormation should allow customers to specify Error Output Prefixes on Kinsesis Firehose Delivery Streams
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/firehose/create-delivery-stream.html
Category tag (optional) -> Analytics
Any additional context (optional)

AWS::ElasticSearch:Domain (support Zone Awareness)

Title -> Customers want to set ZoneAwarenessConfig in Elastic Search
Scope of request -> Add two configuration options: ZoneAwarenessConfig and ZoneAwarenessEnabled
Expected behavior -> See API docs.
Test case recommendation (optional) ->
Links to existing API doc (optional) ->https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-configuration-api.html#es-configuration-api-datatypes-elasticsearchclusterconfig
Category tag (optional) -> Analytics
Any additional context (optional)

AWS::XRay::SamplingRule - New Resource

Title -> AWS::XRay::SamplingRule
Scope of request -> Manages X-Ray sampling rule resources
Expected behavior -> Create, Update and Delete X-Ray sampling rules
Test case recommendation (optional) ->

SamplingRule:
    Type: "AWS::XRay::SamplingRule"
    Properties:
        RuleName: "mySamplingRule"
        ResourceArn: "*"
        Priority: 10
        FixedRate: 0.05
        ReservoirSize: 1
        ServiceName: "*"
        ServiceType: "*"
        Host: "*"
        HttpMethod: "*"
        UrlPath: "*"
        Version: 1
        Attributes:
          - Key: "Origin"
            Value: "example.com"

Links to existing API doc (optional) -> https://docs.aws.amazon.com/xray/latest/api/API_CreateSamplingRule.html
Category tag (optional) -> Developer Tools, X-Ray

AWS::RDS (Aurora Cloning Support)

Quick Sample Summary:

Title -> Add Aurora cloning support within CloudFormation templates.
Scope of request -> Be able to set and update cloning properties when creating or updating Aurora databases.
Expected behavior -> Follow the options available via the console and CLI.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> Maybe similar functionality to
https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html
Category tag (optional) -> Databases
Any additional context (optional)

AWS::Glue::Job support setting MaxCapacity - new property

Title -> AWS::Glue::Job
Scope of request -> AWS::Glue::Job currently does not support setting the MaxCapacity. It only allows setting the AllocatedCapacity, which is officially deprecated in the documentation and does not have the effect to control the number of DPU's for a Glue Job.
Expected behavior -> It should be possible to set the MaxCapacity property for a Glue Job via CFN
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/glue/latest/dg/aws-glue-api-jobs-job.html
Category tag (optional) -> Glue

AWS::EC2::VPNConnection-TransitGatewayId (new property)

Title -> AWS::EC2::VPNConnection-TransitGatewayId (new property) to support Transit Gateway
Scope of request -> Allow this property to be supported via Cloudformation to support usage of Transit Gateway
Expected behavior -> When a user adds a TransitGatewayId, CloudFormation passes that Id to the VPN Connection request.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/ec2/create-vpn-connection.html
Category tag (optional) -> Compute
Any additional context (optional) -> Usage of Transit Gateway isn't sufficient until this requirement is satisfied.

AWS::S3::Bucket-Transition-StorageClass OneZoneIA & Intelligent Tiering

Title -> AWS::S3::Bucket-Transition-StorageClass OneZoneIA & Intelligent Tiering
Scope of request -> AWS::S3::Bucket-Transition-StorageClass support to be added for "OneZoneIA and Intelligent Tiering"
Expected behavior -> When creating an S3 Bucket Transition Policy, it should be possible to add OneZoneIA and Intelligent Tiering as an option for the Storage Class property
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-bucket-lifecycleconfig-rule-transition.html#aws-properties-s3-bucket-lifecycleconfig-rule-transition-properties
Category tag (optional) -> Storage
Any additional context (optional)

AWS::DynamoDB::Table (SSESpecification support)

Objective -> DynamoDB Encryption@Rest will now allow customers to update the SSESpecification of an existing tables with no interruption via the UpdateTable API and a SSESpecification.
Scope of request -> It's in public SDK now: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html#DDB-UpdateTable-request-SSESpecification
Expected behavior -> Match the public APIs.
Test case recommendation (optional) -> Match the public APIs.
Links to existing API doc (optional) -> See 2 above.
Category tag (optional) -> Database
Any additional context (optional) -> Existing customers leverage CloudFormation templates for creating/updating DynamoDB tables. Given we are allowing them to change their tables without delete, any existing customers that want to leverage the new feature using their CloudFormation templates, would need CloudFormation support for the same. It will enable easy adoption for the feature for our existing and new customers. Future and existing customers who wishes to specify KMSMasterKeyId will be able to specify and update KMSMasterKeyId without deleting their table.

AWS::KinesisFirehose::DeliveryStream-DataFormatConversion - (new property)

Title -> AWS::KinesisFirehose::DeliveryStream-DataFormatConversion
Scope of request -> Support new Data Formation Conversation (convert from JSON to parquet/ORC before writing to s3) in Kinesis Firehose
Expected behavior -> When creating a Kinesis Firehose, a customer should be able to specify the data conversion format
Test case recommendation (optional) -> when the stream dumps to an s3 bucket, the data should be in the parquet/orc format
Links to existing API doc (optional) -> https://docs.aws.amazon.com/firehose/latest/APIReference/API_CreateDeliveryStream.html
Category tag (optional) -> Analytics
Any additional context (optional)

AWS::RDS::DBInstance and AWS::RDS::DBCluster (add IAM role association)

Title -> RDS now supports the association of an AWS Identity and Access Management (IAM) role with a DB instance. It will be useful for our customers to have support for this feature within CloudFormation.
Scope of request -> Add roles when creating, and when updating existing resources.
Expected behavior -> See relevant documentation:

AddRoleToDBInstance: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_AddRoleToDBInstance.html
RemoveRoleFromDBInstance: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RemoveRoleFromDBInstance.html
AddRoleToDBCluster: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_AddRoleToDBCluster.html
RemoveRoleFromDBCluster: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RemoveRoleFromDBCluster.html

Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Databases
Any additional context (optional)

AWS::Organizations::OU - New Resources

Title -> AWS::Organizations::OU
Scope of request -> Create and manage a new OU inside an AWS Organization
Expected behavior -> A new OU is created and has the root parent OU or root
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/organizations/latest/APIReference/API_CreateOrganizationalUnit.html
Category tag (optional) -> Organizations

AWS::ApiGateway::- (multiple resources) (new tagging support)

Adding tag support for the following:

AWS::ApiGateway::RestApi
AWS::ApiGateway::VpcLink
AWS::ApiGateway::UsagePlan
AWS::ApiGateway::ApiKey
AWS::ApiGateway::ClientCertificate
AWS::ApiGateway::DomainName

Scope of request -> The resources above will support tags from CloudFormation.
Expected behavior -> In Create or Update, it should allow the creation of tags.
Test case recommendation (optional) -> Test for updating existing CloudFormation resources.
Links to existing API doc (optional) -> https://docs.aws.amazon.com/apigateway/api-reference/resource/api-key and others
Category tag (optional) -> Networking & Content Delivery
Any additional context (optional)

AWS::EC2::instance (specify KMSKeyID in EBS BlockDeviceMapping)

Title -> Specifying KMSKeyID for additional EBS data volumes through BlockDeviceMapping is already available via API.
Scope of request -> Allow specifying this in CloudFormation for EC2 instances.
Expected behavior -> see API.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EbsBlockDevice.html
Category tag (optional) -> Compute
Any additional context (optional)

AWS::ECS::Cluster & AWS::ECS::Service & AWS::ECS::TaskDefinition - support tagging

Title -> AWS::ECS::Cluster & AWS::ECS::Service & AWS::ECS::TaskDefinition - support tagging
Scope of request -> For all features of ECS, support tagging
Expected behavior -> when a tag gets added to any ECS resource, add that tag to the provisioned resource as well
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

AWS::EC2::Instance (set CPU options) (new attribute)

Title -> Allow CPU options to be specified during instance launch.
Scope of request -> As the API, allow for CoreCount and ThreadsPerCore
Expected behavior -> See 2.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html
Category tag (optional) -> Compute
Any additional context (optional)

AWS::Glue::Workflow - New Resource

Title -> AWS::Glue::Workflow
Scope of request -> Manages Glue Workflow Resources
Expected behavior -> Create, Update and Delete Glue Workflows
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/glue/latest/dg/aws-glue-api-workflow.html
Category tag (optional) -> Glue

AWS::SES::ConfigurationSetEventDestination - EventDestination-SNS

1. Title

AWS::SES::ConfigurationSetEventDestination-EventDestination-SNS

2. Scope of request

You can't set up a SNS Topic as a SES Configuration Set Event Destination via CloudFormation. At the moment you can only specify CloudWatch or Kinesis Firehose.

3. Expected behavior

Specify an SNS Topic ARN to set that as an Event Destination.
Ensure that you can only specify ONE event destination (CloudWatch OR Kinesis Firehose OR SNS Topic).

4. Test case recommendation (optional)

5. Links to existing API doc (optional)

https://docs.aws.amazon.com/ses/latest/APIReference/API_DescribeConfigurationSet.html
Can use that to check what event destination if any is set up
https://docs.aws.amazon.com/ses/latest/APIReference/API_CreateConfigurationSetEventDestination.html
Create event destination association
https://docs.aws.amazon.com/ses/latest/APIReference/API_UpdateConfigurationSetEventDestination.html
Update
https://docs.aws.amazon.com/ses/latest/APIReference/API_DeleteConfigurationSetEventDestination.html
Delete

6. Category tag (optional)

Integration

7. Any additional context (optional)

None.

AWS::S3::Bucket - (new property) Object Lock

Quick Sample Summary:

Title -> AWS::S3::Bucket - (new property) Object Lock
Scope of request -> AWS::S3::Bucket - buckets should support object lock configurations, to allow a Write Once Read Many (WORM) model.
Expected behavior -> When a user creates a bucket with an Object Lock Policy, it should no longer be writable but still continue to be readable
Test case recommendation (optional) -> once a bucket is created and locked, it should no longer be writable
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/s3api/put-object-lock-configuration.html
Category tag (optional) -> Storage
Any additional context (optional)

AWS::Cognito::UserPoolClient-AllowedOAuthFlowsUserPoolClient

AllowedOAuthFlowsUserPoolClient can be set by the API, but not with CloudFormation. It must be set to enable the OAuth flows and is needed for #47

Create and Update are both supported without replacement.

https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPoolClient.html#CognitoUserPools-CreateUserPoolClient-request-AllowedOAuthFlowsUserPoolClient

Category: Security, Identity, & Compliance

AWS::Config::OrganizationConfigRule - new resource

Title -> AWS::Config::OrganizationConfigRule
Scope of request -> Can create resource via API, but not via CloudFormation.
Expected behavior -> Should be possible to create, update and delete organization config rules as API supports.
Test case recommendation (optional)
Links to existing API doc (optional) -> https://docs.aws.amazon.com/config/latest/APIReference/API_PutOrganizationConfigRule.html & https://docs.aws.amazon.com/config/latest/APIReference/API_DeleteOrganizationConfigRule.html
Category tag (optional) -> Management

AWS::IAM::OpenIDConnectProvider

AWS::ElasticSearch:Domain-LogPublishingOptions

Scope of request

AWS::ElasticSearch:Domain-LogPublishingOptions to turn on logging for AES. It should support all existing (3 as of this writing) log types and ideally future log types.

Expected behavior

See API docs.

Links to existing API doc

https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-configuration-api.html#es-configuration-api-datatypes-logpublishingoptions

Category tag

Analytics

AWS::Events::Rule -> Target -> BatchParameters

Title -> AWS::Events::Rule -> Target -> BatchParameters (new properties), should work for Batch - it should support scheduling of tasks.
Scope of request -> Add ArrayProperties, JobDefinition, JobName, RetryStrategy as valid properties in AWS::Events::Rule --> Target --> BatchParameters
Expected behavior ->
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)
CWE BatchParameters: https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_BatchParameters.html

AWS::EC2::Host - (new property) Host Recovery

Title -> AWS::EC2::Host - (new property) Host Recovery
Scope of request -> AWS::EC2::Host - allow customers to specify whether or not to disable host recovery for the dedicated host
Expected behavior -> When a user supplies this property, CloudFormation should pass it via the api
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/ec2/allocate-hosts.html
Category tag (optional) -> Compute
Any additional context (optional)

AWS::ECS::TaskDefinition (allow splunk logging driver with secrets)

Title -> ECS splunk logging driver with secrets in AWS::ECS::TaskDefinition
Scope of request -> Add secret support for splunk logging driver in ECS task definition
Expected behavior ->
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

AWS::ACM::Certificate

1. Title

AWS::ACM::Certificate-ExistingAttribute-BetterDX

2. Scope of request

other coverage-related issue with the resource/attribute/option

AWS::ACM::Certificate is basically the canonical example of why Custom Resources are needed. It would be great if I could create an ACM cert in CloudFormation and cfn will handle the adding the DNS records.

3. Expected behavior

Samples:

In Create, it should create the cert request, add the records to the DNS hosted Zone (maybe accept a Hosted Zone as a parameter?).

in Update, (Can ACM Certs be updated?)

4. Suggest specific test cases

it should help me create an ACM Certificate given that the same account is the authority for the domain name used in the certificate.

5. Helpful Links to speed up research and evaluation.

The Stack should not stay in "Pending" until I do some manual step, it should do it for me.

Updated API docs at https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-certificatemanager-certificate.html

6. Category (required) - Networking & Content

7. Any additional context (optional)

If you add this, you'll replace DynamoDB as my second favorite service team ;)

AWS::CloudTrail::Trail - IsOrganizationTrail - new property

Title -> AWS::CloudTrail::Trail-IsOrganizationTrail
Scope of request -> AWS::CloudTrail::Trail does not support IsOrganizationTrail attribute.
Expected behavior -> It should pass parameter to API.
Test case recommendation (optional)
Links to existing API doc (optional) -> https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_CreateTrail.html#awscloudtrail-CreateTrail-request-IsOrganizationTrail
Category tag (optional) -> Management

AWS::Cognito::UserPoolClient-AllowedOAuthFlows

AllowedOAuthFlows can be set by the API, but not with CloudFormation

Create and Update are both supported without replacement.

https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPoolClient.htm
https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_UpdateUserPoolClient.html

Category: Security, Identity, & Compliance

AWS::Organizations::AttachPolicy - New Resource

Title -> AWS::Organizations::AttachPolicy
Scope of request -> Attaches an existing SCP Policy to an existing OU
Expected behavior -> An existing policy is attached to an OU.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/organizations/latest/APIReference/API_AttachPolicy.html
Category tag (optional) -> Organizations

Uses the outputs of #33 and #34 to attach a policy to an OU.

AWS::IAM::SAMLProvider - New Resource

Title -> AWS::IAM::SAMLProvider

Scope of request -> Ability to natively create a SAML provider in CloudFormation, currently a custom resource is required.

Expected behavior -> A SAML provider is created, updated or removed. Metadata file could potentially be referenced as an s3 URI similar to a custom resource with CloudFormation package support to upload a local metadata file.
An Update should update the metadata file.

Category (required) -> Security / IAM

AWS::IAM::Role (allow adding a Description)

Quick Sample Summary:

Title -> AWS::AWS::IAM::Role does not expose the ability to add a Description to the role, which is supported in the CreateRole API.
Scope of request -> Allow the ability to add a description to a role when creating it. Also need to add descriptions to previously related roles.
Expected behavior -> Match the CreateRole API as it relates to descriptions. Also, changing descriptions to existing roles is available via the console.
Test case recommendation (optional) -> Cover the 2 cases above (see 3).
Links to existing API doc (optional) -> https://docs.aws.amazon.com/IAM/latest/APIReference/API_CreateRole.html
Category tag (optional) -> Security
Any additional context (optional)

AWS::Redshift::Cluster - EnhancedVpcRouting

1. Title

AWS::Redshift::Cluster-EnhancedVpcRouting

2. Scope of request

new attribute for an existing resource is desired

3. Expected behavior

4. Suggest specific test cases

5. Helpful Links to speed up research and evaluation

https://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateCluster.html

https://aws.amazon.com/about-aws/whats-new/2016/09/amazon-redshift-now-supports-enhanced-vpc-routing/

6. Category (required) - Will help with tagging and be easier to find by other users to +1

DB (RDS, DynamoDB...)

7. Any additional context (optional)

Available since September 2016 (https://aws.amazon.com/about-aws/whats-new/2016/09/amazon-redshift-now-supports-enhanced-vpc-routing/)

AWS::SNS::Topic (allow tags)

Title -> SNS supports tagging and untagging topics, and it should be supported in CloudFormation.
Scope of request -> Allow for tags on create, updating tags, etc.
Expected behavior -> See 2 above.
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> App Integration
Any additional context (optional)

This was announced: https://aws.amazon.com/about-aws/whats-new/2019/05/amazon-sns-adds-support-for-cost-allocation-tags/

AWS::IAM::Role (add tagging support)

Title -> Customers would like to be able to tag IAM Roles from a CloudFormation template, after the recent introduction of the feature. Support for tags in IAM principals has been added to Boto 3 as well.
Scope of request -> Add at creation, and to update existing roles.
Expected behavior -> See 2.
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

AWS::CodeDeploy::DeploymentGroup-DeploymentType Support BLUE_GREEN also for ECS/Fargate

Title -> AWS::CodeDeploy::DeploymentGroup-DeploymentType
Scope of request -> AWS::CodeDeploy::DeploymentGroup-DeploymentType supports BLUE_GREEN for Lambda but not for ECS/Fargate.
Expected behavior -> BlueGreen deployments for ECS/Fargate services.
Links to existing API doc (optional) -> Announcement: https://aws.amazon.com/blogs/devops/use-aws-codedeploy-to-implement-blue-green-deployments-for-aws-fargate-and-amazon-ecs/
Category tag (optional) -> Compute
Any additional context (optional) -> Same request as in Containers Roadmap: aws/containers-roadmap#130

AWS::ECS::TaskDefinition - (new property) GPU Support

Title -> AWS::ECS::TaskDefinition
Scope of request -> AWS::ECS::TaskDefinition should support the use of GPU resources as resource requirements
Expected behavior -> Pass through resource requirements in api call
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-gpu.html
Category tag (optional) -> Compute
Any additional context (optional)

AWS::ECR::Repository - support tagging

Title -> AWS::ECR::Repository - support tagging
Scope of request -> Support tagging for an ECR Repository
Expected behavior -> when a tag gets added to any ECR Repository, add that tag to the provisioned resource as well
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional) ->

AWS::Events::Rule - New Attribute (Event Bus Name)

This new attribute introduced with AWS EventBridge. You can now create a new dedicated Event Bus for handling event and you can also attach Rule to it. By default if event-bus-name is missing from parameter. It will be attach to CloudWatch default Bus.

On create/update with the event-bus-name it should attach to the Event Bus specified
On create/update without event-bus-name it should attach to the default Bus

https://docs.aws.amazon.com/cli/latest/reference/events/put-rule.html

Category: Integration (AWS EventBus)

AWS::ElasticLoadBalancingV2::ListenerRule - Arbitrary header based routing

Title -> AWS::ElasticLoadBalancingV2::ListenerRule - Arbitrary header based routing
Scope of request -> ELB recently announced support for arbitrary header based routing and CloudFormation support should follow
Expected behavior -> When creating a Listener Rule in CloudFormation, we should be able to specify arbitrary header based routing conditions
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/elb/create-load-balancer-listeners.html
Category tag (optional) -> Networking
Any additional context (optional)

AWS::EFS::MountTarget - (new GetAtt) IP Address

Title -> AWS::EFS::MountTarget
Scope of request -> AWS::EFS::MountTarget should support a !GetAtt of an IP Address
Expected behavior -> When using a !GetAtt on an AWS::EFS::MountTarget, an IP Address should be a valid property
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/efs/create-mount-target.html
Category tag (optional) -> Storage
Any additional context (optional) -> This is adding a GetAtt to an existing resource

AWS::DirectoryService::ADConnector - New Resource

1. Title -> AWS::DirectoryService::ADConnector

2. Scope of request -> Currently AWS::DirectoryService supports SimpleAD and MicrosoftAD. Support for ADConnector should be added. This is currently supported by the API

3. Expected behavior -> Create should create a new AD Connector, Delete should delete the AD Connector. There is currently no API to Update the AD Connector.

4. Test case recommendation (optional) -> N/A

5. Links to existing API doc (optional) -> https://docs.aws.amazon.com/directoryservice/latest/devguide/API_ConnectDirectory.html

6. Category tag (optional) -> Security / DirectoryService

AWS::ApiGateway::DomainName- (new parameter)

Add new parameters to AWS::ApiGateway::DomainName -> Security Policy, DomainNameStatus

Scope of request -> Create Domain Name API takes additional input: security policy
3. Expected behavior -> in Create, allow setting security policy. In Update, allow changing to a different security policy.
4. Test case recommendation (optional) -> Once done, get domain name should return domain name with new attributes security policy and status
5. Links to existing API doc (optional) -> API docs at https://docs.aws.amazon.com/apigateway/api-reference/resource/domain-name/
6. Category tag (optional) -> Networking/Content Delivery
7. Any additional context (optional)

AWS::ECS::TaskDefinition (allow support for pid and ipc docker run options)

Title -> Add support for additional Docker Run options: ipc and pid
Scope of request -> Allow configuration for ipc and pid in task definition
Expected behavior -> Should work for creates and updates
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

AWS::ECS::TaskDefinition (allow support for additional Docker Run options)

Title -> Add support for additional Docker Run options: interactive, pseudoTerminal, systemControls
Scope of request -> Allow configuration for ipc and pid in task definition
Expected behavior -> Should work for creates and updates
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

AWS::Events::Bus - New Resource

CloudWatch Event recently got rebranded as EventBridge and introduced new dedicated EventBus.

When create a new Event Bus should be created.
When update existing Bus should raise Error
When delete the Bus should be deleted unless there is event rule attached to it

https://docs.aws.amazon.com/cli/latest/reference/events/index.html#cli-aws-events

Category: Integration (AWS EventBus)

AWS::Events::Rule -> Target -> EcsParameters (new properties)(support for scheduled tasks)

Title -> AWS::Events::Rule -> Target -> EcsParameters (new properties), should work for ECS and Fargate - it should support scheduling of tasks.
Scope of request -> Add Group, LaunchType, NetworkConfiguration and PlatformVersion as valid properties in AWS::Events::Rule --> Target --> EcsParameters
Expected behavior ->
Test case recommendation (optional) ->
Links to existing API doc (optional) ->
Category tag (optional) -> Compute
Any additional context (optional)

See
CFN ECSParameters: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-events-rule-ecsparameters.html
CWE ECSParameters: https://docs.aws.amazon.com/AmazonCloudWatchEvents/latest/APIReference/API_EcsParameters.html

AWS::ECS::TaskDefinition - (new property) Secrets

Title -> AWS::EC2::TaskDefinition
Scope of request -> AWS::EC2::TaskDefinition currently does not support secrets, but the ECS task definition api call does.
Expected behavior -> Secrets should be consumed by TaskDefinition but not leaked.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/ecs/register-task-definition.html
Category tag (optional) -> Compute
Any additional context (optional) - > ecs containers roadmap issue: aws/containers-roadmap#97

AWS::EC2::Route-TransitGatewayId (new property)

Title -> AWS::EC2::Route-TransitGatewayId (new property) to support Transit Gateway
Scope of request -> Allow this property to be supported via Cloudformation to support usage of Transit Gateway
Expected behavior -> When a user adds a TransitGatewayId, CloudFormation passes that Id to the Route request.
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/cli/latest/reference/ec2/create-route.html
Category tag (optional) -> Compute
Any additional context (optional) -> Usage of Transit Gateway isn't sufficient until this requirement is satisfied.

AWS::Organizations::Policy - New Resource

Title -> AWS::Organizations::Policy
Scope of request -> Create and manage a SCP inside an AWS Organization
Expected behavior -> A new policy is created and available to be attached to an OU
Test case recommendation (optional) ->
Links to existing API doc (optional) -> https://docs.aws.amazon.com/organizations/latest/APIReference/API_CreatePolicy.html
Category tag (optional) -> Organizations

aws-cloudformation / cloudformation-coverage-roadmap Goto Github PK

cloudformation-coverage-roadmap's Introduction

CloudFormation Public Coverage Roadmap

Introduction

Security disclosures

FAQs

Community

License Summary

cloudformation-coverage-roadmap's People

Contributors

Stargazers

Watchers

Forkers

cloudformation-coverage-roadmap's Issues

Scope of request

Expected behavior

Links to existing API doc

Category tag

1. Title

2. Scope of request

3. Expected behavior

In Create, it should create the cert request, add the records to the DNS hosted Zone (maybe accept a Hosted Zone as a parameter?).

in Update, (Can ACM Certs be updated?)

4. Suggest specific test cases

5. Helpful Links to speed up research and evaluation.

6. Category (required) - Networking & Content

7. Any additional context (optional)

1. Title

AWS::Redshift::Cluster-EnhancedVpcRouting

2. Scope of request

3. Expected behavior

4. Suggest specific test cases

5. Helpful Links to speed up research and evaluation

6. Category (required) - Will help with tagging and be easier to find by other users to +1

7. Any additional context (optional)

Recommend Projects

Recommend Topics

Recommend Org