Advisory for Customers Deploying eMAM System on AWS
To
ensure the smooth functioning of the eMAM system, please refrain from making
any changes to your AWS infrastructure.
Advisory:
- Maintain
Proper Security Protocols:
- Ensure
that IAM roles and policies are correctly configured to grant
necessary access without over-permission.
- Avoid
making changes to IAM roles or policies that could revoke required
permissions for the MAM system.
- Monitor
Network Configurations:
- Ensure
VPC and security groups are configured to allow the required ports
and protocols for communication between MAM components.
- Avoid
modifications to firewall rules or network access that could block
essential data flow.
- Stable
IP Address Allocation:
- Assign
static IP addresses to critical services and servers running MAM
components to prevent IP changes that may disrupt connections.
- Avoid
Unplanned Instance Modifications:
- Do
not alter instance types or configurations without prior
consultation, as changes to CPU, RAM, or storage may impact system
performance.
- Data
Backup and Recovery:
- Regularly
back up data and system configurations using AWS backup services.
- Ensure
that any changes made to backup schedules or recovery strategies align
with best practices for the MAM system.
- Storage
Configurations:
- Do
not alter the storage type or access permissions of the designated
storage (e.g., S3 buckets, EBS volumes) without confirming the impact on
MAM operations.
- Maintain
consistent storage paths and ensure bucket policies allow necessary
read/write access.
- OS
and Software Updates:
- Consult
the EMAM team before updating the operating system or core
libraries on instances hosting the eMAM system to avoid compatibility
issues.
- Resource
Scaling:
- Ensure
scaling activities, such as increasing or decreasing instance counts or
sizes, do not interrupt active eMAM processes.
- Coordinate
planned scaling with the eMAM support team if auto-scaling is enabled.
- Avoid
Unauthorized Access:
- Restrict
access to eMAM-related instances and data to authorized users only.
- Monitor
for suspicious activities or changes in access logs that may indicate
security threats.
- Maintain
Configurations:
- Avoid
manual changes to config files related to the eMAM system unless
advised by the support team.
- Use
version control for configuration changes and keep a rollback plan for
unexpected results.
- Regular
Monitoring:
- Utilize
AWS CloudWatch or other monitoring tools to track the performance
and health of eMAM components.
- Report
any anomalies or performance issues to the EMAM support team promptly.
- Integration
Restrictions:
- Avoid
integrating third-party services or applications with the eMAM system
without prior approval to prevent potential conflicts.