- fix graceful shutdown
- Update dependencies
- Update docs and parameters for Lamba Attacks to use https://github.com/steadybit/failure-lambda
- Prevent concurrent executions of Lambda Attacks with the same Failure-SSM-Parameter
- Fix ECS Stop Task Action
- Update dependencies (go 1.22)
- Revisited AZ Blackhole attack
- Reduced amount of required API calls
- Added tests for rollback behaviour
- Fixed a bug where an unused network acl wasn't deleted
- Added ECS Support
- Discovery for Tasks and Services
- Action to stop a Task
- Action to scale a Service
- Actions to inject CPU/IO/memory stress or disk fill for a Task using SSM see README-ecs-ssm-setup.md for the necessary setup
- Check Service Task count
- Service Event Log
- Requires new permissions (or needs to be disabled via
STEADYBIT_EXTENSION_DISCOVERY_DISABLED_ECS
)"ecs:ListClusters", "ecs:ListTasks", "ecs:DescribeTasks", "ecs:ListServices", "ecs:DescribeServices", "ecs:StopTask", "ecs:UpdateService"
- Added ELB Support
- Discovery for Application Load Balancers
- Action to return a static response for a Load Balancer Listener
- Requires new permissions (or needs to be disabled via
STEADYBIT_EXTENSION_DISCOVERY_DISABLED_ELB
)"elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeListeners", "elasticloadbalancing:DescribeTags", "elasticloadbalancing:DescribeRules", "elasticloadbalancing:SetRulePriorities", "elasticloadbalancing:CreateRule", "elasticloadbalancing:DeleteRule", "elasticloadbalancing:AddTags", "elasticloadbalancing:RemoveTags"
- Update dependencies
- Add Force Failover parameter to Trigger RDS Instance Reboot
- Make attribute for EC2 data enrichment configurable via
STEADYBIT_EXTENSION_ENRICH_EC2_DATA_MATCHER_ATTRIBUTE
- Update dependencies
- Update dependencies
- Update dependencies
- Update discovery_kit_sdk to v1.0.5, to resolve error in caching discovery
- Update dependencies
- consume RDS instance and cluster tags
- Update dependencies
- Update dependencies
- Update dependencies
- fixed enrichment for jvm instances
- ignore erroneous roleArns during initialization
- use discovery_kit_sdk for discoveries
- add
aws.zone.id
to ec2- and rds-instances - added
aws.zone.id
to all enrichment rules
- Added
pprof
endpoints for debugging purposes - Update dependencies
- Enrichment for kubernetes-statefulsets, -daemonsets, -nodes and -pods
- Possibility to exclude attributes from discovery
- Fix:
slice index out of range
error in discovery
- Fix:
DiscoveryDisabled*
-Properties are working again
- Make Discovery Intervals configurable
- Keep a copy of current targets in discoveries and call aws apis not in the context of the agent request.
- Allow parallel API calls using a configurable amount of worker threads via
STEADYBIT_EXTENSION_WORKER_THREADS
- Add enrichment rules for kubernetes deployments
- Make targets to recieve EC2 data configurable via
STEADYBIT_EXTENSION_ENRICH_EC2_DATA_FOR_TARGET_TYPES
- user service icons for actions
- collect EC2 instance state in discovery
- update dependencies
- migration to new unified steadybit actionIds and targetTypes
- added hint to aws account lookup of the agent in case of an error
- update dependencies
- replace RDS instance downtime attack with RDS instance stop attack
- add RDS instance downtime attack
- add RDS cluster failover attack
- add RDS cluster discovery
- Add linux package build
- Prefix label attributes at ec2 target discovery with
aws-ec2.
.
- Support read only file system
- Update dependencies
- Support Readiness & Liveness probes (requires helm chart version >= 2.0.0)
- Refactored to use
action_kit_sdk
and thus use the extended rollback safety while having connection issues - Added Lambda discovery & actions (requires new permissions)
- Renamed attack
ec2-instance.state
tocom.github.steadybit.extension_aws.ec2_instance.state
- Added EC2-Instance discovery
- Added Zone-Discovery and Availability Zone Blackhole attack
- Added AWS FIS-Experiment discovery and AWS FIS-Experiment action
- Print build information on extension startup.
- Add missing
kind
field to both actions.
- Support creation of a TLS server through the environment variables
STEADYBIT_EXTENSION_TLS_SERVER_CERT
andSTEADYBIT_EXTENSION_TLS_SERVER_KEY
. Both environment variables must refer to files containing the certificate and key in PEM format. - Support mutual TLS through the environment variable
STEADYBIT_EXTENSION_TLS_CLIENT_CAS
. The environment must refer to a comma-separated list of files containing allowed clients' CA certificates in PEM format.
- Support for AWS role assumption. This permits one extension instance from gathering data from multiple AWS accounts. To configure this, you must set the
STEADYBIT_EXTENSION_ASSUME_ROLES
environment variable to a comma-separated list of role ARNs. Example:STEADYBIT_EXTENSION_ASSUME_ROLES='arn:aws:iam::1111111111:role/steadybit-extension-aws,arn:aws:iam::22222222:role/steadybit-extension-aws'
.
- Support for the
STEADYBIT_LOG_FORMAT
env variable. When set tojson
, extensions will log JSON lines to stderr.
- Restrict discovery execution to AWS agents to avoid common issues.
- The log level can now be configured through the
STEADYBIT_LOG_LEVEL
environment variable.
- Expose AWS RDS instance status in target table
- Report AWS RDS instance status
- EC2 instance state attacks, i.e., EC2 instance stop, reboot, hibernate and terminate.
- Initial release