Skip to main content

Built-in Plugins

This page lists the application and compliance plugins registered by cloudforge-api, and the sample plugins in cfc-testing. For how plugins are discovered, see PLUGIN-SYSTEM.md.

Validate each application specification against your workload before production use.


Applications (35)​

General applications (16)​

These implement ApplicationSpec, carry @ApplicationPlugin, and deploy with the application-service topology. All of them declare support for both Fargate and EC2.

CategoryApplicationIDOIDC
CI/CDJenkinsjenkinsyes
CI/CDGitLabgitlabyes
CI/CDDronedroneno
Code qualitySonarQubesonarqubeno
Version controlGiteagiteano
MonitoringGrafanagrafanayes
MonitoringPrometheusprometheusno
AnalyticsMetabasemetabaseyes
AnalyticsSupersetsupersetno
DatabasePostgreSQLpostgresqlno
DatabaseRedisredisno
Artifact registryNexusnexusno
Artifact registryHarborharborno
SecretsVaultvaultno
CollaborationMattermost Enterprisemattermost-enterpriseyes
CollaborationMattermost Teammattermost-teamyes

The OIDC column reflects supportsOidc on the plugin annotation. Applications without application-level OIDC can still use alb-oidc where the spec allows it.

PHP / CMS applications (19)​

These implement CmsSpec, which extends ApplicationSpec with PHP runtime, media storage, CDN, object cache, and cron settings. They carry @CmsPlugin and deploy with "topology": "cms-service" and the ID below as applicationId.

CategoryApplicationID
CMSWordPresswordpress
CMSDrupaldrupal
CMSJoomlajoomla
CMSTYPO3typo3
CMSConcrete CMSconcrete-cms
CMSOctober CMSoctober-cms
E-commerceWooCommercewoocommerce
E-commerceMagento 2 / Adobe Commercemagento
E-commercePrestaShopprestashop
E-commerceOpenCartopencart
E-commerceSyliussylius
E-commerceBagistobagisto
ForumphpBBphpbb
ForumFlarumflarum
ForumMyBBmybb
CRMSuiteCRMsuitecrm
WikiMediaWikimediawiki
LMSMoodlemoodle
SocialUNA (Dolphin)dolphin-una

Depending on what each spec declares, the cms-service topology can add:

  • an S3 media bucket and CloudFront distribution with media, static, and admin path behaviors
  • an ElastiCache Redis object cache, with CMS-specific Redis and database environment variables
  • system cron entries from cronCommands(...)
  • PHP-FPM and OPcache settings from the spec

The CMS guide documents CMS deployment settings, and the application catalog covers individual applications.


Compliance frameworks (18)​

Always load (11)​

These install for every deployment that has auditManagerEnabled: true.

Framework IDPriorityScope
KeyManagement-10KMS, secrets, and certificate controls
DatabaseSecurity-5RDS and DynamoDB controls
AdvancedMonitoring-5Security Hub, Inspector, and Macie
ThreatProtection0Malware protection, intrusion detection, file integrity
IncidentResponse0Backup, recovery, and forensics
ComputeSecurity0Compute resource controls
LambdaSecurity0Lambda function controls
CdnApiSecurity0CDN and API Gateway controls
ElbSecurity0Load balancer controls
MessagingSecurity0Messaging service controls
IamSecurity0IAM policy and access controls

Conditional (7)​

These install when named in complianceFrameworks.

Framework IDPriorityStandard
HIPAA10HIPAA Security Rule technical safeguards
HIPAA-Organizational15HIPAA administrative safeguards
PCI-DSS20PCI DSS
GDPR30GDPR technical measures
GDPR-Organizational35GDPR organizational measures
SOC240SOC 2 Trust Services Criteria
ISO-2700150ISO/IEC 27001:2022

complianceFrameworks currently accepts only hipaa, pci-dss, soc2, and gdpr; see the limitation in the compliance plugin guide.

{
"securityProfile": "PRODUCTION",
"complianceFrameworks": "hipaa,pci-dss",
"auditManagerEnabled": true
}

Sample plugins​

The cfc-testing module is the reference plugin consumer and is also published as cloudforge-sample. It registers:

ClassTypeIDNotes
CraftCmsApplicationSpecCmsSpec + DatabaseSpeccraft-cmsCraft CMS; web/ document root, queue cron, alb-oidc
CustomSecurityPolicyRulesFrameworkRulesCustomSecurityExample internal policy (priority 60)
OpenSourceSecurityPolicyRulesFrameworkRulesOpenSourceSecurityExample open-source project policy (priority 65)

Use these as starting points for your own plugins. To build one, follow the application plugin guide or the compliance plugin guide.