AWS Amazon Data Lifecycle Manager

What authentication does the Amazon DLM API use?

DLM uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in your Jentic One instance and are injected into signed requests at execution time, so the agent never sees the raw secret access key.

Can I update an existing lifecycle policy without deleting it?

Yes. Call PATCH /policies/{policyId} with the modified PolicyDetails - including schedules and retention rules - and the existing policy is updated in place. The schedule continues without losing history of past runs.

What are the rate limits for the Amazon DLM API?

DLM shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. Bulk policy listing should rely on pagination, and ThrottlingException responses should trigger backoff.

How do I create an EBS snapshot policy through Jentic?

Search Jentic for 'create a DLM lifecycle policy', load CreateLifecyclePolicy, then execute it with PolicyDetails.ResourceTypes, TargetTags, and a Schedules array. Run pip install jentic to use the async search and execute pattern.

Does this API actually take snapshots, or only schedule them?

The API only schedules and configures policies. Snapshot creation happens automatically inside AWS based on the policy schedule, and the resulting snapshots appear in the EC2 EBS API rather than in DLM responses.

Can I limit what my agent is allowed to do with the Amazon Data Lifecycle Manager API?

Yes. Because you run Jentic One yourself, your own rules decide which DLM operations and credentials the agent may use. Since DLM puts the policy id in the URL path (/policies/{policyId}), you can pin the agent to a single lifecycle policy so it reads and updates that one policy and nothing else. You choose the operations it may call, so DeleteLifecyclePolicy stays out of reach unless you explicitly allow it.