Track community.aws modules with no amazon.aws downstream equivalent #2458

Summary

Several community.aws modules remain required for real-world automation because amazon.aws has no equivalent module today. Downstream product teams (Red Hat Ansible Validated Content / supported collections) need explicit coverage for these use cases so consumers can migrate off community.aws without boto3 workarounds or custom EE images.

This issue tracks modules called out from ansible/product-demos cloud content, where report and networking demos depend on community.aws specifically.

Modules with no amazon.aws equivalent (requested for downstream support)

Module	Use case in product-demos	Notes
community.aws.s3_website	S3 static website hosting (IndexDocument, error keys, redirects)	amazon.aws.s3_bucket manages the bucket but does not configure website hosting. Workaround today is raw boto3 put_bucket_website.
community.aws.s3_sync	Bulk upload/sync of a local directory tree to an S3 bucket	amazon.aws.s3_object handles single objects only; no recursive sync module exists in amazon.aws.

Additional community.aws modules used in product-demos (networking demos)

These are also not covered by equivalent amazon.aws modules today and block running peer/transit VPC demos on EEs that only ship amazon.aws:

Module	Use case
community.aws.ec2_vpc_peer	Create/accept VPC peering connections
community.aws.ec2_vpc_peering_info	Query VPC peering connections
community.aws.ec2_transit_gateway	Create/manage transit gateways
community.aws.ec2_transit_gateway_info	Query transit gateways
community.aws.ec2_transit_gateway_vpc_attachment	Attach VPCs to transit gateways
community.aws.ec2_transit_gateway_vpc_attachment_info	Query TGW VPC attachments

Impact

• Ansible Product Demos cloud report jobs (Cloud | AWS | VPC Report, Cloud | AWS | Tags Report) require s3_website and s3_sync for S3-hosted HTML reports.
• Default Product Demos EE ships amazon.aws but not community.aws, so report jobs fail unless a separate EE (e.g. one built with community.aws) is configured.
• Peer/transit networking demos fail similarly without community.aws transit gateway and VPC peering modules.

Request

Please track adding supported downstream equivalents in amazon.aws (or document an official supported migration path) for at minimum:

1. S3 static website configuration (s3_website)
2. S3 directory sync (s3_sync)

…and evaluate transit gateway / VPC peering modules for the same treatment.

References

• product-demos roles: demo.cloud.build_report_s3, demo.cloud.reports
• product-demos playbooks: cloud/cloud_report.yml, cloud/create_reports.yml
• Related: amazon.aws.s3_bucket docs do not expose website configuration