OCI Foundations - Governance and Administration: Difference between revisions
Jump to navigation
Jump to search
NickPGSmith (talk | contribs) (Created page with "== Pricing == Pricing Models: * Pay as you go * Annual Universal Credits (significant savings, more resource use are PAYG) * Monthly universal credits * Bring your own license Factors that impact pricong: * Bigger resources cost more * Data transfer * VMs vs bare metal * Same pricing across the world Data Transfer costs * Don't pay for transfer between ADs * Ingress traffic is free * Pay or Outgoing traffic == Cost Management == Budgets: * Set up alerts if forcasts...") |
NickPGSmith (talk | contribs) |
||
Line 36: | Line 36: | ||
== Tagging == | == Tagging == | ||
Key/Value pairs to organise resources | |||
* eg: Env=Prod, Project=Alpha | |||
* Cost management/reporting | |||
* Tag based Access Control (policies based on tags) | |||
Free-form tags: | |||
* No defined schema or access restriction | |||
Defined tags: | |||
* Recommended | |||
* Defined within a namespace | |||
* Can write a policy for who can define a tag | |||
* Can define allowed values for a tag (schema) | |||
Operations.Environment="Production" | |||
* Namespace: Operations | |||
* Key: Environment | |||
Namespaces cannot be deleted but can be retired. | |||
== Support Rewards == | == Support Rewards == |
Revision as of 16:39, 22 July 2023
Pricing
Pricing Models:
- Pay as you go
- Annual Universal Credits (significant savings, more resource use are PAYG)
- Monthly universal credits
- Bring your own license
Factors that impact pricong:
- Bigger resources cost more
- Data transfer
- VMs vs bare metal
- Same pricing across the world
Data Transfer costs
- Don't pay for transfer between ADs
- Ingress traffic is free
- Pay or Outgoing traffic
Cost Management
Budgets:
- Set up alerts if forcasts are expected to exceed the budget
Cost Analysis:
- Look at past costs
- CSV files generated daily
Service Limits and Usage:
- Limits, Quotas and Usage controls
Compartment Quotas
- Sets the max number of cloud resources that can be used
- Prevent misuse, etc
Tagging
Key/Value pairs to organise resources
- eg: Env=Prod, Project=Alpha
- Cost management/reporting
- Tag based Access Control (policies based on tags)
Free-form tags:
- No defined schema or access restriction
Defined tags:
- Recommended
- Defined within a namespace
- Can write a policy for who can define a tag
- Can define allowed values for a tag (schema)
Operations.Environment="Production"
- Namespace: Operations
- Key: Environment
Namespaces cannot be deleted but can be retired.